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

# Bot Account

> Use a dedicated service account when connecting integrations like Jira, Google, and GitHub.

When connecting organization-level integrations (Jira, Google Meet, Confluence), we recommend authenticating with a dedicated service account rather than a personal account.

## Why

* **No disruption when people leave.** If someone leaves and their account is deactivated, every integration authenticated through them breaks.
* **Audit trail.** Actions taken by Warrn (creating Jira tickets, scheduling Google Meet war rooms) show up as the service account, not a person.
* **Scoped permissions.** Give the service account only the access Warrn needs. No risk of exposing someone's full personal account.

## How to set it up

<Steps>
  <Step title="Create a service account">
    Create a dedicated account in your identity provider (Google Workspace, Atlassian) with a name like `warrn-bot@yourcompany.com` or `warrn-integration@yourcompany.com`.
  </Step>

  <Step title="Grant the right permissions">
    Give the service account access to the projects, repos, or calendars that Warrn needs. Nothing more.
  </Step>

  <Step title="Connect via OAuth in Warrn">
    Go to **Settings** in Warrn, select the integration, and authenticate as the service account.
  </Step>
</Steps>

## Which integrations this applies to

| Integration                       | What Warrn does with it                                           |
| --------------------------------- | ----------------------------------------------------------------- |
| **Atlassian** (Jira + Confluence) | Creates and links Jira issues, exports post-mortems to Confluence |
| **Google Meet**                   | Creates war rooms for alerts and incidents                        |