No other source takes a connection. One Atlassian connection reads the same site’s Confluence, Jira and Jira Service Management. A website, a public help centre and a forum are read as a signed-out visitor reads them.
Read this first: what a connection can read, the assistant can quote
MITHUNAI reads everything the connection’s account can see, and then answers anyone who may ask your assistant. A page that only five people can open in Confluence can be quoted to every visitor of your website once it is read. So, for every connection:- Use an account that sees only what you are happy to share. In Confluence, a dedicated account with access to the right spaces. In Notion, share only the pages you want read. In GitHub, a token for the repositories you name and nothing else.
- Use a token that can only read. MITHUNAI never writes to any of these services, so it never needs more.
- Give the token an end date where the service lets you, and replace it before then.
Who can use connections
Only an owner or admin of your organisation. They can save, replace and delete connections, and connect a source that uses one. An editor can still sync and edit a source an admin connected.Where to find them
In the console, Settings → Connections lists every saved connection: its name, its service, the site it reads (for Confluence), how many sources use it, when it was added, last used, and when its token was last replaced. You can also save one while you connect a source, from the connection step of Connect source.What happens to the token
- It is stored encrypted, and it is never shown again: not to you, not to support, not in any list or API response. There is nothing to copy back out.
- It is sent only to the service it belongs to. A Confluence token goes only to the site you saved it with, and that site cannot be changed later. A Notion token goes only to Notion. A GitHub token goes only to GitHub.
- Every time a sync uses it, that is recorded in your organisation’s audit log.
Replace a token
When a token expires or you replace it at the service, open Settings → Connections, choose Replace token on the connection, and paste the new one. For Confluence you enter the account email and the new API token; the site stays the same. Every source that uses the connection reads with the new token from its next sync. Nothing else has to change.Delete a connection
Choose Delete on the connection. A connection that a source still uses cannot be deleted: the console tells you which sources use it. Remove those sources first, then delete the connection. Deleting destroys the token for good. An organisation can save up to 100 connections, and two cannot share a name.When a sync fails
MITHUNAI does not test a token when you save it. A wrong token shows up at the first sync.
Use the API
Connections have their own endpoints: Save a connection, List connections, Replace a token and Delete a connection. A source names one withconnection_id on Create a source.