...

In VIVO, the basic functions of browsing and searching are open to anyone. However, if a VIVO user wants to edit items on their profile, view restricted data, or to manage VIVO, he they must log in to via a User Account.

When a user logs in, he they provides his their credentials and is are associated with a User Account. The credentials are often an Email address and password, but might be different information, depending on how VIVO is configured.

...

• External Authentication ID – permits logging in by the External Authentication system.
  NOTE: Two User Accounts may not have the same External Authentication ID
• Password – permits logging in by the Internal Authentication system.
• Matching ID – value can be used to associate the User Account with a profile page.

...

System Administrator –- In addition to the abilities of the Curator, the Administrator may access the menu management, user accounts, and advanced data tools features. The advanced data tools section include the ingest menu, Add/Remove RDF data, RDF export, SPARQL query, and SPARQL query builder privileges.

Associating User Accounts with Profile Pages

Each User Account may be matched associated with an Individual in the VIVO data model. The display page for that Individual is known as the “profile” for that User Account.

A common use of this feature is matching a profile to each member of the campus community. When a user logs in to VIVO, he is they are directed to his their profile page, and is are authorized to edit the information on that page.

It is typical for a university to ingest information into VIVO, including the “network ID” for each member of the campus community. When a user logs in to VIVO using the External Authentication system, the ID from the authenticating system is matched against the “network ID” on the individual, and VIVO matches the User Account to the profile.

It is also possible for an administrator to match a User Account with a profile by editing the User Account.

...

To associate profiles with user accounts,

1. set selfEditing.idMatchingProperty in runtime.properties to the URI of the datatype property whose values will be used to associate profiles to accounts.  A common choice it he university "net id" or other local identifier.
2. For each user that will have a corresponding account, set the value of the idMatchingProperty on the user's profile.
3. Set the value of Matching ID on the user's account to the value on the user's profile.

The Root User Account

Each VIVO installation has a special User Account, called the root account. The root account has no Role. Nonetheless, the root account is authorized:

...