Is it possible to create a confluence account within a claimed domain?

[Deleted user]

We have a few claimed domains. External Confluence URL's are hidden for search engines. And yet is it possible to create an account without getting an invite?

if it is possible: how is this done? and what can we do to prevent?

Thanks!

[Ashok Shembde · Accepted solution]

Yes, it is possible to create a Confluence account within a claimed domain, but only under certain conditions. Here’s an overview of the process:

Creating a Confluence Account Within a Claimed Domain:

1. Administrator Setup: The organization’s admin first needs to claim the domain by verifying ownership through Atlassian’s Admin Hub. Once a domain is claimed, the organization has control over any accounts associated with it.

2. Account Creation Process:

   • User Creation: After the domain is claimed, users with email addresses on that domain can still create Atlassian accounts, including for Confluence, by signing up through the standard process (e.g., using their work email).
   • Domain Controls: The organization that controls the domain can enforce additional security requirements (e.g., mandatory SSO, 2FA) on those accounts.
   • Account Claiming: In some cases, if a user tries to create an account within a claimed domain, the organization's admin may need to approve the account or enforce security measures before the account becomes fully active.

3. Managed Accounts: Once an account is created under the claimed domain, it will become a managed account, meaning the organization can enforce policies, security settings, and other controls.

[Ed Letifov _TechTime - New Zealand_ · Accepted solution]

@[deleted] 

Please note, anyone can create an Atlassian Cloud in your domain. Just show up on id.atlassian.com and start registering with a completely fake email in your account – this will trigger a creation of an unverified user record. Unless they are able to receive an email on the address they enter – this is what it will stay as. This is why we (as a Solution Partner) usually recommend to NOT make the SSO policy default for anyone in your domain – this way all these rubbish accounts will fall into some other default policy (e.g. unbillable) which you can regularly review and clean up.

It's possible that in your case JSM account was created first – would be if you allow anyone to register there. See: https://support.atlassian.com/jira-service-management-cloud/docs/change-global-customer-permissions/

And then if your KB is private, but allows any JSM logged-in customer free access – that's how you get the same account in Confluence. They shouldn't be licensed, but account will be there. See: https://support.atlassian.com/jira-service-management-cloud/docs/restrict-access-to-knowledge-base-articles/

[Deleted user]

hi Ed,

thanks for the explanation and your valuable insights. we will investigate further! :)

regards

Folco

[Deleted user]

hi Ashok,

Thanks for your reply. It seems that an account within a claimed domain has created a confluence account. and after that a JSM account was created. We are still investigating.

i was just curious ;)