Visibility controls
Share progress, not your internal process
Every task is internal or shared. Every imported field is opt-in. What crosses the boundary is a deliberate decision — never an accident of permissions.
A boundary you can see
The host team decides what the other side sees, task by task and field by field.
Internal by default
Unrecognized imported fields are excluded until you choose to share them.
Owner sides
Every task belongs to the host side, the partner side, or both — ownership without hierarchy.
Preview as partner
See exactly what the other team sees before you publish.
Sanitized at publish time
Shared boards are generated as a clean projection. Nothing private is hidden — it simply is not there.
- 01Projection, not permissionsInternal notes never enter the shared snapshot, so a stale filter can never leak them.
- 02Field-level rulesChoose which imported fields cross: title, status, owner, due date, description, source link.
- 03Private links stay genericPrivate and unlisted links use generic link-preview text, and secret token URLs never appear in sitemaps or canonical tags.
- 04Private source fieldsEstimates, subtasks and internal assignees stay out unless you opt in.
- 05Activity trailSee what changed on shared tasks, by whom and when.
No internal note should be filtered at render time. It should never enter the shared view in the first place.
MORE OF THE SHARED LANE