Site-wide Attio connections
Keys are pasted by project administrators, one workspace per project, and a Jira administrator is usually not the person holding any of them. That leaves a reasonable question unanswered: which of my projects are sending customer data to which CRM workspace, and who set that up?
The connections page answers exactly that question and refuses to do anything else. It cannot enter a key, reveal one, rotate one or clear one, because it is not the page for credentials somebody else holds.
#Where it is and who can open it
Jira administration carries a page listed as "Attio for Jira". Its heading reads "Attio connections", and under it the page states its own scope: "Every project on this site that is connected to an Attio workspace. Attio keys belong to the project that pasted them, so they are never entered or shown here: this page is for seeing the estate, not for administering credentials you do not hold."
Only Jira administrators are offered it, and that is checked again on the server whenever the list loads. Anyone else is told "The Attio connections list is available to Jira administrators only."
On a site where nothing has been connected, the page explains that no site-level action is owed: "No project has connected Attio yet", with the note that a project administrator connects their own workspace from Project settings, Apps, Attio, and that "Nothing needs to be done here first."
#What each column shows
Column | What it holds | When it has nothing |
|---|---|---|
Project | The project name, with its key beside it | "Unknown project" when Jira no longer returns a name |
Attio workspace | The workspace name recorded when the key was saved, with the workspace slug beside it | "Not recorded" |
Object | The record type's name as it stood when the project chose it | "Not chosen" |
Attributes shown | How many attributes the card shows | Zero |
Connected by | The name and picture of whoever last saved the connection | "Unknown user" when Jira will not name the account, "Not recorded" for a connection made before the app recorded it |
Connected | The date the connection was saved | Blank |
Shown on | Each chosen placement named: Issue panel, Activity tab, Issue sidebar | "Nowhere", which is an ordinary state and is not styled as a fault |
Last column | An "Open settings" button into that project's Attio settings | The words "Project settings, Apps, Attio" where a link cannot be built |
A raw Atlassian account identifier is never printed in the Connected by column. Where Jira will not resolve the account, the page says so in words instead, because "somebody connected this and we cannot say who" and "nobody has been recorded" are two different answers for anyone auditing an estate.
"Shown on" reports what the project chose, not where the card is actually appearing That column lists a project's stored placements. The card only switches on for a project that can also resolve a record, meaning it has a key, a record type, a matching attribute and at least one field. A project that picked a placement and never finished the rest is listed as "Shown on Issue panel" while the card in fact renders nowhere.
#When a row appears and when it goes
A project joins the list as soon as an Attio API key is stored for it, even if setup is unfinished and no placement has been chosen, and it drops off when the key is removed by a reset. The list can be up to about half a minute behind a change made a moment ago, so a row that has not caught up yet is worth a second look rather than an investigation.
#Limits worth knowing before you audit
Up to 2,000 connected projects are indexed for this page. Past that the list stops growing, and the customer card keeps working normally in every project regardless, because the index feeds the list and nothing else.
Names are resolved in batches, up to 400 distinct people in one page load. Anyone past that shows as "Unknown user".
A resolved name and picture are remembered for twenty-four hours, so somebody who changes their display name can appear under the old one here for up to a day.
Nothing on this page can act on a project. When you need to change something, the last column takes you into that project's own Attio settings, where the usual rule applies: you need to be an administrator of that project, not only of the site.
#A few things worth knowing
In this build the Connected by column shows coloured initials rather than a profile photograph, because the avatar host is not among the app's permitted image sources. The name beside it is correct either way, so read the name and ignore the picture.
A Jira project deleted while it still held an Attio connection keeps its row here, with the project name missing. That is deliberate: it is how a leftover connection can be found and cleared up, not a bug in the list.
On a very large estate the "Unknown user" cells are not always a permissions story. Once more than 400 distinct connecting administrators are on one page load, the surplus rows read "Unknown user" even for accounts Jira would happily name.
#Related
An inventory, not a control panel. The keys stay where they were pasted.
