User accounts and permissions manage who has access to Slate and what capabilities a user is granted within your database. Slate supports unlimited user accounts, giving access to as many individuals as needed. Before a user can access your database, a new user account must be created by a current user who is granted permission to the Security Administrator.
Security administrators can add new users, deactivate existing users, and manage user access to records and resources in Slate through the User Permissions module.
Types
You can create the following types of users in a database:
User
A user is an individual who has an institutional account and needs access to Slate to view or edit record data. A user typically connects to Slate through your single-sign-on system. You will use the "User" type for most users' accounts in a database.
User (External)
An external user is an individual who does NOT have an institutional account but needs to access Slate to view or edit record data. Slate authentication will be used for these users, and an activation password must be set. External users must log in to Slate through the External Login URL, for example, https://apply.slateuniversity.edu/manage/login/external.
If an external user needs to access a test environment, the user must exist in test and log in through the External Login URL specific to the test environment.
Service Account and Service Account (Remote)
A service account or service account (remote) is configured for accounts that only need access to the Slate SFTP servers or web services.
Add a User
Use the following steps to add a new user account:
|
|
|
*Click here for a complete listing of all setting descriptions. |
|
After a user account is created, they may be granted permissions by:
- Selecting individual permissions on the Permissions tab
- Inheriting permissions through a role granted on the Roles tab
- Through population permissions granted on the Populations tab.
If a user account is created within your database after your test environment is provisioned, they will not have access to your test environment. Instead, you will need to either:
- Refresh your test environment, so it includes the newly added user account.
- Recreate the user in your test environment.