Project Management AtlassianAdminConfig

Atlassian Admin

Atlassian product administration and organization management.

$skillfish add ~skills/atlassian-admin

Real Examples Get Started Models & Context

Real Conversations

See how the Atlassian Admin skill responds to actual requests. These are representative examples of what your AI agent will produce.

You

We have 150 users across Jira, Confluence, and Bitbucket. We just had a security audit and need to review who has admin access and remove people who left the company. How do I do this efficiently?

Agent

Atlassian Access Audit — 150 Users

Step 1: Export user list from Atlassian Admin

Go to admin.atlassian.com → your organization
Users → Export users (CSV) Columns: email, display name, product access, last active date, account status

Step 2: Cross-reference with HR offboarding list Match exported emails against your HR system's terminated employees list. In Google Sheets:

=IFERROR(VLOOKUP(A2, TerminatedList!A:A, 1, FALSE), "Active")

Flag all matches as "Immediate deactivation required."

Step 3: Admin access audit Filter the export for users with org-admin or site-admin roles. Best practice:

Org-admin: Maximum 2–3 people (IT leads only)
Site-admin per product: Maximum 3–5 people

Step 4: Remediation actions

Action	How	Timeline
Deactivate terminated users	Admin console → User → Deactivate	Immediate
Remove excess org-admins	Admin → Roles → Edit	This week
Enforce SSO	Admin → Security → SAML SSO	30 days
Enable 2FA enforcement	Admin → Security → Two-step verification	7 days

Step 5: Prevent recurrence

Connect Atlassian Access to your IdP (Okta, Azure AD) — users deprovisioned in IdP are automatically deactivated in Atlassian
Set up a quarterly access review in your GRC tool or calendar

Want me to write the SAML SSO configuration steps for Okta or Azure AD?

You

We're on Atlassian Server (Jira + Confluence) and our license expires in 6 months. Atlassian is pushing us to Cloud but we have 200 users, heavy customization, and some compliance concerns about data residency. How do we approach this migration?

Agent

A Server-to-Cloud migration at 200 users with heavy customization and compliance requirements is a real project — 8 to 16 weeks of sustained effort from someone who owns it. The companies that struggle are the ones who treat it as an IT ticket rather than a program with a plan, a budget, and an owner.

Pre-migration audit — do this before anything else

You need a full inventory before you touch the migration tooling. The most expensive surprises in Atlassian Cloud migrations are the ones you discover midway through.

Jira audit checklist:

Custom fields: list every custom field, who uses it, whether it maps to a Cloud equivalent
Workflows: export all workflow configurations — complex approval chains, custom post-functions, and validators often rely on Server-only capabilities
Automation rules: Jira Server uses Automation for Jira (or ScriptRunner) — Cloud uses native automation with a different rule syntax; rules need to be rebuilt, not migrated
Apps/plugins: go to your Atlassian Marketplace account and check every installed app for Cloud compatibility. Filter to "Server" and "Cloud" versions. Some Server apps have no Cloud equivalent — this is your highest-risk item.
Permission schemes and project roles: complex permission matrices often need to be simplified before migration

Confluence audit checklist:

Macros: Server macros that have no Cloud equivalent will render as broken content post-migration. Identify these before you migrate.
Spaces and page count: large Confluence instances (>50,000 pages) have additional migration complexity
Team Calendars, Questions add-ons: check Cloud availability

Compliance and data residency — the specific answers

Atlassian Cloud offers data residency selection for Jira and Confluence on Premium and Enterprise plans. Available regions: US, EU (Frankfurt), Australia, and a few others. This means your data at rest stays in your selected region. Verify this covers your specific requirement — data residency is not the same as data sovereignty or government-grade isolation.

For more stringent requirements:

FedRAMP: Atlassian has FedRAMP Moderate authorization for Jira Software, Confluence, and Jira Service Management on the US region. If you're in a regulated US federal context, this is the path.
GDPR: Atlassian provides a Data Processing Agreement (DPA) for Cloud customers — request it from your account team. It's available but not automatically sent.
SOC 2 Type II: Atlassian Cloud holds this; reports are available under NDA from your account team.
HIPAA: Not currently covered under Atlassian's BAA program — if this applies to you, confirm before committing.

If your compliance concern is about a specific regulatory framework, name it precisely — the answer changes depending on whether this is SOC 2, ISO 27001, HIPAA, or something else.

Migration path options

Method	Best for	Notes
Atlassian Cloud Migration Assistant	Most organizations	Built-in, free, recommended starting point
Manual export/import	Small, simple instances	CSV/XML export — loses history, not practical at 200 users
Mindville (now Insight) / Botron	Complex data models	Third-party; adds cost but handles edge cases better

Recommended approach for your situation: Start with the Cloud Migration Assistant for a dry-run migration to a staging Cloud site. This surfaces app compatibility errors and data integrity issues before you touch production. You can run multiple dry runs at no additional cost.

The "migrate and freeze" strategy

Before you begin migration, freeze customizations. No new custom fields, no new workflow modifications, no new app installations for 6 weeks before migration date. Every change added to a live Server instance during migration prep is a change you have to account for twice.

This sounds restrictive but it's the single most effective way to reduce migration complexity. Communicate it to your teams early with a clear end date.

Realistic timeline at 200 users

Phase	Duration
Audit and app compatibility review	2–3 weeks
Staging migration and testing	2–3 weeks
App rebuild / replacement procurement	2–4 weeks (parallel)
User acceptance testing with team leads	1–2 weeks
Production cutover + hypercare	1 week + 2 weeks support

Total: 8–14 weeks for a clean migration. If you have complex apps with no Cloud equivalent that require custom replacement, add 4–6 weeks.

License timing

With 6 months until Server license expiry, you have enough runway if you start now — but not if you start in month 3. Atlassian also offers Server license extensions on a case-by-case basis; your account team can discuss this if the timeline gets tight.

What apps are you running on Server — that's the first thing I'd want to inventory with you?

Get Started

How to install and use this skill in your preferred environment.

Skills are designed for AI coding agents (Claude Code, Cursor, Windsurf) and IDE-based workflows where the agent can read files, run scripts, and act on your codebase. Web-based AI can use the knowledge and frameworks, but won't have tool access.

Models & Context

Which AI models and context windows work best with this skill.

Recommended Models

Best

Claude Opus 4 Claude Sonnet 4 GPT-4.1 Gemini 2.5 Pro Grok 3 Kimi K2

Good

Claude Haiku 4.5 GPT-4.1 mini Gemini 2.5 Flash Grok 3 mini

Larger models produce more detailed, production-ready outputs.

Context Window

This skill's SKILL.md is typically 3–10 KB — fits in any modern context window.

8K Skill only

32K+ Skill + conversation

100K+ Skill + references + codebase

All current frontier models (Claude, GPT, Gemini) support 100K+ context. Use the full window for complex multi-service work.

Pro tips for best results

1

Be specific

Include numbers — users, budget, RPS — so the skill can size the architecture.

2

Share constraints

Compliance needs, team size, and existing stack all improve the output.

3

Iterate

Start with a high-level design, then ask follow-ups for IaC, cost analysis, or security review.

4

Combine skills

Pair with companion skills below for end-to-end coverage.

Ready to try Atlassian Admin?

Install the skill and start getting expert-level guidance in your workflow — any agent, any IDE.

$skillfish add ~skills/atlassian-admin

← Browse all 169 skills