As of late October 2024, Loom is part of the Atlassian platform. Atlassian organization admins can create new Loom workspaces and manage Loom users and product access for these workspaces from Atlassian Administration.
There’s a limitation you should be aware of if you’re a customer with a Loom workspace on an Enterprise plan purchased from loom.com and you also have a Loom workspace created from Atlassian Administration or another Atlassian site.
Limitation
Users who are part of an existing Loom workspace on an Enterprise plan are currently unable to join an Atlassian Loom workspace.
We’re still integrating the rest of Loom into the Atlassian platform, which includes migrating content and user accounts from Loom workspaces on an Enterprise plan. We estimate we’ll complete the migration in mid-2025. Until it’s completed, if you invite a user who is a member of a Loom Enterprise workspace to an Atlassian Loom workspace, they won’t be able to access the latter workspace or merge their Loom and Atlassian account profiles.
Workarounds
There are some workarounds to give a user who’s part of an existing Loom workspace on an Enterprise plan access to an Atlassian Loom workspace in the meantime, if necessary.
For example, you may want to create an Atlassian Loom workspace to trial Loom functionality in Confluence or Jira. There are two workarounds listed below. Consider the implications of each workaround to determine which one, if any, is appropriate for you.
Workaround options:
This workaround involves removing the user from the Loom Enterprise workspace, then inviting them to the Atlassian Loom workspace. When you do this:
-
This user won’t have access to the Loom Enterprise workspace anymore, including any content they created.
-
Some or all content created by this user will be permanently deleted, depending on the choice you make upon removing them from your workspace.
Steps
-
Follow the instructions to delete members in a Loom workspace. If you’re using SAML SSO, remove the user from your identity provider before you delete them from your workspace. If you don’t remove the user from your identity provider, their Loom account will be created and given access to the workspace again.
-
Follow the instructions to invite a user to Atlassian and give them product access.
This workaround involves inviting the user to the Atlassian Loom workspace using an email alias. An email alias is an alternative email address for an email account.
When you do this:
-
This user will be able to access the Atlassian Loom workspace without losing access to the Loom Enterprise workspace.
-
This user won’t be able to merge their Loom and Atlassian account profiles in the future.
Steps
-
Follow the instructions to invite a user to Atlassian and give them product access. When you’re prompted to enter the user’s email address, enter an email alias instead.
An email alias is created by appending the plus symbol (+) followed by any string of letters or numbers to the username in an email address. For example, an email alias for the email address jane@acme.com could be jane+test@acme.com
Note: You don’t need to set up anything in your email system to enable email aliases. Email systems will recognize an email alias and direct any incoming email to the inbox of the main email account. For example, any emails to jane+test@acme.com will be directed to jane@acme.com.