Back to marketplace

Atlassian Access and Permissions Admin

Plan Jira and Confluence access changes safely: groups, permission schemes, space and page restrictions, SSO, offboarding, audits.

Business & Ops / Project Managementatlassianjira-admin
by AgentVoltv1.0.0
Free to sign up · every skill included with AgentVolt Pro

Before & after

Same prompt, same agent — the only difference is the skill.

Prompt“Manage user permissions and security settings across our Jira and Confluence instances”
Beforegeneric AI agent
Managing user access in Atlassian products requires understanding permissions at multiple levels. You can manage who has access to Jira projects, Confluence spaces, and specific boards or pages. Consider creating user groups to make permission management easier. Set up single sign-on if possible to centralize authentication. Restrict sensitive data by controlling who can view certain projects or pages. Regular audits help identify over-permissioned users. Document your permission structure so it's maintainable.
Afterwith Atlassian Access and Permissions Admin
ATLASSIAN ADMIN OPERATIONS

USER & PERMISSION MANAGEMENT

TASK 1: AUDIT CURRENT PERMISSIONS
• Jira projects: List all projects, users per project, permission levels
• Confluence spaces: List all spaces, members, page-level permissions
• Current groups: List user groups (Developers, QA, Marketing, etc.)
• Unused accounts: Identify inactive users (no login in 90 days)

TASK 2: DEFINE PERMISSION ROLES
  • Admin (full access, manage users/permissions)
  • Project Lead (manage project, board, team)
  • Developer (create/edit issues, comment, view backlog)
  • Viewer (read-only access)
  • Guest (limited read-only, specific projects)

TASK 3: GROUP MANAGEMENT
  • Jira-Admins (3 users) → Admin rights all projects
  • Engineering-Team (12 users) → Dev access backend/frontend/infrastructure
  • QA-Team (4 users) → Read + bug creation on all projects
  • Marketing-Viewers (2 users) → Read-only on Release Planning
  • Exec-Dashboard (5 users) → Limited dashboard view

TASK 4: CONFLUENCE SPACE SETUP
  • Engineering: Public (architecture, decisions), Restricted (performance, security), Private (retros)
  • Product: Public (roadmap, release notes), Restricted (competitive analysis)
  • HR: Private (policies, comp data, admins only)

TASK 5: SSO SETUP (Single Sign-On)
  • Connect to company identity provider (Okta, Azure AD, Google Workspace)
  • Enable SAML 2.0 authentication
  • Sync user groups from identity provider
  • Deactivate manual password management
  • Benefit: Automatic user sync; revoke access by removing from directory

TASK 6: ACCESS CONTROL BY SENSITIVITY

  PUBLIC (All employees)
    • Release notes, roadmap, architecture decisions
  
  INTERNAL (Team + stakeholders)
    • Technical design docs, sprint plans, performance metrics
  
  RESTRICTED (Exec + function leads)
    • Financial data, salaries, reviews, security vulnerabilities

TASK 7: JIRA PROJECT PERMISSION TEMPLATE
  • Project Lead → Administer project, assign users
  • Developers → Create/edit issues, vote, transition
  • Reporters → Create issues, comment, not edit
  • Viewers → Read-only

TASK 8: AUDIT & MONITORING
  • Monthly: Review new requests, flag inactive accounts
  • Quarterly: Audit permission changes, check scope creep
  • Annually: Full access review + certification

TASK 9: SECURITY SETTINGS
  • IP whitelisting (if sensitive data)
  • Session timeout (1 hour inactivity)
  • Two-factor authentication (admins + finance users)
  • Password policy (12+ chars, rotate 90 days for admins)
  • API token management (rotate quarterly)

TASK 10: OFFBOARDING CHECKLIST
  • Remove from user groups
  • Revoke project access in Jira
  • Revoke Confluence space access
  • Transfer owned content to new owner
  • Disable SSO account
  • Audit to confirm access removed
  • Timeline: Within 24 hours of departure

OUTPUT DOCUMENTATION
  • User access matrix (user | projects | spaces | role)
  • Permission scheme template (reuse across new projects)
  • SSO integration guide
  • Audit trail (log of permission changes)

ESTIMATED EFFORT
  • Initial setup: 2-3 days
  • Ongoing: 4 hours/month

About this skill

Atlassian permissions break in quiet ways: one edit to a shared scheme changes twenty projects, a restricted parent page hides a whole subtree, and SCIM overwrites the group you just fixed. This skill plans every access change with its blast radius, verification step, and rollback.

What it does

  • Troubleshoots 'she can't see it' by walking the access chain from account to product access to Browse to restrictions
  • Checks which projects share a permission scheme before any edit and copies it when only one project should change
  • Grants through project roles and groups, not individual users
  • Covers Confluence space permissions, page restriction inheritance, and anonymous access
  • Plans SSO rollouts with a break-glass admin, and offboarding that reassigns filters, dashboards, and automation actors

What you get

A change plan (layer, required admin role, blast radius, steps, verification, rollback) or a full access audit ranked by risk. Version-specific details are marked for you to verify in Cloud or Data Center.

Best for

Jira and Confluence site admins, IT and ops teams, and project admins who inherited a messy Atlassian setup.

SKILL.md preview

SKILL.md
---
name: atlassian-admin
description: Plan and check Atlassian admin changes for Jira and Confluence - users and groups, product access and seats, Jira permission schemes and project roles, issue security, Confluence space permissions and page restrictions, SSO and user provisioning, offboarding, anonymous access, and marketplace app review - with a blast-radius check before every change. Use when the user says "add these new hires to Jira", "who can see this project?", "lock down this Confluence space", "offboard a contractor", "why can't she see the board?", "set up SSO", "audit our Atlassian permissions", or "is it safe to change this permission scheme?".
---

… (sign up to view the full skill)
Sign up to view, copy, and install the full skill

More business & ops skills

View all Business & Ops skills →

Confluence and Jira Template Builder

Build one Confluence or Jira template people actually fill in: real-example structure, placeholders, roll-up reports, required fields.

Business & Ops

Confluence Space Architect and Cleanup

Make a Confluence space findable: shallow page tree, label taxonomy, navigation macros, and a CQL audit of stale and orphaned pages.

Business & Ops

Delivery Loop: Goal to Verified Close

Drive one deliverable from agreed goal and acceptance criteria to verified evidence and a real closeout, with nothing left orphaned.

Business & Ops

Jira JQL, Board and Automation Expert

Correct JQL on the first try, plus boards, dashboards, workflows, and automation rules that avoid Jira's silent traps.

Business & Ops