Access rights and security

Controlling access to a GraphDB repository and assigning user accounts to roles with specified access permissions allows you to:

  • Create security constraints on operations (reading statements, writing statements, modifying named graphs, changing namespace definitions, etc.);
  • Group security constraints in security roles;
  • Manage user accounts and assign these to specific security roles.

Managing users’ access

To manage your users’ access, go to Setup -> Users and Access. The page displays a list of users and the number of repositories they have access to.


Here you can create new users, edit their profiles, change their password, user roles, and read/write permissions for each repository, and delete them. Repository permissions can be bound to a specific location or to all locations (“*” in the location list).

User roles

  • User - a user who can read and write according to his permissions for each repository;
  • Repository admin - a user who can manage repositories but cannot manage locations and users.
  • Full Admin - a user with full access, including creating, editing and deleting users.

Login and default credentials

By default, the security for the entire Workbench instance is disabled. It means that everyone has full access to the repositories and the admin functionality. To enable them, move the Security slider above the user table to on. If security is enabled, the first page you will see is the login page.


The default administrator account information is:

username: admin
password: root

It is highly recommended that you change the root password as soon as you log in for the first time. Click your username (admin) in the top right corner to change it.

Free access

To allow people to access a predefined set of functionalities without having to log in, go to Admin -> Users and Access and click the Free Access slider above the user table. A dialog box opens and prompts you to select the access rights for free access users. The available permissions are similar to those for authenticated users, e.g., you can provide read or read/write access to one or more repositories.


To use free access, you must have security enabled. The settings do not show if security is disabled.



Free access is especially useful for providing read-only access to a repository.