Loom’s Atlassian Integration: What Users Need to Know
Posted:
Product News
Read Time:
Summarize with AI
If you try to sign up for Loom today, you can’t do it without creating an Atlassian account first. That wasn’t always the case.
This started after Atlassian acquired Loom in 2023. Since then, Loom has been moved onto Atlassian’s account, organization, and billing system.
New users must create an Atlassian account to access Loom. Existing Loom accounts are being migrated into Atlassian-managed organizations, even if Loom is the only product you use.
But Loom still records and shares videos the same way. You can record your screen, camera, or both, and share videos as before. What has changed is everything around that experience, like how accounts are created, who owns a workspace, how users are added or removed, and how subscriptions are billed.
For teams already using Jira or Confluence, this setup is familiar because Loom now behaves like the rest of their Atlassian tools. But for educators, creators, freelancers, and small teams who use Loom as a standalone tool, the experience is different.
What Is Loom’s Atlassian Integration?
Loom’s Atlassian integration is a change in where Loom is managed, and not its recording features.
After the acquisition, Atlassian began migrating Loom workspaces into Atlassian Administration, the same control layer used for Jira, Confluence, and Trello. This is the system that handles user identity, workspace ownership, security settings, and billing across Atlassian products.
If your Loom workspace is integrated, three things change at a system level:
Account Identity
Your Loom profile (email, name, avatar, login credentials) is now tied to an Atlassian account. If you already had one with the same email, you’re prompted to merge.
After that, Atlassian becomes the source of truth for your user profile rather than Loom’s legacy account system.
Administration And Access Control
For customers who purchase Loom through Atlassian or migrate their subscription, user management and admin controls move into Atlassian Administration. This is the same admin interface used to manage users for Jira and Confluence.
For legacy Loom users who have not migrated, user management may continue to happen inside Loom.
Billing & Subscriptions
Loom billing only moves to Atlassian if the subscription is purchased through Atlassian or explicitly migrated.
In those cases, invoices are issued by Atlassian, and plan changes are managed through Atlassian’s billing system. Existing Loom subscriptions purchased directly from Loom may continue to be billed separately until they are migrated.
So, what doesn’t change is the Loom product itself. Recording, sharing links, basic editing, and playback work the same way. The integration affects governance.
This distinction is important because it explains why some users barely notice the change, while others immediately run into questions about access, roles, and billing.
” Great Loom alternative for our customer support team, easy to use with no friction if you want quick recordings that you want to share with people. good luck!
Fatos
Founder
What Changes for Loom Users?
Most people don’t notice the Atlassian change while recording a video. You notice it when you sign in, manage users, or deal with billing.
Here are the differences users actually run into.
You May See New Sign-In Or Merge Prompts
Some users create a Loom account and continue normally. Others later see prompts to link or merge accounts when accessing settings, billing, or admin features.
Which path you see depends on your email and workspace settings, and whether Atlassian systems are involved behind the scenes. This inconsistency is why two Loom users can have different login experiences.
Where You Manage Users And Billing May Change
If your Loom subscription is managed through Atlassian, user access and billing are handled outside Loom’s original settings. You’ll be redirected to Atlassian’s admin screens to add users, adjust seats, or view invoices.
If your subscription is still managed directly through Loom, these controls stay where they always were.
Ownership And Control Can Feel Less Obvious
In smaller teams or solo setups, it’s not always clear who controls a workspace once Atlassian admin tools are involved. Actions that were previously done by a Loom workspace owner may now depend on who has admin access elsewhere.
This doesn’t affect video creation, but it does affect who can make account-level changes.
The changes are administrative, but they’re noticeable if you manage users, payments, or multiple workspaces.
Why Many Users Are Concerned
The concerns start after users notice the changes above.
Forced Account Creation
Loom sign-up and usage flows are no longer consistent for all users. Some people create a Loom account without ever seeing Atlassian. Others are later prompted to link or merge accounts when accessing billing, admin settings, or workspace controls.
Because these prompts appear conditionally and not at the point of sign-up, users often don’t know when an Atlassian account becomes required or what action triggered it.
If Loom is the only Atlassian product you use, this feels unnecessary and difficult to predict.
Pricing Uncertainty
Loom now supports multiple billing setups. Some subscriptions are billed directly through Loom. Others are billed through Atlassian.
Because these billing paths behave differently, users don’t have a single reference for how pricing, seat limits, or renewals will apply to them in the future. Even without immediate price changes, that lack of clarity makes long-term planning harder, especially for small teams and independent users.
Platform Lock-In
When Loom accounts, billing, or admin controls are managed through Atlassian, switching tools later involves more than exporting videos. Users may need to unwind account links, permissions, and subscriptions managed outside Loom itself.
This doesn’t prevent switching, but it raises the effort required. For users who chose Loom because it was simple and standalone, that added dependency is a concern.
Product Direction Shift
Loom built its user base as a standalone tool. Atlassian’s products are designed to work within a broader platform.
As Loom becomes more connected to that platform, users question how future decisions will be made. The concern is whether Loom will continue prioritizing lightweight, independent use cases or increasingly optimize for teams already using Jira, Confluence, and other Atlassian tools.
” Quit paying for Loom and try this. If you’re still using Loom, then save yourself the money and transfer to Dadan! Support replies quickly, the AI features (transcript, title, …) work well, the recording works well.
Tibo Geets
Co-Founder
Who This Integration Is Best and Worst For
Whether Loom still fits your setup now depends less on how you record videos and more on how much structure you’re already comfortable managing.
Works Better If
If your team already uses Atlassian tools, this change is likely routine rather than disruptive.
Product and engineering teams using Jira or Confluence already manage users, permissions, and billing in Atlassian’s admin system. Adding Loom doesn’t introduce a new layer, it fits into one you already use.
Larger organizations benefit from centralized control. Account policies, access rules, and billing live in one place, rather than being split across tools.
IT-managed environments where SSO, domain controls, and admin oversight matter will see Loom behaving more like the rest of their stack.
Less Ideal If
If you adopted Loom because it stayed out of the way, the integration can feel heavier.
Solo users, educators, and independent creators often don’t need organization-level admin, billing consoles, or account linking.
Small teams and startups that move quickly may find it harder to keep track of where things are managed, especially when billing, users, and ownership don’t all live in Loom anymore.
Anyone who wants a clearly standalone tool may feel less comfortable committing long-term when future changes depend on how a larger platform evolves.
So, the question is whether the surrounding structure matches how you prefer to work.
You don’t need to make a big decision today. But you do want to stay ahead of how your workspace is set up.
Review New Terms and Pricing
First, check where your Loom subscription is currently billed and what terms apply. Loom plans billed directly through Loom follow one set of rules. Plans managed through Atlassian follow another.
Even if your price hasn’t changed, look at renewal terms and cancellation rules. This gives you clarity on what applies now.
Monitor Account and Workspace Changes
Keep an eye on how your workspace is handled over time. If you begin seeing prompts to link accounts, manage users elsewhere, or access settings outside Loom, that’s a signal your workspace is being managed differently than before.
These changes don’t affect recording, but they do affect ownership and control. It helps to notice them early rather than after you need to make a change.
Backup Important Content
Loom has been clear that videos aren’t going anywhere. Still, if Loom is tied to client work, teaching material, or internal documentation, exporting important videos is a sensible precaution.
This is to make sure you’re not locked into a single tool for content you rely on.
Assess Long-Term Dependency Risks
Ask yourself how comfortable you are with Loom becoming part of a broader platform. If Loom is one tool among many Atlassian products you already use, this may not matter.
If Loom is the only one, consider whether you’re okay with future changes being driven by decisions outside Loom itself.
There’s no right answer here. It depends on how much control and independence you want from your tools.
Consider Alternative Platforms If Flexibility Matters
If you prefer tools that stay clearly standalone, this is a good moment to evaluate alternatives before your workflow depends more heavily on account structures or billing systems you didn’t choose initially.
You don’t need to switch immediately. But knowing your options gives you leverage and peace of mind.
” Perfect loom alternative. I really like this product – it’s the perfect alternative to Loom. Simple, efficient, and exactly what I needed.
Trystan Danylo
Director of Design
Best Loom Alternative
If you’re evaluating Loom and care about flexibility, control, and a clear billing or account boundary, a tool like Dadan is a strong Loom alternative. It’s a separate video platform focused on screen and webcam recording plus collaboration, editing, and hosting, without being tied to a broader suite.
Here’s how Dadan compares with Loom in ways that matter for users who don’t want platform lock-in or shared account control:
Standalone Recording and Hosting
Dadan lets you record your screen, webcam, or both, and store videos in a cloud library that you control. It supports basic editing, interactive elements (like quizzes and polls), and secure sharing directly from its platform.
This means you can manage recordings, access, and shared links from one tool, without relying on an external admin system or account layer.
Team Collaboration and Video Management
Dadan includes collaboration features designed for teams, like shared folders, team libraries, and commenting or feedback tools. You can organize your videos using Teams, folders, and tags, and control who can view or interact with shared content through permissions and secure sharing options.
For teams that use video to communicate updates, onboarding, training, or async feedback, these capabilities help keep content structured without requiring complex platform management.
Editing and AI-Assisted Features
Dadan’s built-in video editor lets you trim, split, and refine recordings. It also offers AI-assisted capabilities, such as automatic transcription, chapter creation, and metadata generation, to make videos easier to manage and reuse.
These features help you produce polished, searchable content without needing separate tools for editing and enhancement.
Pricing Structure
Dadan’s pricing is tied directly to the plan you choose on Dadan’s platform, with a free tier that includes basic recording and a paid tier that adds unlimited storage, advanced editing, and team features.
Some use cases where Dadan fits well are:
Educators and trainers who need secure, organized video libraries
Remote teams that share updates and feedback asynchronously
Content creators and marketers who want editing plus interactive video elements
Small businesses and freelancers who want clear control over billing and accounts
In each of these scenarios, Dadan lets you record, edit, share, and host video without being pulled into a larger platform’s account or billing system, which is precisely the concern some Loom users have with the Atlassian integration.
Conclusion
The key takeaway is clarity. Know how your Loom account is set up today. Know where billing and admin control sit. And decide whether you’re comfortable with Loom becoming part of a larger platform, or whether you’d rather use a tool that stays clearly standalone.
There’s no single right choice. But understanding the trade-offs now puts you in control later.
FAQs
When did Loom become part of Atlassian?
Atlassian announced its acquisition of Loom in 2023. Since then, Loom has been gradually connected to Atlassian’s account, admin, and billing systems. The rollout has been incremental rather than a single switch.
Will Loom users be required to create an Atlassian account?
Not in every case. Some users can sign up for and use Loom without seeing Atlassian. Others are prompted to link or merge accounts later, usually when accessing billing, admin settings, or workspace controls. Whether this happens depends on how the workspace is managed and how the subscription is billed.
Will existing Loom accounts be migrated to Atlassian?
Existing Loom accounts and videos are not removed or replaced. Loom has stated that users will not lose video content or functionality. Some accounts may be linked to Atlassian systems over time, particularly if billing or admin management moves there, but this does not automatically change how videos are recorded or shared.
