Organizations
The payments team should see payments findings and not everyone else's, while your security lead needs all of it. A single flat list cannot express that. A tree can.
Organizations are that tree. Grant a role on a parent and it applies to every child, so model your tree on how you hand out responsibility. Do not copy your org chart if it does not match who actually owns what.
Prerequisites
Each action needs its own permission: orgs:create, orgs:update or orgs:delete.
Create an organization
- Open Settings › Organizations and choose New organization.
- Enter a Name.
- Choose a Parent. Without one, it goes directly under the root.
- Choose Create.
What you should see
The new organization appears indented under its parent. Anything in it also counts towards every parent above it.
Rename or move one
Use the actions menu on the row.
Move puts an organization under a new parent, and what it holds joins that parent and every parent above it. An organization cannot move under itself or one of its own children.
Moving changes who can see things. People with a role on the old parent lose sight of it, and people with a role on the new parent gain it. Check your groups before you move a large branch.
Delete one
Only empty organizations can be deleted. Move what it holds and its child organizations out first.
The root
Your tenant has one root organization, and it cannot be moved or deleted. It matters for one more reason: tenant-level permissions can only be granted on the root. That covers things such as managing members, roles and security settings. The console refuses a group, an invite or a role change that would grant a role with any of them on a child organization.
Try this next
Sketch your tree with three levels at most, then ask of each node: "would I ever grant a role here and nowhere else?" If the answer is no, you do not need that node. Next, invite your team.