A role decides what someone can do. This decides which websites they can do it to. The two work together.
Why you would
The usual cases:
- An agency or contractor working on two of your fifteen sites.
- A group inside a large organisation that should only see its own brand or region.
- A client who should see their own site and nobody else's.
- A new starter you want to give a narrow surface to for their first few weeks.
How it works
Open Team, choose the person, and assign them the specific websites they should have. From then on, that is the whole of the product for them. Sites they are not assigned to do not appear in their lists, their dashboard, their scan history or their notifications. There is no partial view where they can see that something exists but cannot open it.
What it does not change
Their role still applies within the sites they can see. Restricting someone to two websites does not stop them doing the things their role permits on those two. If you want to narrow what they can do as well as what they can see, change their role too.
Adding a new site later
A restricted person does not automatically get access to sites you add afterwards. That is deliberate, and it means you should check assignments when you add a site a contractor is meant to work on.
A note for agencies
If you manage sites for several unrelated clients, consider separate workspaces instead. Per-website access is the right tool inside one organisation. Separate workspaces give you cleaner separation between clients who should never learn of each other's existence. See Workspace settings.