> ## Documentation Index
> Fetch the complete documentation index at: https://docs.amnify.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrations

> The tools your team already works in: where Amnify files work, reads your documentation, and tells you what happened.

Sources are the systems Amnify **scans**. Integrations are the tools your team already works in, connected so security work does not live in a separate place.

<CardGroup cols={3}>
  <Card title="Task management" icon="list-check">
    File a finding as a ticket in your tracker.
  </Card>

  <Card title="Knowledge base" icon="book">
    Read your existing documentation as context.
  </Card>

  <Card title="Communication" icon="comment">
    Get told what happened, where your team already talks.
  </Card>
</CardGroup>

## Task management

Create a ticket straight from a finding, carrying the impact, the severity and the location.

| Provider   | Status    |
| ---------- | --------- |
| Linear     | Available |
| Jira       | Planned   |
| ServiceNow | Planned   |

After connecting, choose where issues go: the team, an optional project, the workflow state new issues are created in (triage, backlog or unstarted), and labels applied to every created issue.

<CardGroup cols={2}>
  <Card title="One ticket per finding" icon="link">
    Per provider, showing the identifier, the URL and the current status.
  </Card>

  <Card title="Status is read only" icon="eye">
    Amnify reads the ticket status to display it. Closing a ticket never closes a finding.
  </Card>
</CardGroup>

Issues are attributed to Amnify, not to whoever connected the integration. Disconnecting strips the credentials and stops all access. Existing links stay readable and revive if you reconnect the same workspace.

## Knowledge base

Your security policies, standards and architecture decisions usually already exist in a documentation tool. Connecting it lets Amnify read them as [context](/knowledge/context) directly, instead of you uploading files.

| Provider   | Status  |
| ---------- | ------- |
| Notion     | Planned |
| Confluence | Planned |

Until then, upload the documents yourself. See [Context](/knowledge/context).

## Communication channels

Where Amnify tells you something needs you.

| Channel         | Status    |
| --------------- | --------- |
| Email           | Available |
| Slack           | Planned   |
| Microsoft Teams | Planned   |

Email works today with no setup: you are notified when a finding or a question is assigned to you, and organization invitations arrive the same way. Slack and Microsoft Teams will carry the same notifications into the channel your team already watches.

## AI coding agents

Amnify also exposes your security data to the AI tools your team already uses, so an agent can read your findings and act on them. See [AI coding agents](/connect/agent-connector).

<Note>
  Owners and managers can connect, reconfigure and disconnect an integration. Every member can create issues from a finding.
</Note>