![]() I'd be happy to clear the air on that, but you can also see a collection of common questions regarding this migration here: Sorry for the concern that migration messaging caused. Additionally, you won’t be billed for Access for any Trello Enterprise users, so you do not need to deactivate them to lower your bill. Trello Business Class users and Trello Enterprise users are being paid for by a Trello admin, so you should discuss their Trello usage with them before deactivating them. “ Trello Free”, “ Trello Business Class”, and “ Trello Enterprise” tells you to what Trello product your Trello users have access. It may be less disruptive to your users if you choose to deactivate users who have not been active in Trello for a long time. ![]() “ Last Active Date” tells you when the user was last active in Trello. Once a user has completed this process, and “Using Atlassian account for Trello” is marked “Yes” then actions you take on their Atlassian account will impact their Trello account. “ Using Atlassian account for Trello” tells you if the user has finished connecting their Atlassian account to their Trello account. “ Added to you Access bill in April” tells you if the user will become a billable user if you don’t take on their Atlassian account before June. “ Email” tells you the email on the user’s Trello account that was claimed so that you can reach out to your users and discuss their Trello usage. csv includes information about your Trello users' Trello usage to help you decide which users to deactivate. csv export to your administrator portal to help you manage your bill while causing minimal disruption to your users. Second, you will not be billed for any Trello-only users that you deactivate. Below we provide more information on how to reach out to these users. You won't be billed for these new Trello-only users if they remove the company email on their Trello. If your employees are using their work email address on their Trello account for non-work related activities, we suggest you reach out to the Trello-only users and ask them to remove their work email address from their Trello account. I hope that helps clarify things a little. ![]() To answer the questions about Trello working with Okta, once your Trello accounts are migrated to Atlassian Accounts, it uses Atlassian's authentication service that sits on top of all of their Cloud products to handle authentication, so as long as you have Okta configured and working for other Atlassian Cloud products it should just start working for Trello post migration as well. If you have users that were only using Trello and weren't being managed in Atlassian Access previously, those will be new users in Access, and yes unfortunately they will incur additional Access costs. You just now have the option for then to use SSO to authenticate for Trello as well as Jira. For all users that are already being managed for SSO access to Jira there is no additional Access costs. Once this migration happens Trello is considered a part of that Atlassian account. Up until now, they had SSO for Jira but not for Trello, and I was not aware of which of my users were using Trello. Here's an example, for our company every employee has access to Jira, and there for has a account that is being managed by Atlassian Access. As far as additional costs for Atlassian Access, you will only consume additional Access licenses for users that you aren't already managing in Atlassian Access. We have Atlassian Access ourselves and I can help answer a couple of those questions.
0 Comments
Leave a Reply. |