Personal connections
Some tools need a sign-in: a Google Analytics 4 service account key, or a Notion, Atlassian or GitHub account you approve on the service’s own page (OAuth). In Cora these are personal connections. A connection belongs to the person who adds it, and Cora uses it only in the missions that person shares it in.
The examples use an invented company, Kestrel Cycles. Leah owns a Google Analytics 4 connection. Sam owns one too.
The rules
Section titled “The rules”- It is yours. You add a connection once, on the Connections page. Nobody else can use it, whatever their role.
- You give it to Cora, one mission at a time. You choose the missions where Cora may use it. In a mission that you have not shared it in, Cora cannot use it. Only you can share it or stop sharing it.
- One of each kind in a mission. Cora must never be unsure which account to use. If Leah’s Google Analytics 4 is shared in the Autumn launch mission, Sam cannot share his there. The mission page says “Leah’s connection”, and Sam can share his in other missions.
- You can only own one of each kind. To use another account, replace the key (or, for a connection made with the service’s sign-in, reconnect). For a service you connect with its own sign-in, the kind is the server’s address host, so two Notion connections are the same kind.
- Org admins can look, not use. They see every connection: who owns it, its kind and the missions it is shared in. For safety they can stop sharing it in a mission or remove it. They cannot read someone else’s key, test it or use it.
- Admins follow the same rule, plus one extra choice. An org admin’s own connection is personal too: they keep it to themselves, or share it with Cora mission by mission. Only an org admin can instead choose Make available to the whole organisation. It then works like a connector your organisation added: it is no longer shared one mission at a time, and mission members switch it on or off in each mission. Cora then uses the admin’s key for everyone, so admins should do this only for an account meant for the team. Where an organisation-wide connection of a kind is switched on in a mission, nobody can share a personal one of that kind there, and the other way round, so Cora still never has two to choose between.
- Leaving removes it. When you leave the organisation, your connections are removed, the keys are deleted, and Cora says so in each mission that used one.
- Cora names whose it was. When it matters, she says which connection she used, for example “from Leah’s Google Analytics 4”.
What does not change
Section titled “What does not change”Connections added by an org admin with a pasted token or a header (see Connecting an MCP server) stay organisation connectors, now recorded as organisation-wide connections owned by the admin who added them. Org admins manage them and set what Cora may do with them, and a mission switches them on or off. If that admin leaves, they stay.
For a personal connection:
- You set its tool access once, on the connection. Each tool, or each group of tools, is Allowed (Cora uses it without asking), Ask first (each call waits for an approval card that goes to you, the owner, or to the approval role you named) or Off (Cora never uses it) (D0716). You set it in the Tool access section of the connection’s page; it is the same in every mission you share it in. An org admin cannot change it on your connection, but can still stop sharing it or remove it. A tool the catalogue marks always-ask always asks: it is never offered as Allowed (D0684).
- A mission only shares it or stops sharing it. Sharing a connection lets Cora use it in that mission with the access set on the connection. Missions do not choose tools one by one.
- Every call is recorded. Whatever the setting, each call Cora makes with your connection is kept in the record.
- Keys and tokens stay in the secrets store. Cora’s worker, prompts and logs never see a key. For Google Analytics 4 the worker gets a one-hour read-only token for one step.
Where to find it
Section titled “Where to find it”- The Connections page, opened from the left rail: the Connected group at the top lists what is connected, and your own connections are labelled Yours. Each service’s page has an Account section (add, replace the key, reconnect, remove), a Tool access section and a Shared with missions section (share, stop sharing). Org admins also see Everyone’s connections on each service’s page.
- The Connections tab of a mission’s details: one row for each kind, with the owner, Share mine, Stop sharing and Add one.
See Connecting Google Analytics for the first connection, and Connecting Google Search Console for the second, and Connecting TikTok Ads for a read-only connection you make by signing in with TikTok (D0681), and Connecting Salesforce for a read-only connection that signs in through your organisation’s own sign-in app (D0682), and Connecting Meta Ads for a read-only connection that signs in with Facebook through your organisation’s own Meta app, which needs no secret (D0688), and Connecting Gmail and Connecting Outlook for reading your own mailbox through a mail server Cora hosts, signing in through your organisation’s own Google or Microsoft app (D0800, D0801), and Connecting Umbraco for an organisation-wide connection an org admin sets up once, whose drafts always wait for approval (D0683), and the console reference for the screens. Decisions D0642 to D0655 record the design.
Connecting with the service’s sign-in
Section titled “Connecting with the service’s sign-in”You can add a connection by pressing Connect and approving on the service’s own page, for Notion, Atlassian, GitHub and other hosted MCP servers (see Connecting with the service’s sign-in). It sits in the same tab and follows the same rules. Two differences: its tokens are renewed for you, so there is no key to replace (the card offers Reconnect when access ends), and it stays personal: an org admin cannot make it available to the whole organisation, because it acts as your account. The sign-in can only be finished by the browser that started it: your browser keeps a secret for each Connect, and Cora’s server keeps only its fingerprint and never keeps the service’s answer, so a sign-in link sent to someone else cannot hand you their account.
Heroes and your connection
Section titled “Heroes and your connection”A mission’s admins can make it a hero: every other mission in the organisation can then call it in (see the console reference). A hero works as it is set up, with every connection shared into it, your personal connection included (D0693). So when you share yours in a mission that becomes a hero, Cora also uses it for the hero’s callers. Nobody has to approve that, but everyone is told first (D0708).
- A warning before a hero is switched on. Before a mission’s admin switches its hero on, the Make it a hero dialog (or the card on the hero’s page) lists each personal connection shared in the mission and whose it is, for example “Leah’s Google Analytics 4, Sam’s Google Search Console: callers of this hero will be able to use these through the hero. They get the hero’s answer only, as a short summary or a full answer, whichever the hero’s card sets.” The admin presses Make it a hero anyway to go ahead.
- The same warning when you share later. If you share your connection into a mission that is already a hero, you see the same warning before it is shared, and press Share anyway to go ahead.
- You are told when it happens. When a mission is made a hero, Cora posts in the mission and mentions each person whose connection is shared there (other than the admin who switched it on): “Your Google Analytics 4 connection in Autumn launch can now be used by callers of hero @autumn-reports. Stop sharing it there if you don’t want that.” You get the usual notice for a mention.
- Stopping sharing works at once. If you don’t want a hero’s callers to use your connection, stop sharing it in that mission. Cora stops using it there straight away, for the mission’s own work and for hero calls.
- Callers get the hero’s answer only. The calling mission never gets the hero’s tools, your connection or the data behind it. It gets the hero’s answer, a short summary by default or a full answer if the hero’s card is set to give one under What callers get back, and never your key.
- You can see every hero call that used it. Under your connection, Hero calls that used this connection lists each one: the mission that called, the person who asked, and when. Nobody else sees this list, not even an org admin.
Organisation-wide connections are not listed in the warning and get no notice: an org admin set them up for the whole team.
Coming next
Section titled “Coming next”Cora will ask in a mission, with a question card, when a task needs a connection the mission does not have: “Share mine” for people who own one, “Add a connection” for others.