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
1
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.2
Grant the right permissions
Give the service account access to the projects, repos, or calendars that Warrn needs. Nothing more.
3
Connect via OAuth in Warrn
Go to Settings in Warrn, select the integration, and authenticate as the service account.