Skip to main content
Two capabilities govern planning, and a third governs looking.

​
Role defaults

block.manage mirrors time.track – every role that records time can plan its own calendar. block.manageOthers mirrors time.editOthers – the delivery approver tier. Finance is a money role, not a delivery one, so it plans nothing.
See /concepts/roles-and-capabilities.

​
Seeing versus scheduling

The Planner separates the two deliberately. Viewing is plural. With time.viewOthers you can overlay any number of teammates on one grid and read the whole team’s week. Scheduling is singular. A new block has to land on somebody’s calendar, and a day-off shade belongs to somebody’s week. So creating and dragging only work while the member picker names exactly one person. Dragging is decided per block, by whose calendar it sits on. Inside an overlay your own blocks stay movable while a teammate’s need block.manageOthers.

​
Capability is not scope

Holding time.viewOthers says you may see other people’s calendars. Supervision scope says whose. The member picker only offers people inside your scope. A Project Manager scoped to one group sees that group, not the whole workspace – even though the capability is identical to an Admin’s. The participant picker on a block works the same way. See /concepts/supervision-scope.
Hiding a control is a convenience, never the boundary. Every block write is re-checked on the server against the capability, the scope, the app switch and the plan. A stale browser tab cannot plan onto a calendar it should not reach.

​
What each action requires

Only the participants that actually changed are permission-checked. Re-saving a block with the same roster does not demand permission over every teammate already on it.

​
Plan and app gating

Turning the Planner off hides it and stops blocks syncing to calendars. Every planned block is kept. “App off” and “not on your plan” are different states. Off means hidden completely. Not on your plan means visible with a paywall. See /concepts/apps-and-modules and /concepts/plans-and-features.

​
Example

Northwind Studio: If Maya wants a senior designer to plan for the design group, she creates a custom role from Member, adds block.manageOthers and time.viewOthers, and sets their supervision scope to that group. See /team/custom-roles.

​
Common questions

Member does not hold time.viewOthers. The member picker is not shown, so they always plan their own week.
Yes. block.manageOthers and time.editOthers are separate capabilities. Grant one without the other through a custom role.
You hold time.viewOthers but not block.manageOthers. The banner says “(read-only)”.
You are overlaying more than one calendar. Pick exactly one person.
Yes, if the manager holds block.manageOthers and the contractor is inside their supervision scope.
Correct. Finance owns the money surface, not delivery. Grant block.manage through a custom role if you need it.

​
Troubleshooting

Roles and capabilities

The whole permission model.

Supervision scope

Whose calendars you can reach.

Custom roles

Move a block capability to another role.

Plans and features

Why the Planner is Pro.

Planner overview

Back to the grid.

Multi-person blocks

Permissions on a shared block.