Administer Jira and Confluence at scale — user management, permission schemes, SSO integration, security configuration, and disaster recovery planning.
Manage organization-wide settings and user access across Jira and Confluence to securely onboard new members, configure permissions, and safely offboard employees without losing project ownership. Reach for this skill whenever you need to update admin settings, manage groups, or enforce security policies across your organization.
name: “atlassian-admin”
description: Atlassian Administrator for managing and organizing Atlassian products (Jira, Confluence, Bitbucket, Trello), users, permissions, security, integrations, system configuration, and org-wide governance. Use when asked to add users to Jira, change Confluence permissions, configure access control, update admin settings, manage Atlassian groups, set up SSO, install marketplace apps, review security policies, or handle any org-wide Atlassian administration task.
Atlassian Administrator Expert
Workflows
User Provisioning
Create user account: admin.atlassian.com > User management > Invite users
REST API: POST /rest/api/3/user with {"emailAddress": "...", "displayName": "...","products": [...]}
Add to appropriate groups: admin.atlassian.com > User management > Groups > [group] > Add members
Enable comprehensive logging; export via GET /admin/v1/orgs/{orgId}/audit-log
Retain per policy (minimum 7 years for SOC 2/GDPR compliance)
Governance & Policies
Access Governance
Quarterly review of all user access: admin.atlassian.com > User management > Export users
Verify user roles and permissions; remove inactive users
Limit org admins to 2–3 individuals; audit admin actions monthly
Require MFA for all admins: Security > Authentication policies > Require 2FA
Naming Conventions
Jira: Project keys 3–4 uppercase letters (PROJ, WEB); issue types Title Case; custom fields prefixed (CF: Story Points)
Confluence: Spaces use Team/Project prefix (TEAM: Engineering); pages descriptive and consistent; labels lowercase, hyphen-separated
Change Management
Major Changes: Announce 2 weeks in advance; test in sandbox; create rollback plan; execute during off-peak; post-implementation review
Minor Changes: Announce 48 hours in advance; document in change log; monitor for issues
TO Jira Expert: New global workflows, custom fields, permission schemes, or automation capabilities available
TO Confluence Expert: New global templates, space permission schemes, blueprints, or macros configured
TO Senior PM: Usage analytics, capacity planning insights, cost optimization, security compliance status
TO Scrum Master: Team access provisioned, board configuration options, automation rules, integrations enabled
FROM All Roles: User access requests, permission changes, app installation requests, configuration support, incident reports
Atlassian MCP Integration
Primary Tools: Jira MCP, Confluence MCP
Admin Operations:
User and group management via API
Bulk permission updates
Configuration audits
Usage reporting
System health monitoring
Automated compliance checks
Integration Points:
Support all roles with admin capabilities
Enable Jira Expert with global configurations
Provide Confluence Expert with template management
Ensure Senior PM has visibility into org health
Enable Scrum Master with team provisioning
{ "permissionScheme": { "name": "Standard Project Permission Scheme", "description": "Default permission scheme for standard projects. Assigns permissions based on project roles.", "version": "1.0", "lastUpdated": "YYYY-MM-DD", "owner": "IT Admin Team" }, "roles": { "projectAdmin": { "description": "Full project administration including configuration and user management", "typicalGroups": ["project-leads", "engineering-managers"] }, "developer": { "description": "Create and manage issues, transitions, and attachments", "typicalGroups": ["dept-engineering", "dept-product"] }, "user": { "description": "View issues, add comments, and create basic issues", "typicalGroups": ["org-all-employees"] }, "viewer": { "description": "Read-only access to project issues and boards", "typicalGroups": ["stakeholders", "external-contractors"] } }, "permissions": { "project": { "ADMINISTER_PROJECTS": { "description": "Manage project settings, roles, and permissions", "grantedTo": ["projectAdmin"] }, "BROWSE_PROJECTS": { "description": "View the project and its issues", "grantedTo": ["projectAdmin", "developer", "user", "viewer"] }, "VIEW_DEV_TOOLS": { "description": "View development panel (commits, branches, PRs)", "grantedTo": ["projectAdmin", "developer"] }, "VIEW_READONLY_WORKFLOW": { "description": "View read-only workflow", "grantedTo": ["projectAdmin", "developer", "user", "viewer"] } }, "issues": { "CREATE_ISSUES": { "description": "Create new issues in the project", "grantedTo": ["projectAdmin", "developer", "user"] }, "EDIT_ISSUES": { "description": "Edit issue fields", "grantedTo": ["projectAdmin", "developer"] }, "DELETE_ISSUES": { "description": "Delete issues permanently", "grantedTo": ["projectAdmin"] }, "ASSIGN_ISSUES": { "description": "Assign issues to team members", "grantedTo": ["projectAdmin", "developer"] }, "ASSIGNABLE_USER": { "description": "Be assigned to issues", "grantedTo": ["projectAdmin", "developer"] }, "CLOSE_ISSUES": { "description": "Close/resolve issues", "grantedTo": ["projectAdmin", "developer"] }, "RESOLVE_ISSUES": { "description": "Set issue resolution", "grantedTo": ["projectAdmin", "developer"] }, "TRANSITION_ISSUES": { "description": "Transition issues through workflow", "grantedTo": ["projectAdmin", "developer", "user"] }, "LINK_ISSUES": { "description": "Create and remove issue links", "grantedTo": ["projectAdmin", "developer"] }, "MOVE_ISSUES": { "description": "Move issues between projects", "grantedTo": ["projectAdmin"] }, "SCHEDULE_ISSUES": { "description": "Set due dates on issues", "grantedTo": ["projectAdmin", "developer"] }, "SET_ISSUE_SECURITY": { "description": "Set security level on issues", "grantedTo": ["projectAdmin"] } }, "comments": { "ADD_COMMENTS": { "description": "Add comments to issues", "grantedTo": ["projectAdmin", "developer", "user"] }, "EDIT_ALL_COMMENTS": { "description": "Edit any comment", "grantedTo": ["projectAdmin"] }, "EDIT_OWN_COMMENTS": { "description": "Edit own comments", "grantedTo": ["projectAdmin", "developer", "user"] }, "DELETE_ALL_COMMENTS": { "description": "Delete any comment", "grantedTo": ["projectAdmin"] }, "DELETE_OWN_COMMENTS": { "description": "Delete own comments", "grantedTo": ["projectAdmin", "developer", "user"] } }, "attachments": { "CREATE_ATTACHMENTS": { "description": "Attach files to issues", "grantedTo": ["projectAdmin", "developer", "user"] }, "DELETE_ALL_ATTACHMENTS": { "description": "Delete any attachment", "grantedTo": ["projectAdmin"] }, "DELETE_OWN_ATTACHMENTS": { "description": "Delete own attachments", "grantedTo": ["projectAdmin", "developer", "user"] } }, "worklogs": { "WORK_ON_ISSUES": { "description": "Log work on issues", "grantedTo": ["projectAdmin", "developer"] }, "EDIT_ALL_WORKLOGS": { "description": "Edit any worklog", "grantedTo": ["projectAdmin"] }, "EDIT_OWN_WORKLOGS": { "description": "Edit own worklogs", "grantedTo": ["projectAdmin", "developer"] }, "DELETE_ALL_WORKLOGS": { "description": "Delete any worklog", "grantedTo": ["projectAdmin"] }, "DELETE_OWN_WORKLOGS": { "description": "Delete own worklogs", "grantedTo": ["projectAdmin", "developer"] } } }, "projectMappings": [ { "projectKey": "EXAMPLE", "projectName": "Example Project", "scheme": "Standard Project Permission Scheme", "roleAssignments": { "projectAdmin": ["project-leads"], "developer": ["team-example-devs"], "user": ["org-all-employees"], "viewer": ["stakeholders-example"] } } ], "notes": { "usage": "Copy this template and customize role assignments per project. Use group names that match your Atlassian groups.", "review": "Review permission scheme assignments quarterly as part of access review.", "changes": "Any changes to permission schemes should be documented and approved by IT Admin." }}
Atlassian Cloud Security Hardening Guide
Overview
This guide provides a comprehensive security hardening checklist for Atlassian Cloud products (Jira, Confluence, Bitbucket). It covers identity management, access controls, data protection, and monitoring practices aligned with enterprise security standards.
Identity & Authentication
SSO / SAML Setup
Implementation Steps:
Verify your domain in Atlassian Admin (admin.atlassian.com)
Claim all company email accounts
Configure SAML SSO with your identity provider (Okta, Azure AD, Google Workspace)
Set authentication policy to enforce SSO for all managed accounts
Test with a pilot group before full rollout
Disable password-based login for managed accounts
Configuration Checklist:
Domain verified and accounts claimed
SAML IdP configured with correct entity ID and SSO URL
Attribute mapping: email, displayName, groups
Single Logout (SLO) configured
Authentication policy enforcing SSO
Fallback access configured for emergency admin accounts
SCIM provisioning enabled for automatic user sync
Two-Factor Authentication (2FA)
Enforcement Policy:
2FA required for all managed accounts
Enforce via authentication policy (not just recommended)
Hardware security keys (FIDO2/WebAuthn) preferred for admin accounts
TOTP (authenticator app) as minimum for all users
SMS-based 2FA disabled (SIM swap vulnerability)
Recovery codes generated and stored securely
Session Management
Session timeout set to 8 hours of inactivity (maximum)
Absolute session timeout: 24 hours
Require re-authentication for sensitive operations
Monitor concurrent sessions per user
Enforce session termination on password change
Access Controls
IP Allowlisting
Configuration:
Enable IP allowlisting for organization
Add corporate office IP ranges
Add VPN exit node IP addresses
Add CI/CD server IPs for API access
Test access from all approved locations
Document approved IP ranges with justification
Review IP allowlist quarterly
Exceptions:
Mobile access may require VPN or MDM solution
Remote workers need VPN or conditional access policies
API integrations need stable IP ranges
API Token Management
Policies:
Inventory all API tokens in use
Set maximum token lifetime (90 days recommended)
Require token rotation on schedule
Use service accounts for integrations (not personal tokens)
Monitor API token usage patterns
Revoke tokens immediately on employee departure
Document purpose and owner for each token
Best Practices:
Use OAuth 2.0 (3LO) for user-context integrations
Use API tokens only for service-to-service
Store tokens in secrets management (never in code)
Implement least-privilege scopes for OAuth apps
Permission Model
Review global permissions quarterly
Use groups for permission assignment (not individual users)
Implement role-based access for Jira projects
Restrict Confluence space admin to designated owners
Limit Jira system admin to 2-3 people
Audit "anyone" or "logged in users" permissions
Remove direct user permissions where groups exist
Audit & Monitoring
Audit Log Configuration
What to Monitor:
User authentication events (login, logout, failed attempts)
Permission changes (project, space, global)
User account changes (creation, deactivation, group changes)
API token creation and revocation
App installations and updates
Data export operations
Admin configuration changes
Setup Steps:
Enable organization audit log
Configure audit log retention (minimum 1 year)
Set up automated export to SIEM (Splunk, Datadog, etc.)
Create alerts for suspicious patterns
Schedule monthly audit log review
Document incident response procedures for alerts
Alerting Rules
Critical Alerts (Immediate Response):
Multiple failed login attempts (>5 in 10 minutes)
Admin permission grants to unexpected users
API token created by non-service accounts
Bulk data export or deletion
New third-party app installed with broad permissions
Warning Alerts (Same-Day Review):
New admin users added
Permission scheme changes
Authentication policy modifications
IP allowlist changes
User deactivation (verify it is expected)
Data Protection
Data Residency
Configure data residency realm (US, EU, AU, etc.)
Verify product data pinned to selected region
Document data residency for compliance audits
Review data residency coverage (some metadata may be global)
Monitor for new residency options from Atlassian
Encryption
Verify encryption at rest (AES-256, managed by Atlassian)
User Provisioning & Lifecycle Management Checklist
Overview
This checklist covers the complete user lifecycle in Atlassian Cloud products, from onboarding through offboarding. Consistent provisioning ensures security, compliance, and a smooth user experience.
Onboarding Steps
Pre-Provisioning
Receive approved access request (ticket or HR system trigger)
Verify employee record in HR system
Determine role-based access level (see Role Templates below)