Getting StartedSet up Gurusup for your company

Set up Gurusup for your company

A checklist for an admin's first week after the Quickstart. Connect the main sources, decide who reads what, bring your team in and keep an eye on what Gurusup learns.

This page is for the admin who has finished the Quickstart. Admins only. It walks you through the first week: each item says why it matters, where it is in the app and which page has the details.

You don't have to do it in one sitting. The order matters most at the start: decide access before you connect, and grant categories before you tell people to ask.

Before you start

  • You are an admin of the organization, and its memory is built or building. See the Quickstart.
  • To invite anyone, your plan needs free seats. Free includes one seat, which is yours. See Plan and usage.

The checklist

Decide who reads each source

Why: what Gurusup already learned keeps the access it had, so a source that must stay within one team has to be restricted before Gurusup reads it.

Each source has one of three settings:

Knowledge accessWho reads it in Brain
Default accessEveryone, according to what they are already allowed to see: admins every category, members and agent accounts the categories an admin granted them.
RestrictedOnly the people you pick. Administrators are not included unless you pick them.
PrivateOnly you. Administrators are not included.

Where: when you connect an app from Sources, the connect dialog asks Who can read it. Afterwards, change it under Knowledge access on the source's page. Apps you connected during setup start with Default access. Who can see a channel in Slack or a page in Notion does not carry over.

Details: Restrict a source to specific people.

Connect your main sources

Why: Gurusup answers only from what it has read. The best answers come from questions that join several tools, so connect the places where your team decides and records things, not only one.

ConnectWhy early
SlackGurusup reads only what is posted after the app joins a channel. It cannot import older messages, so every day without it is lost. Run /invite @GuruSup Brain in each channel.
Notion and HubSpotYour written decisions and your deals. They start from the moment you connect. Bring in earlier pages and deals with Import history under History on the source's page.
Holded, ClickUp, Asana, Linear, Granola, tl;dv, Factorial, Zernio, monday.com, AttioThey start from the moment you connect. Bring in past work with Import history under History on the source's page.
SesameIt starts from the moment you connect and has no Import history.
Mintlify, Documentation.AIGurusup checks your docs when you connect but only learns the public pages that change after that, and checks again every 6 hours.

Everything a source brings in uses your usage.

Where: Sources, then Connect source.

Details: Connectors overview.

Invite your team and choose roles

Why: each person asks Gurusup from their own assistant, under their own access.

Most people should be a Member. Make someone an Admin only if they need to manage sources, people or billing. An admin reads every category.

Where: Team, then Invite. Enter the Email, pick Member or Admin in Role, and click Send invite. A pending invitation holds a seat.

Details: Invite your team and Roles.

Grant categories

Why: a new member reads no category, so until you grant one their assistant gets nothing back.

Where: Team, click the member's row, then under Access click each category to grant it. The Access column updates. This needs a built memory.

Details: Give a member access to categories.

Set up Gurusup contacts and external contacts

Why: when Gurusup lacks an answer, it can only ask people who are set up as contacts. With none, it tells the person asking that there is no team contact available.

Where: Team, click the member's row, then turn on Gurusup contact in the Contact section. A notice at the top of Team says how many members need a contact method, with Show them. For partners without an account, open the External contacts tab of Team and click External. Slack methods need Slack connected first.

Members can set up their own contact under Profile settings.

Details: Gurusup contacts and external contacts.

Get everyone's assistant connected

Why: Gurusup has no chat window. People use it only through an assistant.

Where: Gurusup MCP in the sidebar, for you and for everyone. Members see the same steps on their Welcome screen. Send new members Get started as a member.

Details: Setup and authentication.

Add skills

Why: a skill gives every assistant in the organization the same instructions for a task. Each new skill waits in Pending and does nothing until an admin approves it.

Where: Skills, in the Brain group of the sidebar. Use Import skills to add SKILL.md files, then open each one in Pending and click Approve. Check that each skill has a description: an assistant picks a skill by reading it.

Details: Skills.

Watch Ingest and resolve Conflicts

Why: Ingest tells you whether what you connected arrived. Conflicts holds the cases where two sources disagree and Gurusup cannot tell which is right. It does not notify you, so check it.

Where: Ingest and Conflicts, in the Brain group of the sidebar. On Ingest, open the Failed tab. On Conflicts, open the Open tab, pick what is true or ask a colleague.

Details: Follow ingestion and Resolve conflicts.

Review Queries

Why: you see who uses Gurusup, what they ask, and whether Gurusup found something to answer with. A topic that keeps coming back empty points to a missing source or a missing category.

Where: Queries, in the Brain group of the sidebar.

Details: Review queries.

Check usage and plan

Why: reading new content spends usage, and asking questions does not. When the month's usage runs out, new content waits as Paused until it renews or you upgrade.

Where: Usage and Billing, in the menu at the top of the sidebar (click your organization's name).

Details: Plan and usage and Plans and quotas.

Optional: create agent accounts

Why: software that needs Gurusup, rather than a person, gets its own account with its own categories and API keys. Each one takes a seat.

Where: Team, open the Agents tab, click API key agent, then Create & mint key. The key is shown once.

Details: Agent accounts.

Disconnect and Remove source do not delete what Gurusup learned, and the app has no other way to delete it. Connect only what you want in your memory, and restrict it before Gurusup reads it. To have knowledge removed, contact support.

Check that it worked

  • Sources lists each connected source under Company sources, with its status and its Contribution, and shows Total memories at the top.
  • Team shows your people as Active, each with categories in the Access column, and no notice about members without a contact method.
  • Ingest has nothing left on the Failed tab that you have not looked at.
  • A member asks a question that joins two sources, and the answer names pages from both.

If something does not work

MessageWhat to do
Bring your whole team in when you click InviteEvery seat is taken. Cancel a pending invitation or upgrade. See When the seats are full.
"Couldn't update grant. Category access can't be changed until Gurusup has finished building your company knowledge. Contact support if this keeps happening."Wait for the build to finish, then grant categories again.
"No members selected. Nobody will be able to read this restricted knowledge."Pick at least one person on Knowledge access.
"A plan change is scheduled. Seat and role changes are temporarily unavailable."Wait until the plan change applies.