> For the complete documentation index, see [llms.txt](https://docs.spreo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spreo.io/management/manage-integrations.md). # Manage Integrations Organization-wide settings for Jira, AI assistants and AI features. The Admin menu has an Integrations group with organization-wide settings for the tools that connect to Spreo. Each section below has a button that opens that screen in Spreo. ### Atlassian Available to Owners and Admins. Open Atlassian settings This screen shows the Atlassian site your organization is connected to, and how many people have linked their Atlassian profile.
The Atlassian admin screen, showing the connected site and Custom Field Rules
**Custom Field Rules** let you always include, or always hide, a Jira custom field on Jira cards. A rule can apply to one Jira project key, or to every project with `*`. Changes to these rules are recorded in the [Activity Log](/management/activity-log.md). Each Spreo organization connects to one Atlassian site. See [Jira Integration](/boards/jira-integration.md). ### MCP Available to Owners and Admins. Open MCP settings The switch **Allow account members to connect AI tools via MCP** controls whether members can connect an AI assistant to their boards. It is on by default. The **Connected members** table lists everyone who has connected an AI tool, which client they used and when.
The MCP admin screen, with the account switch and the Connected members list
See [MCP Permissions and security](/boards/mcp/mcp-permissions-and-security.md). ### AI Settings Available to Owners only. Open AI Settings Switch Spreo's AI features on or off for the organization, and choose between Spreo's AI providers and your own API keys. See [Beta Features](/boards/beta-features.md#ai-features).
The AI Features admin screen, with Review & Opt In and Use Own API Keys
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.spreo.io/management/manage-integrations.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.