Restrict a source to specific people
Keep what Gurusup learns from a source readable only by the people you pick, for example one team's Slack channel, its CRM or its own documents.
Admins only, except for files a member uploads: the member makes the same choice for those, see Upload content. Use Restricted to keep a team's knowledge within the team, or Private to let only yourself read it. Both override role and categories, so admins read the knowledge only if they are included.
Every source has one of three settings:
| Knowledge access | Who reads it in Brain |
|---|---|
| Default access | Everyone, according to what they are already allowed to see: admins every category, members and agent accounts the categories an admin granted them. |
| Restricted | Only the people you pick. Administrators are not included unless you pick them. |
| Private | Only you. Administrators are not included. |
Gurusup learns from a restricted source in its own space, so what it learns there does not mix into the pages the rest of the organization reads.
Before you start
- Restrict when you connect. Restricting later does not hide what Gurusup already learned from the source.
- Pick people one by one. There are no groups, and a member's Department grants nothing. When someone joins the team, add them by hand.
- Only active members can be picked. Invitations appear once accepted. Agent accounts are never offered.
- Admins are not included unless you pick them. That includes you.
What a source is, per app
You restrict a whole source, never one page or one deal.
| What you connect | The setting covers | When you can set it |
|---|---|---|
| Notion, HubSpot and the other connectors | The whole connected account | When you connect it, and later from Sources |
| Slack | Every channel the app joins after you connect the workspace. Each channel is a source and starts with that access. | When you connect the workspace. Not per channel afterwards. |
| Webhook | That webhook | When you create it, and later under Knowledge access on its page |
| File upload | Local Uploads, which holds every file an admin uploads. A member's files go to a source of their own for each choice. | With your first upload, and later in the Upload files dialog or from the Local Uploads row. For an admin, every file shares it, the ones already uploaded too. A member chooses again for each upload. |
To keep one team's documents apart, send them through a source of their own, such as a webhook created for that team.
Restrict a source when you connect it
Start connecting
On Sources, connect the app, create the webhook, or start your first upload.
Choose Restricted
Under Who can read it (Knowledge access for a webhook or an upload), open the Access mode menu and choose Restricted. Gurusup says "Only the people you choose. Administrators only if you choose them."
Pick the people
Tick each person. With more than eight teammates, Search members by name or email appears above the list, with a count such as "3 selected" under it. With nobody picked, Gurusup warns "No members selected. Nobody will be able to read this restricted knowledge."
Finish connecting
Connect as usual. You should see "Gurusup applies this from the first item it reads." under the list, next to a How access works link.
What the setting covers depends on what you connect.
| You are connecting | What Gurusup says |
|---|---|
| An app | "Gurusup applies this from the first item it reads." For Slack, that means each new channel starts restricted to the same people. Afterwards you manage each source separately on its own page. |
| Your first upload | "These settings apply to Local Uploads, including future files." |
| Later uploads | "Applies to every uploaded file, including the ones already uploaded." The dialog shows the current access and you can change it there. |
Restrict a source that is already connected
You can change access for a connected app source, a webhook, or Local Uploads under Knowledge access on its page. Slack channel access cannot be changed from Sources after the channel is created. You can also edit Local Uploads access in the upload dialog; changes apply to every uploaded file.
Open the source
On Sources, open the source's page and find Knowledge access. With several accounts of one app, click the account's name first.
Choose Restricted and pick people
Open the Access mode menu, choose Restricted and tick the people who can read it.
Check that it saved
There is no save button: each change saves as soon as you make it. You should see "Knowledge access saved." If it fails, Gurusup says "Knowledge access could not be saved. Your previous settings still apply; try changing access again."
Only what arrives after you save is restricted. Gurusup says "Restricting this source applies to future ingestions. Knowledge Gurusup already has keeps its existing category permissions." If a source must be private from its first message, restrict it when you connect it.
Example: keep HubSpot to Sales
Your sales team wants Gurusup to answer "Which open deals mention the pricing objection we discussed in Slack last week?", but deal values should stay with Sales. You connect HubSpot from Sources, choose Restricted and pick the two account executives and the head of sales.
| Person | Reads what Gurusup learns from HubSpot |
|---|---|
| The two account executives and the head of sales (picked) | Yes, including answers that join HubSpot with Slack or Notion they can also read |
| A marketing member who has the sales category | No. Categories do not open a restricted source, and the source is not listed for them on Home or Sources. |
| The CEO, an admin who was not picked | No. They still see the HubSpot source on Home and Sources and can open its page and add themselves under Knowledge access. |
| An agent account with the sales category | No |
| Anyone, for a memory Gurusup built from HubSpot and a Slack channel together | Only if they can read both sources |
In Queries, the CEO does not see questions that drew on HubSpot until someone picks them.
Change who can read it
Open the source's Knowledge access, then tick or untick people. Each change saves at once. Gurusup says "Changes apply to all previously restricted content from this source." The new list counts from the next question anyone asks.
Removing a member from the organization takes them off every restricted source. If they were the only person picked, nobody reads the source until you pick someone else. Making someone an admin does not add them: pick them here.
Go back to default access
Open the Access mode menu and choose Default access. A dialog titled Switch to default access says "This source goes back to what each person is already allowed to see, so more people than the ones you picked will read it. You lose your list of people, and you can't undo what anyone reads." Click Confirm.
What a restricted source protects
The list holds everywhere Gurusup answers from:
| Where | Who gets it |
|---|---|
| Answers, searches and pages through any assistant, and skills that depend on that knowledge | Only people picked |
| Knowledge Gurusup built from several sources | Only people who can read every source it came from |
| Questions Gurusup sends to colleagues, such as a conflict about restricted knowledge | Only people picked |
| Queries | Admins who were not picked do not see questions that drew on the source |
| The source's name and contribution on Home and Sources | Only people picked, and admins. Members who were not picked do not see the source in their lists or totals. |
It does not hide:
- That the source exists, from admins. Every admin sees it on Home and Sources, with its name, logo and contribution. Members who were not picked do not see it: it is left out of their lists and totals. Name sources with admins in mind, for example a webhook called "People team".
- What arrives, on Ingest. Every admin sees each item from the source on Ingest, with its title and what changed in memory, even admins you did not pick.
- What Gurusup learned before you restricted it. See Restrict a source that is already connected.
- Permissions in the app itself. Gurusup does not copy who can see a channel or a page in Slack or Notion. The people you pick in Gurusup are the ones who read it. See Permissions model.
If something does not work
| Message | What to do |
|---|---|
| "No members selected. Nobody will be able to read this restricted knowledge." | Pick at least one person, or save knowing nobody reads it. |
| "No teammates in your organization yet." | There is nobody to pick. Click Invite teammates (it opens the Team page), then come back. |
| "Access changed elsewhere. Review the latest settings before saving again." | Someone changed the source while you edited. Your changes are discarded: review the list, redo them and save. |
| "Could not save knowledge access. Try again." | Try again. If it keeps failing, contact support. |