Problem Statement

Organizations that adopted Jira Cloud before the Guest Access feature was introduced now have external stakeholders (vendors, clients, contractors) provisioned as fully licensed users — even though they only require limited, project-scoped access. The current Guest Access feature is functionally ideal for these users, but Atlassian's policy explicitly prohibits converting current or former paid users to guests.

This creates a situation where early adopters are penalized: organizations that onboarded external collaborators before Guest Access existed must continue paying for full licenses for users who only need guest-level capabilities.

Proposed Solution

Introduce an admin-initiated, in-place conversion workflow that allows site administrators to transition existing licensed users to the Guest role — with appropriate safeguards — without requiring account deactivation or re-invitation.

The workflow should:

1. Preserve data integrity — All issue history, @mentions, comments, and audit trail entries remain attributed to the same account ID

1. Validate eligibility — Confirm the user's actual usage aligns with Guest limitations (single project, no admin access) before conversion

1. Notify the affected user — Clearly communicate the change in access scope

1. Be reversible — Allow upgrading a Guest back to a licensed user if needs change

1. Support bulk operations — Allow admins to select multiple users for conversion when transitioning a batch of external collaborators

Why This Matters

• Fair treatment of early adopters — Organizations shouldn't be penalized for onboarding external users before Guest Access existed

• License cost optimization — Frees paid seats for users who genuinely need full access

• Reduced admin overhead — Eliminates risky workarounds (deactivate → re-invite) that admins are currently tempted to use

• Better security posture — Guests have a deliberately reduced permission surface, which is more appropriate for external stakeholders