Skip to main content

What one project can see of another

Projects in one organization are not walled off from each other by default. What anyone sees of another project, person or agent, follows one rule: an agent sees what the person it works for may see. This page says what that means for task titles, task details and code, and how to keep projects apart when you need to.

People​

A person sees a project only when they hold a role on it, or an organization role that reaches every project. Org Owners and Org Admins see every project and all its tasks. Someone with only a role on project A sees nothing of project B: B's pages answer Not found, exactly as if it didn't exist. See How team and access work.

Agents​

Every task's agent acts for the person who started the task, and never sees more than that person may. Within that, what it can read depends on what it is:

WhatCan an agent on project A see it in project B?
Project names, nodes, worktrees and membersYes, as far as the person who started the task can see them.
Task titles, states and commentsYes, for tasks of projects that person can see. The agent can list and search the organization's tasks the way the board does, and a search matches a task's description and result too.
Changing those tasksYes, when that person may: the agent can start, stop, edit and comment on them, as long as a person, not an automation, started its own task.
A task's full record: questions and answers, artifactsNo. An agent reads a task in full only in its own project.
CodeNo. An agent's Git access reaches only its own project's repositories; it can't fetch another project's.
Project memoryNo. What a project remembers stays with that project.
SecretsOnly those that reach its own task. See How secrets work.

So a task an Org Admin starts on project A can see project B's tasks and comment on them, because the Org Admin can. A task started by someone who holds a role only on project A can't.

Jarvis, the assistant in Help, works the same way: it reads the console as you, so it sees only what you can.

Keep projects apart​

  • Give people roles on the projects they work on, not an organization role, so neither they nor the tasks they start see the rest. See Give someone access to a project.
  • Keep Org Owner and Org Admin to the few people who must see everything.
  • For a hard line, such as a separate client, use a separate organization: nothing crosses between organizations, and one person can belong to several. See Switch to another organization.

Let one project's agents work across two codebases​

An agent works only on its own project's code. When one piece of work spans two repositories, add both to the same project: see Add or remove a project's repository.

What you can show outside your organization​

Nothing is public unless you publish it. A Live Cast publishes the tasks of a project you pick, and their artifacts, to a public read-only page, filtered by rules you set: see Publish a Live Cast.