User Accounts: Policy for Atlassian Cloud
Purpose: Ensure secure, verifiable access to Red Hat Jira and Confluence, and reduce the risk of orphaned or unauthorized accounts.
Audience: Red Hat associates, partners, and customers who use Red Hat Atlassian Cloud. This page is public.
Last reviewed: Oct 27, 2026 — Stacey Hamilton
Canonical for: Which email each group must use on Red Hat Atlassian Cloud. Login steps stay on Accessing the Atlassian Cloud environment.
Quick answer: Associates use the Red Hat SSO account. Partners use the official company email issued by their employer. A Red Hat or personal address is not allowed. Customers use their primary company email. PME may suspend accounts that do not follow this. There are no exceptions after a user or group has moved to the designated email.
Where to start
Who you are | Read this section | Do this first |
|---|---|---|
Red Hat associate | Use your Red Hat SSO account | |
Partner | Employer email, not a Red Hat or personal address | |
Customer | Primary company email | |
Two accounts after migration | Send both email addresses to PME | |
Account that does not follow this policy | PME may suspend or revoke access |
Scope
This policy applies to all Red Hat associates, partners, and customers who use Red Hat Atlassian Cloud products.
Policy Statement
Email Requirements
Red Hat associates must use their SSO account provisioned and managed by Red Hat IT.
Partners must use their official, designated company email address (issued by their primary employer). Use of Red Hat-provided or personal email accounts is prohibited.
Customers must use their primary company email address to log in to Atlassian Cloud.
Security Rationale
Access is controlled via email identity. Partner and customer company emails ensure offboarding is handled by the user’s employer. Non-company emails create a security gap where Red Hat may not be notified when access should be revoked.
If you have two Atlassian accounts after migration (historical Data Center email vs. current company email), see Recommended Steps for Handling Dual-Account Scenarios.
Policy Compliance
Compliance Measurement
Compliance is mandatory and enforced through regular audits to identify non-compliant email accounts.
Enforcement
PME may suspend or revoke access for accounts using non-compliant email addresses.
Exceptions
No exceptions are granted once a user or group has been migrated to the designated email standard.
See also
Change log
Date | Change |
|---|---|
Oct 27, 2026 | Applied the public-page header and a where-to-start table. Email rules are unchanged. |
May 27, 2026 | Added customer guidance and a link to the dual-account page. |