Working · 2026-11PrimaryExpansionProduct

Domain verification to claim work accounts

Let a company prove it owns its email domain and then take control of every account employees created with that domain, with security policies available in a paid admin tier.

Also called: managed accounts, domain claim

Claim and evidence

The claimWhen you claim accounts to manage, we let these users know that your organization manages their account.

Atlassian · support.atlassian.com · 2020-12-16

What the numbers show

No published number for this tactic has passed our word-for-word check yet, so there is no chart.

Why it works

Diagram, not data
Admin verifiesthe emaildomainClaims accountson that domainUsers told thecompany managesthemSecuritypolicies in apaid tier
Admin verifies the email domainClaims accounts on that domainUsers told the company managesthemSecurity policies in a paid tier

Individuals sign up freely with work emails, and the company later needs control for security and offboarding. Account claiming gives IT that control and is a natural moment to sell the admin and security tier that applies policies to the claimed accounts.

How to run it

  1. Let admins verify a domain by DNS or a hosted file
  2. After verification, let them claim all or selected accounts on that domain
  3. Notify users that their account is now managed by the company
  4. Offer authentication and security policies on claimed accounts in a paid tier
  5. Prevent the same account being claimed by two organizations

Before / after

Before
Admin
You can only manage users you invited
Work accounts scattered, no company control
After
Admin
Domain verified
Accounts on your domain
Claim accounts
Security policies need the paid admin tier
Domain verified, accounts ready to claim

Generalised wireframe of the pattern, not a copy of any company's screen.

Ways to run it

Design options to test, not promised results.

  1. Option AClaim all or selected

    After verification, let admins claim every account on the domain or pick specific ones, as Atlassian does.

  2. Option BPolicies as the upsell

    Keep claiming free but put authentication and security policies for claimed accounts in a paid tier.

  3. Option CDNS or hosted file

    Offer more than one verification method so IT can prove ownership without waiting on another team.

Dated examples

  1. —

    Atlassian

    After verifying a domain, Atlassian org admins can claim accounts on it, making them managed accounts they can edit, deactivate or delete; applying authentication and security policies needs an Atlassian Guard Standard subscription.

    “When you claim accounts to manage, we let these users know that your organization manages their account.”
    ✓ quote checked word-for-word on the page

    support.atlassian.com · 2020-12-16

Does it still work?

Workingas of 2026-11

Current Atlassian user-management docs describe the flow. source

Risks

  • Users may lose control of personal work in claimed accounts
  • Domain disputes between subsidiaries or agencies
  • Charging for basic security can be criticised as an SSO tax

Sources

  1. support.atlassian.com · Atlassian Support · 2020-12-16
    “More control over the Atlassian accounts on your company’s domain”
    ✓ quote checked word-for-word on the page

Change log

  • 2026-11-20 — harvest v0.1 (pass2-expansion-ops)