Introducing Confluence in the organization goes great, but somehow users keep creating organizations (and registering products) within the claimed domain.
The good news is that we get the notifications, the bad news is that ist's a hardship to get these organizations deleted.
Obviously the solution would be to prevent users from the claimed domain(s) to create /register the new organizations, which they usually do by mistake.
How can I configure acces in such a way that (claimed) users are not allowed anymore to create new organizations and register products, so they keep working within the managed boundaries of our own organization?
Hi @Caspar Laar and welcome to the Community.
It sounds as if you have too many org and site admins.
You may start here
and then look at access, permissions, groups etc., including permissions for spaces with anonymous access (if that applies).
@Caspar Laar Once you have the user permissions sorted out, the following posts may (or may not 🙃) help you with preventing it from happening again:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the info and asnswers!
My problem is 100% similar to the one described in the 'Rogue Sites' topic. Seems we need the Enterprise license to be able to control these product registrations from managed accounts.
Quite annoying that such a basic administrative functions is hidden in the most expensive license....
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.