# Attio project settings in Jira Somebody has asked you to connect a service desk to Attio, or to change what agents see on the customer card, and the first two questions are where the screen is and whether you are allowed to open it. Both answers are narrow on purpose. Attio is configured per project, by the people who administer that project, on a page that only exists in Jira Service Management. This page covers where that screen lives, who can reach it, and what each of its six sections is for. What to type into them is the business of the setup pages; this is the map of the building. ## Where the page is Inside a Jira Service Management project, the project's own settings carry an entry named "Attio", described as "Connect this project to an Attio workspace". The app's own copy gives the location as "Project settings, Apps, Attio", and that is the wording the site-wide connections list falls back to when it cannot build a link for you. There is no site-level equivalent. Every project that wants the card connects its own Attio workspace, and two projects on the same Jira site can be connected to two different workspaces. ⚠️ **On any other kind of project, the entry is absent** The Attio page appears only on service desk projects. In a business or software project the app adds nothing at all, the settings entry included, so there is nothing to set up there and nothing to find. An app that is installed but adds no entry, and an app that is not installed, look identical from that screen. ## Who can open it Project administrators of that project, signed in. Nobody else is offered the page, and hiding it is not the only protection: every action the screen takes is checked again on the server, which refuses anyone else with "Attio settings for this project are available to project administrators only." That check is asked of Jira live each time rather than remembered, so somebody who loses project administration is refused on their next action rather than at some later point. Which project a settings action applies to is taken from the context Jira signs for the page, never from anything the browser sends, so no screen can be pointed at a project it is not open in. When that context is missing the page asks you to reload: "Capable could not tell which Jira project this settings page belongs to. Reload the page and try again." The site-wide connections list is a different audience again. It is for Jira administrators, it is read-only, and it is covered on its own page. ## One page, two shapes A project that has not finished setup opens into a six-step wizard. A project that has finished opens as a tab strip with the same six sections. Nothing switches between them by hand: the page decides from what is stored. Setup counts as finished when all five of these are true: * an Attio API key is stored for the project * a record type has been chosen * an attribute to match reporters on has been chosen * at least one field has been chosen for the card * at least one placement has been chosen Once the tabbed page has been shown during a visit it stays shown, even while an edit temporarily leaves the project unable to show a card, for example in the moment after changing the record type, which clears the fields chosen under it. The page returns to the wizard only when the stored key goes, which in practice means a reset. ## The six sections | **Tab** | **What it is for, in the app's own words** | | ----------- | ---------------------------------------------------------------------------- | | Connection | "The Attio API key this project uses, and the workspace it reaches." | | Record type | "Which Attio object your customers live in." | | Matching | "How a reporter is found in Attio, and how linked records are titled." | | Fields | "What the card shows, in the order it shows it." | | Permissions | "Who sees the card, on top of being able to see the issue." | | Placement | "Where on the issue the card appears. Changes here take effect immediately." | The settings page is deliberately never hidden by the placement choice, and never hidden on a project that has not connected anything. It is the screen that chooses the placements, so gating it on one would leave an unconfigured project impossible to set up and a disconnected one impossible to reconnect. ## The header, and what it is telling you Above the tabs the page states the live position: the Attio workspace the project is connected to, where the card is being shown and to whom, in the shape "Shown on Issue panel and Activity tab, to agents in this project.", and which matching mode is in force. All of it is read from what the server has stored. While the settings load, a placeholder in the shape of the real page is shown and announced as "Loading the Attio settings for this project". If they cannot be read at all, the page is replaced by "These settings could not be loaded" with the underlying reason, and nothing can be edited until it clears. Settings written by an older version of the app are read tolerantly. A stored value the current version does not recognise falls back to its default rather than taking the page down, and the page does not open showing unsaved changes merely because a newer setting was missing. --- ## A few things worth knowing * The header describes what is stored, not what is on your screen. With unsaved edits sitting in the tabs it still reports the old placements and the old audience, which makes it a poor way to check whether your change went in. * On a project that is not a service desk there is no Attio entry to find. Before concluding the app is missing from the site, check the project type: the connections page will tell you whether other projects have connected it. * The tabbed page and the wizard are the same six questions, so an administrator who has only ever seen the wizard will look for a Next button that the tabbed page does not have. On the tabs, most changes wait for Save changes instead. --- ## Related [Saving changes to Attio settings](https://help.gocapable.com/attio-for-jira/saving-changes-to-attio-settings.html) [Site-wide Attio connections](https://help.gocapable.com/attio-for-jira/site-wide-attio-connections.html) --- _Six tabs, one project, and no site-wide shortcut._