Roles
Who can open which page, do which action and read which knowledge in Gurusup, for admins, members, agent accounts and connected assistants.
For admins setting up an organization, members wondering why something is missing, and reviewers checking access.
An organization has three kinds of account.
| Account | What it is | How it signs in |
|---|---|---|
| Admin | A person who runs the organization: sources, people, plan | Browser sign-in, and the same account in their assistant |
| Member | A person who uses Gurusup through their assistant | Browser sign-in, and the same account in their assistant |
| Agent account | A machine account for software, always with the Member role | An API key, never the browser |
What someone can read is decided by their role, the knowledge categories an admin granted them, and whether a source is restricted to named people. Can this person read it? shows the order Gurusup checks them in.
To change someone's role, see Members and roles. For agent accounts, see Agent accounts.
What each account can do
| Page | Admin | Member | Agent account |
|---|---|---|---|
| Welcome | Until you have gone through it once | Until you have gone through it once | No app access |
| Overview (Get started for admins until someone starts building the memory) | Yes | Yes | No app access |
| Gurusup MCP | Yes | Yes | No app access |
| My requests | No. Admins follow requests under Ingest. | Yes | No app access |
| Sources and Catalog | Yes | Yes: the company sources they can read and the catalog, with Upload files and Import wiki. They cannot connect or manage company sources, except their own tl;dv key while an admin lets members connect their own account. | No app access |
| Ingest | Yes | No | No app access |
| Conflicts | Yes, every conflict | Yes, only the conflicts whose source and categories they can read | No app access |
| Skills | Yes | No | No app access |
| Queries | Yes | No | No app access |
| Team, in the organization menu | Yes | No | No app access |
| Usage, in the organization menu | Yes | No | No app access |
| Billing, and Plans from there, in the organization menu | Yes | No | No app access |
| Organization settings (General) | Yes | No | No app access |
| Profile (from Profile settings in the menu under your name) | Yes | Yes | No app access |
A member who types the address of an admin page is sent back to the home page. Members can open Sources, Catalog and Conflicts. A source row opens a page with only the About tab, and members cannot manage it, except their own tl;dv connection. In Catalog, each row has a View button or a Connected mark, and an app's page says "Only admins can connect (app). Ask an admin to set it up." Until an admin builds the organization's memory, pages such as Sources, Ingest, Conflicts, Queries and My requests show "Available once your memory is built" in place of their content. Skills (admins only) shows the real list of skills as soon as the organization has at least one, and shows that message only while there are none.
| Action | Admin | Member | Agent account |
|---|---|---|---|
| Edit your own name and profile picture | Yes | Yes, under Profile | No |
| Set up your own Gurusup contact | Yes | Yes, under Profile | No |
| See the categories you can read | All | Not listed in the app. An admin sees them in your row in Team. | No |
| Follow the requests Gurusup sent to colleagues for you | Under Ingest, for the whole organization | Under My requests, your own | No |
| Build the organization's memory for the first time | Yes, with Continue in setup, or by itself once content is ready | No | No |
| Connect, reconnect, disconnect and remove sources | Yes | No | No |
| Upload files and import a wiki from Sources | Yes | Yes. A member's files go to their own upload source, grouped as Local Uploads. | No |
| Create webhook sources, choose what to import from a connected app | Yes | No | No |
| Restrict a source to specific people | Yes | No | No |
| Settle conflicts | Yes, every conflict | Yes, the ones they can read | No |
| Ask a contact about a conflict | Yes | No | No |
| Approve, edit, archive and import skills | Yes | No | No |
| See questions asked under Queries | Yes, except questions that drew on a restricted source they are not on | No | No |
| Invite people, resend or cancel invitations | Yes | No | No |
| Change someone's role | Yes, not their own | No | No |
| Remove someone from the organization | Yes, not themselves | No | No |
| Grant knowledge categories to people and agent accounts | Yes | No | No |
| Set someone's name, avatar or department | Yes | Only their own name and avatar | No |
| Set up Gurusup contacts for others and external contacts | Yes | No | No |
| Create agent accounts, mint and revoke their keys, delete them | Yes | No | No |
| See usage, billing and plans, and change plan | Yes | No | No |
| Rename the organization | Yes | No | No |
A connected assistant acts as the account it signed in with. It can never do more in Gurusup than that account can.
| Tool | Admin | Member | Agent account | What decides the result |
|---|---|---|---|---|
init, health, get_profile | Yes | Yes | Yes | init lists only the skills in categories the account can read |
ask_company_memory, search_company_memory, retrieve_company_memory | Yes | Yes | Yes | The account's knowledge access, see below |
start_company_memory_activity | Yes | Yes | Yes | Nothing, it only groups calls |
add_company_knowledge | Yes | Yes | Yes | Saved knowledge can't be viewed, edited or removed from the app afterwards |
skills_get | Yes | Yes | Yes | Only skills in categories the account can read |
skills_publish | Yes, waits for review like anyone's | Yes, waits for an admin to approve it | Yes, waits for an admin to approve it | Refused for categories the account can't read |
request_human_info | Yes | Yes | Yes | Only people set up as Gurusup contacts or external contacts, and only people allowed to read the knowledge behind the question |
report_issue, send_feedback | Yes | Yes | Yes | Records a note for the Gurusup team, changes nothing in Gurusup |
learn, memory_progress and the operation tools, such as sources_connect (only on the ?profile=catalog address) | Yes, every operation | Yes, member operations | Yes, member operations | The role: the assistant is offered only the tools it allows, and Gurusup checks again when a tool runs. Building the memory, managing people and permissions, changing a skill's status and choosing what a source learns are admin only. See What each role can do |
Approving a skill, building the memory and managing people are for admins only, in the app or through an assistant. No tool edits or deletes knowledge that is already saved. See Tools reference and What an agent can see.
Knowledge from a source with default access
Every page of Brain belongs to one of eleven categories: general, marketing, sales, finance, product, engineering, operations, customers, hr, legal and leadership.
| Account | Reads |
|---|---|
| Admin | Every category, while the account is active |
| Member | Only the categories an admin granted them. A new member starts with none. |
| Agent account | Only the categories an admin picked for it. It starts with the ones chosen when it was created. |
An admin grants categories under Team. A member does not see their own list in the app. Until an admin grants one, their assistant gets nothing back.
Knowledge from a restricted source
An admin can set a source to Restricted and pick people, or choose Private so only they can read what Gurusup learns from it. Administrators are not included unless picked. Private is stored as Restricted with the setting admin's own account selected. A member who uploads files makes the same choice for those files: see Upload content.
| Account | Reads a restricted source |
|---|---|
| A member who was picked | Yes |
| A member who was not picked, even with the matching category | No |
| An admin who was not picked | No. Admins are not included unless picked. |
| An agent account | No. Agent accounts are not offered in the list. |
Knowledge Gurusup built from several sources is readable only by someone who can read every one of them. See Restrict a source to specific people.
What everyone sees
| Item | Who sees it |
|---|---|
| The list of sources on the home page and on Sources, with each source's name, logo and contribution | Admins: every source. Members: only the sources they can read. A restricted source they were not picked for does not appear, and is left out of the totals. |
| A member's own requests to colleagues | That member, and admins under Ingest |
| Questions people asked, under Queries | Admins only, minus questions that drew on knowledge they can't read |
| The department set on a member | Admins. It is a label and grants nothing. |
Through an assistant
An assistant sees exactly what its account reads, nothing more. Two people using the same assistant get different answers when their access differs. If nothing the account can read answers a question, the assistant is told to say it found nothing.
Sources connected by one person
Every connector documented today is connected by an admin for the whole organization, and follows the rules above.
Can this person read it?
Gurusup runs this check on every question, for every piece of knowledge it could return. A change to someone's access applies to their next question.
- Restricted comes first, and admins get no pass. An admin who was not picked does not read a restricted source. Agent accounts are never offered in the list.
- Restricting later only covers what comes next. Knowledge Gurusup learned from a source before it was restricted keeps its categories. Switching a source back to Default access puts its restricted knowledge under categories again.
- Knowledge built from several sources needs all of them. Someone reads it only if they can read every source behind it.
Plans
No page or action is locked by plan. Plans limit two things: usage and seats. Active members, admins, agent accounts and pending invitations each take one seat, so on Free, whose one seat is yours, you can't invite anyone or create an agent account until you upgrade. Pro has up to 3 seats. See Plans and quotas.
Rules about roles
- The person who creates the organization is its first admin.
- The organization always keeps at least one admin. The only admin can't be demoted or removed.
- You can't change your own role or remove yourself in the app. Ask another admin.
- An agent account is always a member: "Agent accounts are always members; their role can't be changed."
- While a plan change is scheduled, Gurusup turns down invitations, new agent accounts, role changes and removals until it applies.