Before anyone in your organisation can connect an AI assistant to Diri, two things are needed: an agreement with Cyrigo, and an administrator who turns AI access on. For what bring your own AI is, see Bring your own AI.
Bring your own AI is activated by Cyrigo, under an agreement with your organisation. Contact support@cyrigo.com. We go through which AI assistants you plan to use and, for Microsoft Copilot, help your Microsoft 365 administrator with the setup.
Until it is activated, the Import & AI > Tokens tab says that your organisation is not part of it yet, and anyone who tries to connect an AI assistant is told the same.
Before you start, check your own side too:
When Cyrigo has activated it, a Diri administrator turns it on:
All settings are under Import & AI > Tokens > Token policy, and are visible to administrators only.
| Setting | What it decides |
|---|---|
| Who can make tokens | Everyone or Nobody. Covers both AI assistants connected by signing in and personal access tokens. Choosing Nobody while some are in use asks whether to revoke them now or keep them working. |
| Which AI clients may sign in | Any kind, or only the kinds you tick: Claude, Microsoft Copilot, ChatGPT, Programs on your users' computers (such as Claude Code or Cursor) and Other services. For example, allow only Microsoft Copilot if that is the assistant your organisation has approved. A connection of a kind you no longer allow stops at its next request. |
| Highest reach | Which existing records the AI's packages may change. Own records: those the user owns, created or is responsible for. Colleagues' records too: any record the user may edit. A person still reviews every change before it is published. |
| Full control text | Whether the AI sees the full text of framework controls, or only their codes and titles. The full text lets it propose evidence that fits the control. |
Under All tokens in this organisation, administrators see every connected AI assistant and token: who owns it, what it can do, its reach and when it was last used. Click Revoke to stop one at its next request.
Users see their own connections under Your tokens, and can revoke them there. A connection ends by itself after 90 days without use, and after 12 months in any case; the user then connects again.