Security and privacyPermissions model

Permissions model

How roles, categories and restricted sources control what people and agents can see in Gurusup, and what they do not do.

For admins and security reviewers. Gurusup decides what someone can read in layers. The role decides which screens and actions they get. Categories are the default for knowledge, and they group it by business function. A restricted source overrides them: only the people picked for it can read it. An admin picks them, or the member who uploaded the files.

LayerSet byDecides
Role (admin or member)An admin, under TeamWhich pages and actions someone gets, and whether categories apply to them
CategoriesAn admin, per person or agent accountWhich knowledge from sources with default access someone reads
Restricted sourceAn admin, per sourceWho reads that source's knowledge, in answers and in the app, and which members see the source listed. Nobody else, admins included. Every admin still sees the source and each arriving item's title on Ingest.

Roles

Gurusup has two roles: admin and member.

RoleKnowledge access
AdminReaches every category while the account is active. Reaches a restricted source only if picked for it.
MemberReaches only the categories an admin has granted to that person, and the restricted sources they were picked for

Only admins manage people, roles, categories, and connected sources and their access. A member chooses only who reads the files they upload and who reads their own tl;dv connection, while an admin lets members connect their own account. The checks run on the server, not only in the app. The full list is in Roles.

Categories

Gurusup sorts what it learns into categories that match business functions. There are eleven: general, marketing, sales, finance, product, engineering, operations, customers, hr, legal and leadership. When Gurusup answers a question, it only uses knowledge from categories the asker can reach.

An admin grants a member access to a category from the Team page. A category that has no content yet starts closed to members when its first page arrives.

Restricted sources

An admin can set a source to Restricted and pick the people who can read it, or set it to Private so only the person who sets it can read it. Administrators are not included unless picked. A member who uploads files can choose Restricted or Private for them too. Then:

  • Only those people read what Gurusup learns from it. A category grant does not open it, and admins are not included unless picked.
  • With Private, only the person who set it can read what Gurusup learns from it. The source is stored as Restricted with that person's own account selected. Another admin who opens it sees Restricted with that person selected.
  • Gurusup learns from it in its own space, so it does not mix into the pages the rest of the organization reads.
  • Knowledge built from several sources is readable only by someone who can read every one of them.
  • Questions Gurusup sends to colleagues about that knowledge only go to people who can read it.

Restricting a source that is already connected only covers what arrives afterwards. What Gurusup learned before keeps its category permissions. Knowledge access is also available for sources without a connection, including webhooks and Local Uploads. See Restrict a source to specific people.

Assistants

An assistant connected to Gurusup acts as the person who signed in with it. It reads what that person reads, through the same layers, and nothing more. Changing assistants does not widen access. An assistant can also run operations in Gurusup for that person, such as connecting a source, but only the ones that person's role allows, and Gurusup checks the role again on every call. See What an agent can see.

Agent accounts

Agent accounts are machine accounts that use a static API key. They always have the member role. Their knowledge access is set by the same categories as people, and an admin chooses which categories each agent account can reach. Agent accounts are not offered when an admin picks people for a restricted source.

A revoked key can keep working for up to five minutes, because Gurusup remembers a checked key for that long. Revoke a leaked key straight away and expect that short delay. Deleting the agent account has the same delay: its keys can keep working for up to five minutes.

When someone leaves

When an admin removes a member, Gurusup deletes their category grants, takes them off every restricted source and deletes their Gurusup contact. Their access ends in the app and through their assistant. Signing in again does not bring them back: only a new invitation, accepted after the removal, does.

What they saved to Brain through their assistant stays.

What these do not do

  • Categories are business-function groups, not walls between individual people. To keep something to named people, restrict its source.
  • A restricted source is restricted as a whole. For Notion, HubSpot and the other connectors, that is the whole connected account, so you cannot restrict one page or one deal on its own. For Slack, the access set when you connect the workspace applies to every channel added afterwards.
  • A restricted source is hidden from members who were not picked, not from admins. Members see only the sources they can read on Home and Sources, and the totals leave the others out. Admins see the full list, so they can manage who reads each source, and they see each arriving item's title on Ingest.
  • The department set on a member grants nothing. It is a label.
  • Gurusup does not copy permissions from your source apps. If a page in Notion or a channel in Slack has its own access rules, Gurusup does not read or apply them. What matters is which pages you share, which channels the app has joined, and the access you set in Gurusup. See Connectors and scopes.