User management¶
What’s in this document?
See also
User roles and permissions describes in detail the different roles and permissions that can be assigned to users.
When you are logged in as an admin user, which is the default, you can create, delete, and modify user accounts.
Create new user¶
To reach the Create new user screen, select and then click the Create new user button. The following shows an example of this screen:
Note
Workbench uses a similar screen for users to customize Workbench behavior. See Customizing Workbench behavior for more on the User settings section of this screen.
Each account must have a non-blank password set for it, unless Don’t set a password has been enabled.
A user account can be assigned one of three built-in roles:
User — users with this role can use GraphDB and they can save SPARQL queries, graph visualizations and user-specific server-side settings. They can also be given read and write access to specific repositories.
Repository manager — in addition to the capabilities of a User role, a user with a Repository manager role also has full read and write permission to all repositories and can create, edit, and delete repositories. Repository managers can also access monitoring features and configure whether the service reports anonymous usage statistics.
Admin — in addition to what Repository managers can do, a user with an Admin role can perform any server operation. This includes management of users and access, management of clusters, attaching remote locations, and viewing system information.
In the Repository permissions section of this screen, granting an account write permission for a given repository includes read permission for that repository. If the GraphQL only checkbox is selected with the Read checkbox for a given user and repository (or for Any data repository), then when security is turned on for this GraphDB instance, that user will only be able to read that data using the GraphQL interface. If GraphQL only is checked with the Write checkbox, the specified user will only be able to write to the indicated repository or repositories with the GraphQL interface when security is turned on. (See this documentation’s GraphQL section for more information on GraphDB’s support for this query language.)
You can grant global access to all repositories to any individual user by using the Any data repository checkbox.
This interface also provides Custom user roles, which can be used together with Fine-grained access control for controlling access to individual RDF statements or named graphs, or Role-Based Access Control in GraphQL.
Delete user¶
To delete a user account, go to the screen and click the Delete user trash can icon on the row listing the account that you wish to delete. A message box will ask you to confirm before it deletes the account.
Edit user account details¶
On the screen, each edit icon in the Actions column takes you to the screen that lets you edit the configuration of the user listed on that icon’s row. The following shows the edit screen for the admin user:
The only difference between the Edit user and Create new user screens is that in Edit user you cannot change the username.
The settings available through this form are the same as the settings that can be modified when creating a new user account, with the sole exception of the name of the account, which cannot be changed.