Language: English
Every AI assistant you connect to ActivityInfo appears on the “Authorized Applications” page of your account settings, together with what you granted it and when it last used that access. Review the list from time to time, and revoke anything you no longer use.
The list is your own. It shows the applications you have authorised, not those authorised by your colleagues.
Review the applications you have authorised
- Click on the user profile and select “Account settings.”
- Select “Authorized Applications” on the left navigation panel.
Each entry shows the name of the application and the scope you granted. Select an entry to see its details in the right side panel:
| Detail | Meaning |
|---|---|
| Scope | “Read-only” if the application can only view your data, “Read & Write” if it can also make changes |
| Authorized on | The date you approved the application |
| Last used | The date the application last used its access. A date long in the past is a good reason to revoke it |
An application that supplied no name of its own is listed as “Authorized Application”. The name is supplied by the application and is not verified by ActivityInfo, so treat it as a label rather than as proof of what the entry is. If you do not recognise an entry, revoke it.
If you have not connected anything, the page reads “You haven't authorized any applications.”
Revoke an application's access
- Select the application in the list.
- Click “Revoke access” in the right side panel.
- Confirm when ActivityInfo asks “Are you sure you want to revoke this application's access? It will no longer be able to access your account.”
ActivityInfo confirms with “The application's access has been revoked.”
The application loses access at once. Its access token and refresh token both stop working, so an assistant that was connected can no longer read or change anything in your ActivityInfo account. Revoking does not undo changes the assistant already made, and it does not remove any data it already sent to the AI provider.
To use that assistant again, connect it again and approve it on the “Authorize application” screen. It appears in the list as a new entry.
What revoking does not cover
Revoking is per user and per application. It is one of three separate controls, and it is not always the one you want:
| To do this | Use this |
|---|---|
| Stop one assistant that you connected | Revoke the application here |
| Stop every assistant from reaching one database, for all users | Turn off the MCP server for that database. See Enabling the MCP server for a database |
| Stop one colleague's access to a database, including through an assistant | Change or remove that user's role in the database |
Revoking your own authorisation has no effect on a colleague who has connected the same assistant with their own account. When someone leaves your organisation, remove their ActivityInfo user rather than relying on them to revoke anything.
Change what an assistant is allowed to do
There is no way to widen or narrow the scope of an authorisation that already exists. To change from read access to also allowing changes, or the other way around, revoke the application and connect it again, choosing the scope you want on the “Authorize application” screen.