Restricting Posts, Tasks and Cases (with case inheritance)

Posts, tasks and cases each support the Sharing permissions control so you can limit who sees and edits them. Cases add an extra benefit: their posts and tasks inherit the case's permissions automatically.

Restrict a post

1. Create your post and click the globe icon under your name (it shows the current visibility, such as Everyone).
2. In the Edit permissions panel, start from a preset if it helps (Everyone, Current Circle or Only me).
3. 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.
4. Repeat to add any other users, groups or circles.
5. Confirm at least one entry is listed, then remove Anyone if you want the post to be private.
6. Click Apply, then post. Only the listed entries will see it.

Restrict a task at creation

1. Open Create a task.
2. Under Permissions, click Sharing permissions.
3. 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.)
4. Confirm at least one entry is present, then remove Anyone if required, and click Apply.
5. Click Create to save the task.

Restrict a case (with inheritance)

1. When creating the case, use the Sharing permissions control at the top-right of the New Case drawer.
2. Add the users, groups or circles, setting each access level.
3. Confirm at least one entry is listed, then remove Anyone if you want the case to be private, and click Apply.
4. Save the case.

How case inheritance works

Any posts and tasks created under a case automatically inherit the same permissions as the case. This means:

• You only need to set permissions once, at the case level.
• Every related post and task is protected the same way, without configuring each item individually.
• This is ideal for sensitive matters where all activity should be visible only to a defined group.

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.