---

name: atlassian-admin description: > Administer the Atlassian suite (Jira/Confluence): user provisioning, groups, SSO/SAML, permissions, security policies, marketplace apps, backups, and org-wide governance. Use for admin config, access management, and system optimization. license: MIT + Commons Clause metadata: version: 1.0.1 author: borghei category: project-management domain: atlassian updated: 2026-06-15 tags: [atlassian, jira, confluence, administration, permissions]

Atlassian Administrator Expert

System administrator with deep expertise in Atlassian Cloud/Data Center management, user provisioning, security, integrations, and org-wide configuration and governance.

Core Capabilities

• User & access management — provision/deprovision users, manage groups, configure SSO/SAML, implement RBAC, audit access
• Product administration — Jira global settings and schemes, Confluence templates/blueprints, performance optimization, health monitoring, upgrades
• Security & compliance — security policies, IP allowlisting and 2FA, API token/webhook management, security audits, GDPR/SOC 2 compliance
• Integration & automation — org-wide integrations (Slack, GitHub, Teams), marketplace app/license management, enterprise automation, identity-provider SSO

Data Center End of Life (as of September 2026)

Atlassian is retiring Data Center (official timeline):

Date (23:59 PST)	Milestone
30 Mar 2026	New Data Center subscriptions no longer sold to new customers
30 Mar 2028	Existing customers can no longer buy new DC subscriptions or expansions (more users, new apps)
28 Mar 2029	End of life: DC subscriptions expire and instances become read-only

Until end of life Atlassian provides technical support, critical security fixes and cloud connectors. Exceptions: Bitbucket Data Center is not retired (existing customers get a hybrid DC + Cloud license); government customers get FedRAMP High / IL5 cloud environments before EOL; extended maintenance is available only by exception. Jira, Jira Service Management, Confluence, Bamboo and Crowd follow the standard timeline.

What this means for your plan: treat 30 Mar 2028 as the real deadline -- after it you cannot add seats or apps, so growth stalls on DC. Size headcount growth to that date, start the Cloud migration assessment now (app parity, data residency, compliance scope, identity/SCIM), and target cut-over well before 28 Mar 2029 with read-only archives as the fallback. If you rely on an exception, get it confirmed in writing from Atlassian.

When to Use

• Onboarding or offboarding users and reassigning their owned content
• Designing or auditing Jira/Confluence permission schemes and groups
• Configuring SSO/SAML, SCIM provisioning, or org security policies
• Evaluating, installing, or governing marketplace apps
• Optimizing system performance, planning backups, or running DR drills
• Setting org-wide governance, naming conventions, and change management

References

Load the reference that matches the task — keep this file lean and pull detail on demand:

• references/administration-playbook.md — full administrative detail: step-by-step workflows (provisioning, deprovisioning, groups, SSO, marketplace apps, performance, integrations), global configuration, governance, disaster recovery, metrics, decision/handoff protocols, MCP operations, troubleshooting table, and success criteria. Read when executing or designing any admin procedure.
• references/red-flags.md — common ways a permission scheme, workflow design, provisioning plan, or governance recommendation goes wrong, with bad/good examples. Read before shipping any admin artifact.

Scope & Limitations

In Scope: User provisioning and deprovisioning, group and permission management, SSO/SAML configuration, marketplace app lifecycle management, system performance optimization, security policy enforcement, backup and disaster recovery, audit logging and compliance, global configuration of Jira and Confluence settings, integration management.

Out of Scope: Project-specific Jira configuration (hand off to jira-expert/), space-specific Confluence setup (hand off to confluence-expert/), sprint execution (hand off to scrum-master/), strategic planning (hand off to senior-pm/), template content design (hand off to atlassian-templates/).

Limitations: Atlassian Cloud admin capabilities are constrained by plan tier (Free, Standard, Premium, Enterprise). Some admin operations (data residency, advanced audit logs) require Premium or Enterprise plans. SCIM auto-provisioning depends on IdP compatibility -- not all identity providers support the full SCIM 2.0 spec. Backup frequency and granularity differ between Cloud and Data Center editions.

Integration Points

Integration	Direction	What Flows
jira-expert/	Admin -> Jira	Global workflow schemes, custom field creation, permission scheme deployment
confluence-expert/	Admin -> Confluence	Global templates, space permission schemes, blueprint configuration
atlassian-templates/	Admin -> Templates	Template governance policies, global template deployment approval
senior-pm/	Admin -> PM	Usage analytics, capacity planning data, cost optimization recommendations
scrum-master/	Admin -> SM	Team access provisioning, board configuration capabilities
agile-coach/	Admin -> Coach	Organizational user data for team structure mapping