Concepts and referenceWhat an agent can see

What an agent can see

How Gurusup decides what a connected assistant can see and do, how categories and restricted sources scope it, what leaves Gurusup in a tool result, and how agent accounts differ.

An assistant connected to Gurusup does not have its own view of your organization's memory. It sees what the account it signed in with is allowed to see, and nothing more.

Access follows the signed-in account

When you connect your assistant, you sign in to Gurusup in your browser (see Setup and authentication). From then on, every request the assistant makes carries your organization and your account. One connection is one person in one organization.

Your role comes from your membership in Gurusup, not from the sign-in. If an admin changes your role or your access, the next request follows the change.

That has three consequences.

  • Two people with the same assistant can get different answers. Each sees what their own account allows.
  • The assistant cannot see more than you can. Changing assistants does not widen access.
  • Gurusup does not show you what you cannot see. If nothing you are allowed to see answers the question, the assistant is told to say that it could not find anything, not to guess. See Sources and citations.

What scopes the results

Every read tool (ask_company_memory, search_company_memory, retrieve_company_memory) filters before it returns anything. Two layers decide what passes.

LayerSet byWho reads it
CategoriesAn admin, per person and per agent account under TeamAn admin reads every category. A member or an agent account reads only the categories an admin granted.
Restricted sourcesAn admin, per source under SourcesOnly the people picked for that source. Admins are not included unless they are picked. Agent accounts are not offered in the list. A category grant does not open a restricted source.

A few rules follow from those two layers.

  • Knowledge built from several sources comes back only if you can read every source behind it.
  • A source restricted after it was connected covers only what arrives afterwards. Knowledge Gurusup learned before keeps its category permissions.
  • The subject you give a question focuses the search. It never widens or narrows access.
  • Skills follow categories: the assistant lists and loads only skills whose categories you can read.
  • Asking a person cannot be used to get around access. Gurusup only sends a question that depends on restricted knowledge to people who can read it.

For the full model and its limits, see Permissions model and Restrict a source.

What happens when access is denied

  • Nothing matches. The answer comes back with no pages, and the assistant is told to say it found nothing.
  • The matches are not readable for you. The answer also carries an internal note saying so. The assistant is told not to pass internal notes or scores on, so what you normally read is that it found nothing.
  • The organization has sources but you can read none. Asking and searching fail with "You don't have access to any sources in this organization. Ask an organization admin to give you access." Ask an admin to grant you a category or add you to a restricted source. See MCP troubleshooting. If the organization has no sources, or all of them were revoked, there is no error: the answer comes back with no pages.
  • Your access changed during a question. The call fails with "Knowledge access changed while processing this request. Please retry." Ask again. See MCP troubleshooting.
  • You publish a skill for categories you cannot access. Gurusup refuses it with 400.
  • The memory is not ready. init returns a notice that Gurusup is not ready to answer, and reads fail with 503 until the build has finished. See MCP troubleshooting.

Who can do what

ActionWho
Ask, search, open pagesAny member or agent account, within what they can read
Use skillsAny member or agent account, for skills in their categories
Save knowledgeAny member or agent account. The assistant is told to do it only after you ask or confirm.
Submit a skillAny member or agent account. The skill waits for an admin to approve it.
Ask a person for missing informationAny member or agent account. The assistant previews the contact first. Only people set up as Gurusup contacts (by themselves or by an admin) or external contacts can be asked.
Report a problem or send feedbackAny member or agent account. It records a note for the Gurusup team and changes nothing in Gurusup.
Operate Gurusup with learn and the operation tools, such as sources_connect (on the ?profile=catalog address only)Any member or agent account, with the operations their role allows. Admin-only operations, such as building the memory, managing people or approving skills, are refused. See What each role can do.
Approve a skill, review questions under Queries, manage Team, restrict a source, build the memoryAdmins, in the app, or through an assistant with the operation tools.

No tool edits or deletes knowledge that is already saved. Knowledge saved through an assistant cannot be edited or removed from the app afterwards.

What leaves Gurusup

Gurusup sends the assistant only what its tools return, and the assistant's provider then handles that content under its own terms. Depending on the tool, a result contains:

  • excerpts from pages of Brain, the facts behind them, and each page's title and link (ask_company_memory),
  • short snippets of matching pages, with their titles and links (search_company_memory),
  • the text of a page or passage the assistant asks for, with its title and link (retrieve_company_memory),
  • the full text of a skill you can use (skills_get) and the list of skills you can use (init),
  • the name of the contact Gurusup would ask, the channel and the question it would put to them, when a preview runs (request_human_info),
  • your email and an opaque profile ID (get_profile).

Gurusup also receives what the assistant sends: your question, anything it saves, and the text of a report or feedback. Saved knowledge is stored with your account, email and role. Reports include your organization and account, what the assistant wrote, and the name and version of the assistant app. See Tools reference.

Agent accounts

Agent accounts are for software that uses Gurusup without a person signing in, such as an internal script or a service. They are not how you connect your own assistant like Claude or ChatGPT: that uses the browser sign-in described in Setup and authentication.

An agent account is a machine account, not a person. Admins create and manage them under Team, in the Agents section. Members do not see Team.

An agent account:

  • has a name and an email. The email cannot already be used by another account, or Gurusup shows "That email already belongs to another account. Use a different email for the agent.",
  • is always a Member, never an admin, whatever its key says,
  • gets its own knowledge categories, set the same way as for people,
  • cannot be picked for a restricted source in the app, so it does not read restricted sources,
  • uses API keys instead of signing in. The software sends the key to the Gurusup MCP server as a bearer token (an Authorization header with Bearer and the key), and then uses the same tools as a person,
  • uses one seat, like a person.

For the steps to create one, manage its keys and delete it, see Agent accounts.

Because an agent account is always a Member, it can never manage Team or approve skills, and it reads only the categories you pick. Give each agent only the categories it needs, and revoke a key you think has leaked. The app says a revoked key loses access immediately. The MCP server remembers a key it checked for up to five minutes, so a revoked key can keep working for up to five minutes after you revoke it.

If Gurusup says "Agent accounts aren't enabled for this organization yet. Contact support to turn them on.", contact support.