AtlasAtlasDocs

Search documentation

Find a page in the Atlas docs

Get started

Project scope and access

Private, Limited and Open projects, who can see and change them, and tightening a project's scope.

Every project has a scope: Private, Limited or Open. Scope decides what Leads and Members who aren't on the project's team can do with it. Admins always have full access to every project, whatever its scope.

What each scope means

PrivateLimitedOpen
Project teamFull accessFull accessFull access
Everyone else (Leads and Members)Can't see it at allCan read everything, and commentFull access

Full access means everything your role allows. For a Member, that's the work inside the project: tickets, sprints, comments, attachments, work logs, meetings and daily updates. For a Lead, it also includes setting up the project: its details, team, boards and workflow stages.

Private

Only the team and Admins can see the project. For everyone else it doesn't exist: it doesn't appear in lists, search, reports, dashboards or notifications, and opening a link to it shows Not found. New projects start as Private.

Limited

People who aren't on the team can read the whole project: tickets, comments, work logs, daily updates, the team, meetings and reports, including exports. They can add comments, and edit or delete their own comments. They can't change anything else, add attachments, log work, be assigned tickets or be invited to meetings.

Open

Everyone in the organization has full access, as if they were on the team. Everyone appears in its team, workload, standup and reports, and can file daily updates on it. Leads get the project and board setup actions too. Keeping a team list is optional on an Open project: it gives no extra access, and it's used as the starting point if the project is ever tightened.

Change a project's scope

Only Admins can change a project's scope.

ChangeWhat happens
To a looser scope, for example Private → OpenMore people get access. Nothing is removed.
Open → Limited or PrivateYou're asked to confirm the team and the project manager first.
Limited → PrivateThe team stays as it is; everyone else loses read access.

Tighten an Open project

  1. 1

    Choose Limited or Private

    Atlas asks you to confirm who stays on the team.

  2. 2

    Confirm the team

    The current team list, if the project kept one, is filled in. Add or remove anyone in the organization, Leads and Members alike.

  3. 3

    Confirm the project manager

    If the current manager stays on the team, nothing changes. If you leave them off, you can pick a replacement there and then; otherwise the project is left without a manager.

People who lose access when a project is tightened:

  • are unassigned from their tickets in the project,
  • are removed from its upcoming meetings,
  • keep their comments, work logs, daily updates and notifications as history.

Last updated October 1, 2026