Accessing the Atlassian Cloud environment
Purpose: Tell each person how to sign in to Red Hat’s Atlassian Cloud site, including new hires.
Audience: Red Hat employees, customers, and partners. This page is public.
Last reviewed: Oct 12, 2026 — Stacey Hamilton
Canonical for: Public login steps for redhat.atlassian.net. The steps for each group stay on this page. Licensed associates can use the Agile Tooling and Knowledge Hub for internal policy.
Quick answer: Use the table to find your group, then follow that section. Red Hat employees, including new hires, sign in with their primary Red Hat email through auth.redhat.com. Customers and partners use the email issued by their employer. Jira: https://redhat.atlassian.net/jira/for-you. Confluence: https://redhat.atlassian.net/wiki. If you cannot get in, open a ticket or email jiraconf-sd@redhat.com.
Where to start
Who you are | Read this section | Do this first |
|---|---|---|
Red Hat employee or new hire | Primary Red Hat email, then auth.redhat.com | |
Customer | Email issued by your employer | |
Partner | Employer email, not a former @redhat.com address | |
Anyone who cannot log in | Try incognito, then choose the redhat site | |
Inactive, deactivated, or suspended account | Match your status in the table, then follow that row |
Red Hat employees
This section is for Red Hat employees, including new hires.
Use your primary Red Hat email (typically your Kerberos ID before the
@domain).Complete login through internal SSO at auth.redhat.com.
Email aliases do not work. SSO does not authenticate them. They are not accounts.
Account provisioning may take time on your first login. This is expected.
Confluence access can be delayed because of licensing. If you see a login error, wait about 1 hour and try again.
If you have not logged in for 45 days, your account may be marked inactive. Open a ticket to regain access. This is a Red Hat policy. Atlassian does not automatically deactivate accounts for inactivity.
Customers
Use the email address issued by your employer. See the User Accounts policy.
If your company already uses Atlassian Cloud, that login is the same one you use for Red Hat’s site. Use the app switcher (nine dots, top left), open the menu under Jira, and choose the site named redhat.
If your company does not use Atlassian Cloud and login fails, a password reset grants access.
Partners
Log in with the email address your company issued for its own systems, not a former
@redhat.comemail. See the User Accounts policy.If you have two Atlassian accounts after migration, see Recommended Steps for Handling Dual-Account Scenarios.
Account status
Status | What it means | What to do |
|---|---|---|
Inactive (Red Hat policy) | Account not used for 45+ days | Open a ticket with PME |
Deactivated | Disabled by an org administrator | Open a ticket with PME. Admin reactivation may be required. |
Suspended | Disabled by the user’s employer IdP or IT | Contact your company’s IT team. Red Hat cannot fix partner or customer suspended accounts. |
Log-in troubleshooting
For login support, open a ticket or email jiraconf-sd@redhat.com if you cannot open a ticket.
Issue / Error | Troubleshooting steps |
|---|---|
“Something went wrong on our end” |
|
First-time login
When logging into Cloud for the first time you may see:
A screen suggesting projects to join. These may not be tailored to you. Click “Show all projects” to find relevant ones.
A screen displaying various roles.
A custom onboarding screen with an introduction to Cloud.
In Jira Cloud, spaces are the new name for what was called projects in Data Center. See Atlassian’s new navigation documentation.
See also
Change log
Date | Change |
|---|---|
Oct 12, 2026 | Added a where-to-start table so employees (including new hires), customers, and partners each have a section. Applied the public-page header. |