Plan requirement
| Subscription | Any plan |
| Access | Admin |
Users are added to an organisation automatically by their email domain, when they submit a request for the first time or register. Whether the users you already have come along depends on one thing: whether their address is verified.
Set it up
- Open the organisation and add its email domains.
- Save.
- Check that a new user from that domain is assigned.
- Look for existing users from that domain who did not move, and add them by hand.
What happens to the users you already have
Verified addresses move on their own. Users with a verified email address on that domain are added to the organisation when the mapping is created, so step four covers only what is left.
Unverified addresses do not. Somebody who raised a ticket before the mapping existed and never verified their address has to be added manually. Nothing flags them, which is why step four exists at all.
Where users may belong to multiple organisations, existing users are added to the new organisation with the shared domain and keep the ones they already had. The change may not show immediately.
The rule that catches people
Add a domain to an organisation when that domain is already mapped to another organisation, and new users are mapped only to the first organisation sorted alphabetically by name. That holds even if you allow users to belong to several.
So a shared domain does not spread users across both organisations: it quietly picks one, on alphabet. If you were expecting both, check which name comes first.
Add every domain, and never a public one
Companies use several: an old name after a rebrand, a country domain, a subsidiary. Users on the ones you missed stay unassigned and nothing flags it.
And never map a generic consumer email domain. It is the obvious warning and it still happens, and it assigns thousands of unrelated people to one organisation, which is slow to unpick.
Comments
0 comments
Article is closed for comments.