atlassian-admin

What this skill does

# 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 Competencies

**User & Access Management**
- Provision and deprovision users across Atlassian products
- Manage groups and group memberships
- Configure SSO/SAML authentication
- Implement role-based access control (RBAC)
- Audit user access and permissions

**Product Administration**
- Configure Jira global settings and schemes
- Manage Confluence global templates and blueprints
- Optimize system performance and indexing
- Monitor system health and usage
- Plan and execute upgrades

**Security & Compliance**
- Implement security policies and standards
- Configure IP allowlisting and 2FA
- Manage API tokens and webhooks
- Conduct security audits
- Ensure compliance with data regulations (GDPR, SOC 2)

**Integration & Automation**
- Configure org-wide integrations (Slack, GitHub, etc.)
- Manage marketplace apps and licenses
- Set up enterprise automation
- Configure webhooks and API access
- Implement SSO with identity providers

## Workflows

### User Provisioning
1. Receive request for new user access
2. Verify user identity and role
3. Create user account in organization
4. Add to appropriate groups (Jira users, Confluence users, etc.)
5. Assign product access (Jira, Confluence)
6. Configure default permissions
7. Send welcome email with onboarding info
8. **NOTIFY**: Relevant team leads of new member

### User Deprovisioning
1. Receive offboarding request
2. **CRITICAL**: Audit user's owned content and tickets
3. Reassign ownership of:
   - Jira projects
   - Confluence spaces
   - Open issues
   - Filters and dashboards
4. Remove from all groups
5. Revoke product access
6. Deactivate or delete account (per policy)
7. Document deprovisioning in audit log
8. **USE**: Jira Expert to reassign issues

### Group Management
1. Create groups based on:
   - Teams (engineering, product, sales)
   - Roles (admins, users, viewers)
   - Projects (project-alpha-team)
2. Define group purpose and membership criteria
3. Assign default permissions per group
4. Add users to appropriate groups
5. Regular review and cleanup (quarterly)
6. **USE**: Confluence Expert to document group structure

### Permission Scheme Design
**Jira Permission Schemes**:
- **Public Project**: All users can view, members can edit
- **Team Project**: Team members full access, stakeholders view
- **Restricted Project**: Named individuals only
- **Admin Project**: Admins only

**Confluence Permission Schemes**:
- **Public Space**: All users view, space members edit
- **Team Space**: Team-specific access
- **Personal Space**: Individual user only
- **Restricted Space**: Named individuals and groups

**Best Practices**:
- Use groups, not individual permissions
- Principle of least privilege
- Regular permission audits
- Document permission rationale

### SSO Configuration
1. Choose identity provider (Okta, Azure AD, Google)
2. Configure SAML settings in Atlassian
3. Test SSO with admin account
4. Test with regular user account
5. Enable SSO for organization
6. Enforce SSO (disable password login)
7. Configure SCIM for auto-provisioning (optional)
8. Monitor SSO logs for failures

### Marketplace App Management
1. Evaluate app need and security
2. Review vendor security documentation
3. Test app in sandbox environment
4. Purchase or request trial
5. Install app on production
6. Configure app settings
7. Train users on app usage
8. Monitor app performance and usage
9. Review app annually for continued need

### System Performance Optimization
**Jira Optimization**:
- Archive old projects and issues
- Reindex when performance degrades
- Optimize JQL queries
- Clean up unused workflows and schemes
- Monitor queue and thread counts

**Confluence Optimization**:
- Archive inactive spaces
- Remove orphaned pages
- Compress attachments
- Monitor index and cache
- Clean up unused macros and apps

**Monitoring**:
- Daily health checks
- Weekly performance reports
- Monthly capacity planning
- Quarterly optimization reviews

### Integration Setup
**Common Integrations**:
- **Slack**: Notifications for Jira and Confluence
- **GitHub/Bitbucket**: Link commits to issues
- **Microsoft Teams**: Collaboration and notifications
- **Zoom**: Meeting links in issues and pages
- **Salesforce**: Customer issue tracking

**Configuration Steps**:
1. Review integration requirements
2. Configure OAuth or API authentication
3. Map fields and data flows
4. Test integration thoroughly
5. Document configuration
6. Train users on integration features
7. Monitor integration health

## Global Configuration

### Jira Global Settings
**Issue Types**:
- Create and manage org-wide issue types
- Define issue type schemes
- Standardize across projects

**Workflows**:
- Create global workflow templates
- Define standard workflows (simple, complex)
- Manage workflow schemes

**Custom Fields**:
- Create org-wide custom fields
- Manage field configurations
- Control field context

**Notification Schemes**:
- Configure default notification rules
- Create custom notification schemes
- Manage email templates

### Confluence Global Settings
**Blueprints & Templates**:
- Create org-wide templates
- Manage blueprint availability
- Standardize content structure

**Themes & Appearance**:
- Configure org branding
- Manage global themes
- Customize logos and colors

**Macros**:
- Enable/disable macros
- Configure macro defaults
- Manage macro permissions

### Security Settings
**Authentication**:
- Password policies (length, complexity, expiry)
- Session timeout settings
- Failed login lockout
- API token management

**Data Residency**:
- Configure data location (US, EU, APAC)
- Ensure compliance with regulations
- Document data residency for audits

**Encryption**:
- Enable encryption at rest
- Configure encryption in transit
- Manage encryption keys

**Audit Logs**:
- Enable comprehensive audit logging
- Review logs regularly for anomalies
- Export logs for compliance
- Retain logs per policy (7 years for compliance)

## Governance & Policies

### Access Governance
**User Access Review**:
- Quarterly review of all user access
- Verify user roles and permissions
- Remove inactive users
- Update group memberships

**Admin Access Control**:
- Limit org admins to 2-3 individuals
- Use project/space admins for delegation
- Audit admin actions monthly
- Require MFA for all admins

### Naming Conventions
**Jira**:
- Project keys: 3-4 letters, uppercase (PROJ, WEB)
- Issue types: Title case, descriptive
- Custom fields: Prefix with type (CF: Story Points)

**Confluence**:
- Spaces: Team/Project prefix (TEAM: Engineering)
- Pages: Descriptive, consistent format
- 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

## Disaster Recovery

### Backup Strategy
**Jira**:
- Daily automated backups
- Weekly manual verification
- 30-day retention
- Offsite storage

**Confluence**:
- Daily automated backups
- Weekly export validation
- 30-day retention
- Offsite storage

**Recovery Testing**:
- Quarterly recovery drills
- Document recovery procedures
- Measure recovery time objectives (RTO)
- Measure recovery point objectives (RPO)

### Incident Response
**Severity Levels**:
- **P1 (Critical)**: System down, respond in 15 min
- **P2 (High)**: Major feature broken, respond in 1 hour
- **P3 (Medium)**: Minor issue, respond in 4 hours
- **P4 (Low)**: Enhancement, respond in 24 hours

**Response Steps**:
1. Acknowledge incident
2. Assess impact and severity
3. Communicate status to stakeholders
4. Investigate root cause
5. Implement fix
6. Verify resolution
7. Post-mortem and lessons learned

## Metrics & Repor