Managing Studio users

In situations where LDAP isn't used, Studio administrators can add, edit, and remove users.

When adding a new user, you specify their details, including:

Their password. You can also specify whether they're required to change it the first time they log in. To ensure the security of both the user and the application, this should always be required.
Their role: administrator, power user, user, restricted user, or none. You should verify that the user can be trusted before making them an administrator or power user.
Their level of data set access: read only or read/write.
Their access to individual projects and their role within each. In scenarios that require strict security, new uses should only have access to projects they need to be involved in.

Once the user has been added, administrators can edit the above information at any time. They can also edit roles the user inherits from any groups they belong to.

Administrators also have the option of deactivating users. Once a user has been deactivated, they can be either reactivated or deleted.

For more information on managing users, see the Administrator's Guide.