Appearance
Groups
A group is a named set of this workspace's people. Share a page with the group and everyone in it gets that level.
Groups are tenant data — a fact about one workspace, owned by its admin — which is why creating and populating one needs manage_groups rather than an operator.
Naming a group in a grant
A grant names a group as group:<uuid>, prefixed rather than bare. An account id and a group id are both UUIDs, and "shared with one person" versus "shared with forty" is not a distinction to leave to luck.
Precedence
At a single page, the most specific statement about who you are wins:
person → group → workspace → everyoneAcross pages, nearest still wins outright — an explicit none close to a page beats a group grant far from it. Without that, a group grant at the root would quietly reopen everything closed beneath it.
Two groups that disagree at the same page take the more generous. Otherwise adding somebody to a group could take access away, which is not what anybody means by adding them to a group. A revocation belongs on the page, where it is meant.
Only members can be in a group
Otherwise a group is a second, quieter way into a workspace.
No foreign key can enforce that, because group membership is tenant data while workspace membership is control plane — so the route enforces it, and removing somebody from the workspace takes them out of its groups.
There is no directory sync. People arrive by invitation or through a claimed SSO domain, and leave when an admin removes them.