Creating Custom Roles in Guru

👥

Access Required

Only Admins (or a relevant custom role) can create and manage Custom Roles.

📘

Best Practices

• Assign roles explicitly to ensure permissions are effective. Check out the scoping exercise below.
• Use role toggles carefully, especially for sensitive permissions like deleting content or managing billing.
• Test roles in smaller batches before rolling them out widely.

Watch the video tutorial: Assigning access in Guru

Understanding Custom Roles

Unlike System Roles, Custom Roles can be tailored to meet your team's specific permissioning needs. Custom Roles define permission profiles but do not grant access on their own. Permissions become active only when assigned to specific objects such as Workspaces, Collections, Knowledge Agents, Sources, or Pages.

Understanding System Roles

While Custom Roles can be set to meet your team's specific permissioning needs, there are three System Roles that are unchangeable in Guru: Admins, Creators, and Owners.

1. Admin is a Workspace-level rolein Guru. Admins can manage the overall platform configuration, permissions, content, users, and integrations.
2. Owner is a workspace-level role in Guru. Admins can delegate elevated access to specific objects to Owners—like Collections, Pages, Sources, and Knowledge Agents—without granting full Admin rights.

❗️

Important

Users with the Owner role have no access to any other objects unless explicitly granted.

Owners only gain permissions for the specific object(s) where they are designated as an Owner.

3. Creator is a Workspace-level role in Guru. Creators can create new objects, but cannot manage objects they didn't create. When a Creator creates one of these objects, they automatically become the Owner of that object. Users with the Creator role can create the following:
   1. Knowledge Agents
   2. Collections (Including Cards and folders within Collections they created)
   3. Pages
   4. Sources

❗️

Important

Users with the Creator role can only create the supported object types listed above. They do not have any elevated permissions beyond object creation.

However, because they become the Owner of any object they create, they will gain:

• Edit
• Share
• Delete

permissions for that object.

Creating and Editing Custom Roles

1. Go to the Manage menu.
2. Select Custom Roles to see all system and custom roles, along with available permissions.

1. Click Create New custom role to create a new one from scratch.
   1. Alternately, you can choose to duplicate an existing role's permissions by clicking the three stacked dots next to an existing role and select Duplicate.
2. Name the role.
3. Click Create.
4. Use the permission checkboxes within the table to assign relevant actions for each object.
5. Next, don't forget to navigate to the specific object settings (Workspaces, Collections, Knowledge Agents, Sources, or Pages.

Assigning Roles to Objects

• Custom roles must be assigned to individual objects (e.g., Workspaces, Collections, Knowledge Agents, Sources, or Pages).
• Creating an object (like a Page) automatically assigns the Owner role to the creator.
• Custom roles cannot be set as default roles for newly created objects.

Frequently asked questions about Custom Roles

What happened to Author and Expert roles?

1. Teams that were created before the Custom Roles feature was rolled out had access to Author and Expert roles. Those roles still exist, though they have been transitioned to Custom Roles and can be managed and customized to your needs under manage > Custom Roles.

**What is the best way to scope out a new role? **

Use the following exercise to scope out a new custom role.