As of February 2022, all Trello accounts are associated with an Atlassian account, including Trello accounts managed by a Trello Enterprise. This page will help Enterprise admins understand the implications of these changes.
How will this impact my managed users?
Changes within Trello
For most users, the only change will be their experience logging in to Trello, as users will now be required to use Atlassian account.
If SSO is enforced for your Enterprise, your users will be required to log in through both your SSO provider as it is configured for your Trello Enterprise, and Atlassian account. Depending on whether your company also has an Atlassian organization and what the organization’s security settings are, this may be through SSO or with an email address and password. If the Atlassian organization uses the same SSO setup as the Trello Enterprise, the user will only have to go through SSO once.
If SSO is not enforced for your Trello Enterprise, users will not need to go through the two-step login process. Instead, they can log in with only their Atlassian account. After moving to an Atlassian account, their Trello password will no longer work. They will either need to set a password, or, if required by the Atlassian organization, log in with SSO—even if they weren’t using SSO for Trello before.
Changes for Atlassian organizations
If your company also has an Atlassian organization and has claimed its domain, then your managed users on that domain will be managed by both the Trello Enterprise and the Atlassian organization. The organization admin can change end users' profile information, enforce security settings, and deactivate or delete an Atlassian account.
Note that if a user’s Atlassian account is deactivated or deleted, their Trello account will be deactivated or deleted as well. This can only be reversed by the organization admin. Deactivated or deleted users will not count toward the number of licensed users for your Enterprise. However, Trello users who have been deactivated from your Enterprise will not automatically have their Atlassian account deactivated.
What’s not changing
This will not change users' access to Trello boards or workspaces, or other permissions within Trello.
Moving to Atlassian Access
Finally, if you are currently enforcing SSO and do not want your users to have to go through a 2-step login process, you have the option of moving your SSO configuration to Atlassian Access. Although Atlassian Access is a paid product, there's no charge for users with a Trello Enterprise license.
If you decide to consolidate your SSO settings and move to Atlassian Access, the following pages can help you with that process:
Was this helpful?