Every tool has an admin page. You still manage access in four places.

Asana has teams. Notion has guests. ClickUp has everything. Add a contractor and you make the same decision four times — and none of them is the decision you actually care about: which client they may see.

Access sounds like an admin chore until the first contractor. You want them on the board and the timer, not the wiki. You want them in one client, not all of them. So you open Asana, then Notion, then the timer, and you make four slightly different decisions, and one of them is wrong by Friday.

Nobody sets out to become an access administrator. You add a tool, it ships a settings page, and by the fourth tool you have a job you did not apply for. The cost is not the clicking. The cost is the Friday you cannot answer who can see the client.

Four decisions, one truth

The point is not to hide admin pages. It is to make the decision once. A person joins the organisation, gets a role, gets the products they need, and maybe gets restricted to one workspace. The apps still check membership when the person arrives. The portal is where you said the intent.

What we actually enforce

• Roles on the organisation: owner, admin, editor, member.
• Product access per person — Tides, TurtleTime, Kraken and Shelly are ticked separately. A bookkeeper can be timer-only.
• Workspace restrictions, so a contractor sees one client and not every client.
• Seats and workspaces counted on the organisation, on one bill, with the plan actually enforced.
• Removing a member drops organisation access; the product sessions stop working once the membership is gone.

Where the work tools stop

Asana, Notion and ClickUp each govern their own world. That is fine until you want a person to have a board and a timer but not the wiki, and to see one client but not the rest. None of them is the right place to answer that, because none of them holds the client directory.

If you cannot answer “who can see this client?” in one place, you do not have access control. You have four admin pages.

If you only run one tool, its admin page is the correct answer. This is for the studio where the person, the client and the seat span more than one product.

Use the portal when access is an organisation fact, not four admin pages that drift apart. Decide once, and the apps enforce it.