- Allow users to request membership of a Guru group from the web and Slack
- Give a group a role on a collection: Member, Author, or Collection Owner
- Review who is a workspace Admin
- Optionally sync Knowledge Agents, and give groups a role on each one
- Optionally remove someone from Guru when they’re removed from the app in Opal, which frees their seat
- Automatically revoke access when a time-bound grant expires
Supported resources
Opal syncs active members of the workspace and matches them to people in Opal by email. Knowledge Agents are listed in Guru’s member directory, and Opal skips them. Pending invitations stay out of Opal until the person joins.
Knowledge Agents sync only when Sync Knowledge Agents is
true.
How Guru access maps to Opal
- Groups: each user group appears in Opal as a Guru Group. Users request membership of a group, and revoking that grant removes them from the group. Guru’s private single-person groups are not synced.
- Collections: each collection appears in Opal as a Guru Collection, with the access levels Member, Author, and Collection Owner. Guru grants a collection to groups only, and each group holds one role, so a person reaches a collection by belonging to a group that has a role on it. Giving that group a different role replaces the current one. Revoking the grant removes the group from the collection.
- Knowledge Agents: when sync is on, each Knowledge Agent appears in Opal as a Guru Knowledge Agent, with the access levels Viewer, Expert, and Admin. Groups hold these roles the same way they hold collection roles.
- Workspace Admin: the workspace appears in Opal as Guru Workspace, listing everyone whose highest role is Admin. Opal syncs that role for review. Guru computes every other highest role from collection access, and it has no API for changing the Admin role, so Opal can’t grant or revoke it.
Limitations
- Opal can’t invite someone to Guru. People join through Guru or your identity provider.
- Opal doesn’t sync folders or cards. They inherit access from their collection.
- Opal manages Guru’s standard collection roles. A custom collection role defined in the workspace is left as it is in Guru.
- Groups an identity provider manages through SCIM stay in the sync. Change their membership in the identity provider. Guru can reject a membership change on those groups.
- Removing someone from the Guru workspace stays off until Remove users from Guru is
true.
Requirements
Before you begin, you must:- Be an Opal Admin
- Be a Guru Admin, so you can generate a user token. An Admin can also generate the token for another Admin. A user whose custom role includes Manage Apps & Integrations can generate tokens too, but the token still has to belong to an Admin
- Ask the Opal team to enable the Guru integration for your organization
Configuration steps
1. Generate a user token
Guru’s steps are in Leveraging Guru’s API.- In Guru, go to Manage > Apps & Integrations, then open the API Access tab. You can also open API Access directly.
- Select Generate User Token and enter the name of a Guru Admin. To generate a token for a different Admin, select Generate a new user token.
- Copy the token and store it where your team keeps secrets. Guru shows it when you generate it. If you need it again, reissue it with the circular arrow on that page. The trash icon revokes it.
Use a user token. A collection token is read-only and only sees one collection, so the connection check fails.
2. Create the Guru app in Opal
In Opal, go to Inventory > + App and select Guru. Fill in the following fields:
Opal checks the email and token when you save the app.
You can change Remove users from Guru and Sync Knowledge Agents later from the app’s Setup tab. Replacing the token is done there too.
3. Import groups, collections, and the workspace
After you save the app, on the app’s Assets tab, select Import assets. Import the groups people should be able to join, the collections you want to assign, and Guru Workspace. Turn on requests for the groups. If you set Sync Knowledge Agents totrue, import the Knowledge Agents as well.
Opal pulls access only for imported items, so members and group roles appear after the next sync. A person gets collection access by joining a group that already has a role on that collection. Assign that role to the group on the collection.
Leave requests off for Guru Workspace. Opal lists Admins there and can’t change the role.
The Setup tab lists the reads the token must be allowed to make: Read members, Read groups, and Read collections. Read Knowledge Agents appears when sync is on. A failed check means the token’s user can’t see that data.