Administration
Two audiences here: a project administrator who owns one connection, and a site administrator who wants to know how many connections exist and to which workspaces.
The freshness page is the one worth reading before anybody reports a bug: some changes appear at once and others take up to fifteen minutes, by design.
#In this section
Attio project settings in JiraThe Attio settings for a service desk live inside that project's own settings, only project administrators can open them, and the same page is both the setup wizard and the settings screen.Saving changes to Attio settingsMost Attio settings wait for Save changes, two of them do not, and a save always re-reads the whole configuration from the server. Knowing which is which is the difference between an edit landing and vanishing.Site-wide Attio connectionsA read-only inventory for Jira administrators: which projects on the site are connected to which Attio workspace, who connected them, and where the customer card is being shown.Disconnecting a project from AttioThere is no key-only disconnect. Reset to defaults removes the key, every setting under it and everything cached, takes the card off every request, and sends the project back to setup.How long Attio changes take to appearValues edited in Attio can take fifteen minutes to reach the card, an attribute renamed there can take an hour, and changes made in project settings show on the next view of a request.
#Related
Know what is cached before you call it broken.
