Disconnecting a project from Attio
A service desk is moving off Attio, or was connected to the wrong workspace, and you want the customer card gone. The app has exactly one action for that, at the bottom of the Connection tab, and it is deliberately blunt: it is called Reset to defaults and it removes the whole Attio setup for that project rather than only the credential.
That bluntness is the point. A reset that kept the object, the matching attribute, the field list and the audience used to leave administrators with a half-configured project shaped around somebody else's CRM. Read what it takes before you press it, particularly if what you actually wanted was a new key.
#There is no separate disconnect
The Connection tab offers no button that removes the key and leaves everything else in place. If your aim is to swap one key for another, that is a different action: type the new key and press "Test and save this key". The key is tested against Attio first and stored only if Attio accepts it, the workspace recorded against the project is updated to the workspace that key belongs to, and every other setting is left alone.
#What Reset to defaults removes
The screen states its own consequences before you commit: "Removes the API key, the record type, the matching attribute, every field on the card, the linked record settings, the audience and the placements, and clears everything this app has cached about your Attio records. The card comes off every issue in this project and setup starts again from the beginning. Nothing in Attio itself is changed or deleted."
Removed by a reset | Left alone by a reset |
|---|---|
The stored Attio API key | Everything in your Attio workspace: no record, object or key is changed or deleted |
The record type, the matching attribute and both domain lists | Who reported a request, which the app re-reads from Jira |
Every field on the card, the linked-record settings and the picture settings | Whether a given viewer can read a given request |
The audience and any group restriction | A person's Jira group membership |
Every placement, so the card comes off all three surfaces | A Jira user's display name and picture |
Everything cached about that project's Attio records, object definitions and viewer permissions | |
The project's row on the site-wide connections page |
The four Jira facts in the right-hand column are kept because they are answers about Jira rather than about Attio. None of them carries CRM data or any part of the configuration, and each is re-derived from Jira on its own schedule.
#It takes two presses
The first press on "Reset to defaults" reveals a confirmation with two buttons: "Yes, erase this project's Attio setup" and "Keep my settings". Nothing is removed until the second press.
The cache clearing is bounded rather than open-ended, and it is hygiene on top of the rest. Anything it does not reach expires on its own, and a cache that refuses to clear never fails the reset: dropping the key, clearing the settings and taking the card off every request all still happen.
#What you are left with
Because the key has gone, the project settings page goes back to the six-step setup wizard, starting at Connect. Agents in that project see nothing at all on their requests rather than a broken panel, and a project administrator opening a request is told "This project is not connected to an Attio workspace yet." with a link into the project's settings.
Nothing is changed inside Attio A reset only removes what this app stored in Jira. The API key itself is not touched in your Attio workspace, so a key you no longer want has to be revoked in Attio separately.
#Reconnecting afterwards
Pasting a new key does not put the card back. The placements went with everything else, so the card shows nowhere until an administrator chooses one again, and the settings page says as much: "The card is not shown anywhere yet. Choose a placement to switch it on." Nobody should see customer data reappear on live requests without somebody deciding that it should.
Reconnecting to a different Attio workspace is safe for the same reason the reset clears the caches. The previous workspace's customer data cannot be served to the new connection.
#A few things worth knowing
If what you wanted was a new key, this is the wrong button. Testing and saving a replacement key on the Connection tab keeps the record type, the fields, the audience and the placements; a reset throws all of them away and starts the wizard again.
Reconnecting does not restore the card. The placements were cleared with everything else, so the card stays off every request until somebody chooses a placement for a second time.
A reset in Jira leaves the key live in Attio. Revoking it is a separate job in your Attio workspace, and skipping it leaves a working credential in circulation for a service desk that no longer uses it.
#Related
One button, the whole setup. Aim it deliberately.
