Loom is now part of Atlassian. If your workspace has been migrated, Loom users are managed in Atlassian Administration, not in Loom’s own workspace settings. In that case the integration account needs the Organization admin role in your Atlassian organization, and a Loom workspace Admin role alone is not enough for AccessOwl to provision or deprovision users.
Capabilities
Provisioning
AccessOwl creates user accounts with the specified roles/permissions during access requests.
Deprovisioning
AccessOwl deactivates users in Loom during access revocations.
User Sync
AccessOwl periodically syncs a list of users along with their assigned roles/permissions.
Check which setup applies to you
Open your Loom Workspace Settings. If you see the banner “Loom is now a part of Atlassian. Manage settings and users in Atlassian Administration.”, your workspace is Atlassian-managed. Workspaces created from February 2026 onwards are Atlassian-managed by default.Atlassian-managed workspace
Users are managed in Atlassian Administration. You need Organization admin access to your Atlassian organization.
Standalone Loom workspace
Users are managed in Loom. You need Admin access to your Loom workspace.
Setup
Atlassian-managed workspace
1
Add Loom in AccessOwl
Either add a new application or open Applications and click the +-symbol, then continue.
2
Invite the integration account and assign Organization admin
AccessOwl shows you the integration account’s email address. Invite it into your Atlassian organization and promote it to Organization admin, following the steps in the Atlassian overview. Make sure the invite includes access to Loom.
The integration account needs Organization admin because that is the role with the broadest permissions for managing users and product access across your Atlassian organization. Without it, AccessOwl can connect to Loom but cannot invite, change roles for, or deactivate users.
Standalone Loom workspace
1
Add Loom in AccessOwl
Either add a new application or open Applications and click the +-symbol, then continue.
2
Invite the integration account as Admin
AccessOwl shows you the integration account’s email address. In Loom:
- Open the Manage Workspace Members page.
- Click Invite Members (top right).
- Enter the integration account’s email address.
- Select Admin from the role dropdown.
- Click Invite.
The integration account needs Admin because only Admins can invite members, change roles, and deactivate or reactivate users. Without Admin, the integration account cannot provision or deprovision users.
FAQ
Loom is now part of Atlassian: where do I manage users?
Loom is now part of Atlassian: where do I manage users?
In Atlassian Administration once your workspace has been migrated. The admin roles that govern user management and billing there are Org Admin, Site Admin, Billing Admin, and App Admin. The Loom workspace Admin role still controls in-product permissions inside Loom itself, but it no longer covers adding or removing workspace members.
Loom sync stopped working after the Atlassian migration
Loom sync stopped working after the Atlassian migration
A workspace part-way through the migration blocks the integration account at sign-in with a screen asking to complete the migration to Atlassian, which AccessOwl cannot click through. Reconnecting the integration lands on the same screen and does not help. Complete the migration in Atlassian, then confirm it landed by checking that Loom appears as a managed app in Atlassian Administration. AccessOwl resumes syncing on the next cycle.