> ## Documentation Index
> Fetch the complete documentation index at: https://docs.prisme.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Connected accounts
> Connect and disconnect the accounts an agent uses to read on your behalf
Some agents draw on knowledge bases fed by an external source — SharePoint, Google
Drive — where **per-user access control** is switched on. Those agents do not serve the
same documents to everyone: each answer is built from what *you* are allowed to open in
the source system.
To do that, the agent needs an account of yours to check against. This page explains
when you are asked for one, and how to take it back.
## Being asked in a conversation
The first time an agent reads such a base in a conversation, it asks — **before running
any search**:
> Connect your Sharepoint Next account so the agent can search the knowledge base with
> your own permissions.
Connect, and the search runs with your full scope. Dismiss the card, and the search runs
anyway, over the documents that are not restricted. Nothing is ever blocked; the card is
an invitation, not a wall.
The request is raised before the search, never after — so it never depends on what you
asked. A card appearing after a question would, by appearing, reveal that matching
documents exist that you may not read.
You are asked at most once per connector per conversation, and only one card is in
flight at a time even when several bases are involved.
## Managing accounts from the input menu
You do not have to wait to be asked. The menu next to the message box lists the
connectors the agent's knowledge bases rely on, each showing the service by name, with
**Connect** or **Disconnect** beside it.
This is also where you revoke an access you granted earlier — during a conversation that
has since ended, for instance.
## One account per use
This is the part worth understanding, because it is visible and it surprises people.
A credential belongs to a **use**, not to a person:
| Use | What it is for | Who connects it |
| ------------------ | ----------------------------------------------------------- | ------------------------------ |
| **Knowledge base** | Feeding the base — the scheduled synchronization replays it | Whoever sets up the connection |
| **Agent** | Reading, on your behalf, while you chat | Each reader, for themselves |
So connecting SharePoint for a knowledge base does **not** connect it for an agent, even
if it is the same person and the same SharePoint account. You will be asked twice, once
per use.
This is the point of the split. Without it, someone who set up a base, then tested their
own agent against it, and finally disconnected from the chat would have taken the
nightly synchronization down with them — silently, and for everybody.
Disconnecting from the chat therefore drops the reading credential and nothing else. The
base keeps synchronizing. The reverse holds too: disconnecting a connection from the
Connectors page leaves your chat access alone.
## What the agent knows
An agent never learns that documents it cannot show you exist. A search where everything
was filtered out returns exactly what a search that matched nothing returns, so there is
nothing for it to hint at — not in its answer, not in its sources.
## Troubleshooting
### The agent finds nothing, or much less than expected
Check whether you connected your account when it asked. Without it, only unrestricted
documents are searched. Open the input menu to connect, or start a new conversation to
be offered the card again.
### I connected, and I am asked again in the next conversation
Expected: the question is settled per conversation. The account itself is remembered —
the second time, connecting takes a click and no sign-in, unless the provider has
expired your session.
### I disconnected from the chat and my knowledge base stopped syncing
That should not happen, and the two credentials are separate precisely so it does not.
Report it, mentioning the connector and whether both were connected with the same
account.
## Next Steps
Feed a knowledge base from SharePoint or Google Drive
Control what an agent is allowed to do on your behalf