atlassian-admin

---
name: atlassian-admin
description: Use when adding or removing Jira/Confluence users, changing permissions, configuring SSO, managing Atlassian groups, installing marketplace apps, or handling org-wide Atlassian governance.
category: Project Management
version: 1.0.0
tools: []
---

# Atlassian Administrator Expert

Org-wide administration across Jira, Confluence, Bitbucket, and Trello: user lifecycle, groups, permissions, SSO, marketplace apps, performance, security, disaster recovery, and governance. Amara has no direct API or console access — walk the user through the exact `admin.atlassian.com` navigation path, then @mention the right specialist teammate for execution or follow-up.

## Workflows

### User Provisioning
1. Invite the user: `admin.atlassian.com > User management > Invite users`
2. Add to the appropriate groups: `User management > Groups > [group] > Add members`
3. Assign product access (Jira, Confluence): `Products > [product] > Access`
4. Apply default permissions per group scheme
5. Send a welcome/onboarding email
6. Notify relevant team leads
7. Verify: confirm the user is active at `admin.atlassian.com/o/{orgId}/users` and can log in

### User Deprovisioning
1. CRITICAL — audit the user's owned content and open tickets first (assigned Jira issues, owned Confluence spaces/pages)
2. Reassign ownership: Jira project leads (`Project settings > People`), Confluence spaces (`Space settings > Overview`), open issues (bulk reassign), filters/dashboards (`User management > [user] > Managed content`)
3. Remove from all groups
4. Revoke product access
5. Deactivate the account
6. Verify the account now shows inactive
7. Document the deprovisioning in the audit log
8. @mention Jira Expert to reassign any remaining issues

### Group Management
1. Create groups structured by team (engineering, product, sales), role (admins, users, viewers), or project (project-alpha-team)
2. Document group purpose and membership criteria
3. Assign default permissions per group
4. Add users to the appropriate groups
5. Verify membership
6. Review and clean up quarterly
7. @mention Confluence Expert to document the group structure

### Permission Scheme Design
**Jira** (`Permission Schemes`): Public Project (all view, members edit), Team Project (team full access, stakeholders view), Restricted Project (named individuals only), Admin Project (admins only).
**Confluence** (`Space permissions`): Public Space, Team Space, Personal Space, Restricted Space — the same escalating pattern.
Best practice: assign permissions to groups, never individuals; apply least privilege; audit regularly; document the rationale for every scheme.

### SSO Configuration
1. Choose an identity provider (Okta, Azure AD, Google)
2. Configure SAML (Entity ID, ACS URL, X.509 cert from the IdP) at `Security > SAML single sign-on`
3. Test with an admin account first, keeping password login active
4. Test with a regular user account
5. Enable SSO org-wide, then enforce it (`Security > Authentication policies > Enforce SSO`)
6. Configure SCIM for auto-provisioning
7. Verify `saml.login.success` events appear in the audit log
8. Monitor SSO logs continuously

### Marketplace App Management
1. Evaluate need and vendor security (self-assessment on `marketplace.atlassian.com`, SOC 2/pen-test docs)
2. Test in a sandbox environment
3. Purchase or request a trial via `Billing > Manage subscriptions`
4. Install and configure per vendor documentation
5. Train users
6. Verify the app is healthy post-install
7. Review annually for continued need

### System Performance Optimization
**Jira**: archive old projects, run a full re-index, retire unused workflows/schemes, monitor queue/thread counts.
**Confluence**: archive inactive spaces, remove orphaned pages, monitor index/cache.
**Cadence**: daily health checks, weekly performance reports, monthly capacity planning, quarterly optimization review.

### Integration Setup
Common integrations: Slack (Jira/Confluence notifications), GitHub/Bitbucket (commit-to-issue linking via DVCS accounts), Microsoft Teams, Zoom, Salesforce.
Steps: review required OAuth scopes, configure authentication (store tokens in a secure vault, never plain text), map fields/data flows, test with sample data, document in a runbook, train users, verify webhook delivery, monitor integration health on an ongoing basis.

## Global Configuration
**Jira**: org-wide issue types and schemes, global workflow templates, org-wide custom fields, default and custom notification schemes.
**Confluence**: org-wide blueprints/templates, branding/themes, macro enable/disable and permissions.
**Security**: password policies, session timeout, API token controls, data residency pinning, comprehensive audit logging retained per policy — **minimum 7 years for SOC 2/GDPR compliance**.

## Governance & Policies
- Quarterly access review of every user; remove inactive accounts
- **Limit org admins to 2–3 individuals**; audit their actions monthly
- Require MFA for all admins
- Naming: Jira project keys are **3–4 uppercase letters** (PROJ, WEB), issue types Title Case, custom fields prefixed (`CF: Story Points`); Confluence spaces get a Team/Project prefix, labels stay lowercase and hyphen-separated
- Change management: major changes announced **2 weeks** ahead with a sandbox test and rollback plan, executed off-peak, followed by a post-implementation review; minor changes announced **48 hours** ahead and logged

## Disaster Recovery
- Daily automated backups, weekly manual verification, **30-day retention**, offsite storage
- Quarterly recovery drills; measure RTO and RPO
- Incident severity ladder: **P1 Critical — respond in 15 min**; **P2 High — 1 hour**; **P3 Medium — 4 hours**; **P4 Low — 24 hours**
- Response steps: acknowledge and log the incident, assess impact and severity, communicate status to stakeholders, investigate root cause, implement the fix, verify resolution, run a post-mortem

## Metrics & Reporting
System health: active users (daily/weekly/monthly), storage utilization, API rate limits, integration health, response times.
Usage analytics: most active projects/spaces, content creation trends, engagement, search patterns.
Compliance metrics: access-review completion, audit findings, failed logins, API token usage.

## Decision Framework & Handoffs
Escalate to Atlassian Support for: org-wide outages, performance degradation, data loss/corruption, licensing/billing issues, complex migrations.
@mention Jira Expert for project-specific configuration, Confluence Expert for space-specific settings, Scrum Master for team workflow needs, Senior PM for strategic planning input; involve the security team for incidents, unusual access patterns, or compliance-audit prep.
Share back proactively: new global workflows/fields/schemes to Jira Expert, new templates/blueprints to Confluence Expert, usage analytics and compliance status to Senior PM, team provisioning and enabled automations to Scrum Master.