Projects
Project access and settings
Who can see a project, public-to-organization projects, project roles, the View and Manage Projects permissions, and the per-project settings.
On this page
Project access works at two levels: whether someone can use the Projects area at all, and whether they can see a particular project.
Module permissions#
| Permission | Allows | Default |
|---|---|---|
| View Projects | Open Projects and see company projects available to you | Owner, Admin, Manager |
| Manage Projects | Create, edit, archive and reassign company projects | Owner, Admin |
Presets that include Manage Projects: Designer, Manager, Developer, Operations.
Who can see a project#
A project is visible to:
- its members, and
- everyone in the organization with View Projects, if the project is public to organization.
Set this in the project's Settings → Access & visibility → Public to organization. New projects follow the workspace default (Projects → Settings → Default to public).
Search follows the same rule: a project appears in someone's search results only if they could open it.
Project settings#
Each project's Settings tab:
- Members — add people, set their project role (owner, admin, member), remove them.
- Communication — post updates and file shares to the project conversation.
- Access & visibility — public to organization; notify on changes.
- Lifecycle — auto-archive after a number of days of inactivity (0 disables).
Workspace project settings#
Projects → Settings sets defaults for every project:
- Default to public for new projects.
- AI weekly summaries — progress summaries generated for projects.
- Standard tags offered on every project.
- Cost codes for job costing.
- Auto-archive defaults.