The Copilot connection page in Daftra: connection address, managing and switching off connections
Copilot lets each user connect their own AI assistant (such as Claude or ChatGPT) to their Daftra account. The assistant works as the user: it sees what they see, does only what their permissions allow, and its actions carry their name. The Copilot page is where you find the connection address and setup steps and manage your connections.
Contents
Before you start
- Your role needs at least one Copilot permission from Roles.
- The assistant needs a plan that allows adding a custom connector (see the plans table on the page).
Page sections
With no connection, it shows: There is no active connection. Connect from your assistant by following the steps below; it will appear here once you approve it.
| Section | Content |
|---|---|
| My connection | Your connection state (On / Off), the Connected assistant, Last used, a Revoke button per assistant, and Revoke all. |
| The address to paste | Your account’s MCP address (your account address followed by /mcp) with a copy button. Paste it exactly; the /mcp at the end is part of it. |
| Choose your assistant | Step-by-step setup for Claude, ChatGPT and Gemini. |
| What your plan allows, before you start | A table of what each assistant’s plan allows; Daftra cannot tell which plan you have. Check the table against your own plan. |
| When it does not work | Known problems and what to do. |
| Administrator reference (Gemini Enterprise) | MCP address, Authorization URL, Token URL, Client registration URL and Scopes; no client secret is issued and sign-in must use PKCE with S256. |
Consent screen
- When connecting from the assistant, a Daftra page titled Connect [assistant] to Daftra opens (sign in first if needed).
- It states the assistant will act as you, with your permissions in your account, shows the name the application gave itself, and the permissions (scopes) it will get.
- Click Connect to approve or Cancel.
- If your role has no Copilot permission: Copilot is not enabled for your role, asking an account owner to grant Copilot access.
Switching off
- Click Revoke next to the assistant and confirm: Switch off this connection? The assistant will stop working with Daftra on its next request.
- Or Revoke all: Switch off all your Copilot connections? Your assistants will stop working with Daftra on their next request.
- Switching off takes effect immediately: the assistant stops working on its next request.
- Removing Copilot permissions from the role ends the connection within an hour at most (on token refresh).
Security
- Connection uses OAuth with the user’s own sign-in; no API key is needed.
- Connections are accepted only from known assistants (Claude and ChatGPT) or from software running on the user’s own machine.
- The access token is valid for one hour and refreshes automatically for up to 30 days; permissions are re-read from the role on every refresh.
- Daftra re-checks the user’s permissions on every request, so a Copilot connection can never exceed what the user has.
Error messages and fixes
| Message | Cause | Solution |
|---|---|---|
| Copilot is not enabled for your role | The user’s role has no Copilot permission | The account owner grants Copilot permissions to the role in Roles |
| The Copilot connection could not be switched off. Please try again. | Temporary failure while revoking | Try again |
| This redirect_uri does not belong to a known assistant. | Connecting from an unknown application | Use Claude, ChatGPT or software on your own machine |
Note: Modules currently available to the assistant: Sales, Inventory, Clients & CRM, Accounting, Purchasing, Work Orders & Workflow, and Finance. The Copilot page is on the testing branch and not yet on the release branch.
Frequently asked questions
Does the assistant see data I can’t?
No, it works with your permissions only.
Whose name do the assistant’s actions carry?
The user who connected it.
Can every user connect their own assistant?
Yes, each user enables the connection for themselves.
When does the assistant stop after switching off?
On its next request.
Why does the connection fail straight away?
Usually the address was pasted without /mcp.
Is Gemini supported?
Gemini steps are on the page but its support is not complete in this release.