Posts, tasks and cases each support the Sharing permissions control so you can limit who sees and edits them. Cases add an extra benefit: posts created in a case inherit the case's permissions automatically. Tasks created in a case do not — restrict them yourself.
Restrict a post
- Create your post and click the globe icon under your name (it shows the current visibility, such as Everyone).
- In the Edit permissions panel, start from a preset if it helps (Everyone, Current Circle or Only me).
- Under Add access for, choose User, User group or Circle, find the entry, set the access level (Full Access, View and Edit or View only), then click Add. Use Add me to add yourself quickly.
- Repeat to add any other users, groups or circles.
- Confirm at least one entry is listed, then remove Anyone if you want the post to be private.
- Click Apply, then post. Only the listed entries will see it.
Restrict a task at creation
- Open Create a task.
- Under Permissions, click Sharing permissions.
- In the Edit permissions panel, add the users or groups, setting each to Full Access, View and Edit or View only. (Task presets are Everyone and Only me.)
- Confirm at least one entry is present, then remove Anyone if required, and click Apply.
- Click Create to save the task.
Restrict a case (with inheritance)
- When creating the case, click Sharing permissions at the top of the New Case drawer.
- Add the users, groups or circles, setting each access level.
- Confirm at least one entry is listed, then remove Anyone if you want the case to be private, and click Apply.
- Click Create to save the case.
How case inheritance works
Any posts created in a case automatically take the same permissions as the case — the visibility shown in the post form starts from the case's settings. This means:
- You set post permissions once, at the case level.
- Every post in the case is protected the same way, without configuring each post individually.
Tasks do not inherit. A task created in a case starts visible to everyone, even when the case is restricted. On a sensitive case, restrict each task when you create it (see Restrict a task at creation above), or see Tasks inside a case (Document ID: 173).
Tips
- Add a group or circle rather than individual users where possible, so case access stays correct as team membership changes.
- Always confirm at least one entry is present before removing Anyone — otherwise no one will be able to see the item.