Skip to main content
Every task in a Chief Project has a visibility setting that decides who can open it. This lets you limit a draft to yourself and applicable Owners, share working notes with your whole Project team, or open a sensitive conversation to a handful of named people — without moving the task anywhere.

​
The three visibility levels

Open any task and look for the visibility badge near the task title. It shows the current level: Private, Project, or Restricted. Here is what each one means:
  • Only you (Private) — You and Owners whose role applies to the Project can see the task. Other Project members cannot open it unless you share it with them or raise its visibility.
  • Everyone in the project (Project) — Anyone with access to this Project can see the task. This is the default for most tasks.
  • Specific people (Restricted) — Only you and the people you choose can see the task. You pick named Project members one by one.
Example: You start a task to draft a board update using your team’s shared files. While it is rough, you keep it Private, limiting access to you and applicable Owners. Once it is ready for feedback, you switch it to Restricted and add your two co-authors. After the update ships, you set it to Project so the whole team can reference it.

​
How to change a task’s visibility

  1. Open the task you want to change.
  2. Select the visibility badge next to the task title (it reads “Change visibility, currently…”). The Task visibility dialog opens.
  3. In the dialog, select one of the three options: Only you, Everyone in the project, or Specific people.
  4. If you choose Specific people, a Share with specific people list of Project members appears below. Select each person who should have access; a checkmark marks the people you have chosen.
  5. Select Save. The dialog confirms with “Saving…” and then closes. The visibility badge updates to the new level.
⚠️ Important: Tasks in Projects that have the Google integration connected start as Private on purpose. This keeps mailbox and calendar content from being shared with the whole Project until you deliberately raise the visibility.
Visibility controls who inside your Project or Organization can open the task. It does not create a public link. To let someone outside the Project view a read-only copy, create a secret link instead.

​
FAQ

If the member list could not load, Chief disables Save so you do not accidentally wipe the task’s existing audience by saving an empty selection. Close and reopen the dialog, or select Retry if an error appears, then choose your people and save again.
Yes. A Project Owner can open Private tasks in that Project. An Organization Owner whose role reaches the Project can also open them. Collaborators and Readers cannot open a Private task unless you share it with them or raise its visibility.
They lose access immediately. If they had the task open, they will see a message that the task is no longer available to them; their access to the rest of the Project is unchanged.