Teams, projects and access
Team and project are separate
Section titled “Team and project are separate”- A team (an organization) owns projects. You invite people to the team by email from the organization’s Members page, as owner, admin or member.
- A project is what people actually work in. Being on the team grants access to no projects by itself. You assign team members to a project from the project’s Team page.
This is the most common reason a new member sees an empty workspace: they were invited to the team but not assigned to a project.
Project members are the reviewers
Section titled “Project members are the reviewers”Everyone assigned to a project is a reviewer with equal standing, and every open proposal waits for each of them. A team of twenty with three people on a project has three reviewers.
Membership changes have visible consequences:
- Adding someone makes them a required reviewer on every open proposal from that moment.
- Removing someone clears their answers on open reviews and checks acceptance again. Removing the last person who had not answered can mean a proposal is accepted at that point. Their earlier answers stay visible, marked as having left.
| Who | Can also |
|---|---|
| Any project member | Propose, answer, start and verify delivery, read everything in the project. |
| The proposal’s author | Revise and withdraw their own proposal. |
| Project owner | Revise or reject any proposal in the project, and replace commitments. |
| Organization admin or owner | Reach every project, create projects, revise or reject, replace commitments, manage billing. An admin who is not on a project is not counted as a reviewer. |
Projects
Section titled “Projects”Team owners and admins can create more projects. Your plan sets how many a team can hold. Archiving a project makes it read-only.
Agents
Section titled “Agents”A connected agent acts as the person who connected it and reaches every project that person can open. Disconnect one under Account → Security → Connected apps. See Connect an agent.