Project settings
Edit a project's details, set approval governance, manage members and invitations, review the governance log, and archive or delete the project.
Project settings is where you administer one project — its identity, its approval policy, its team and its lifecycle. Changes here affect only this project.
Where: sidebar Project settings (bottom of the project sidebar) ·
/p/<project>/settings
Who can change what
Everyone on the project can open settings, but controls follow your role:
- Owners and organization owners and admins can do everything: edit details, change approval governance, manage members and invitations, read the governance log, and archive or delete the project.
- Editors, Approvers and Viewers see the details and the member list read-only. Fields they cannot change are disabled, and the tabs and actions they cannot use are hidden.
General
Project details
- Name — shown in the project switcher, breadcrumbs, reports and on Home.
- Key — a short code of up to 8 capital letters or digits shown beside the name, such as
AGV. - Description — mission, scope and stakeholders. The co-engineer reads it for context, so a good description improves its answers.
Edit and click Save.
Approval governance
Require explicit approvers separates approving from editing. When it is on, editors can still write content, but only members with the Approver role (and owners) can approve requirements, change-request stages, baselines and documents. Turn it on before a formal review so sign-off comes only from designated approvers. See Managing permissions.
Lifecycle
Visible to owners and organization admins.
- Archive project — makes the project read-only for everyone, including owners and the co-engineer. Members keep read access, and it shows as Archived on Home. Restore project reverses it at any time.
- Delete project — removes the project with its requirements, tests, documents, risks and history. Confirm by typing the project name. Treat it as permanent; archive instead if you might need the project again.
Members
Lists everyone with access and their project role: Owner, Editor, Approver or Viewer. Organization owners and admins can always reach the project without being listed.
- Add from organization — choose someone already in the organization and a role. They get access immediately, with no email round-trip.
- Invite by email — send a project invitation with a role. See Invite members.
- Change a role — owners change any member's role from the role menu.
- Remove or leave — owners remove members from the row's action menu; anyone can leave a project from their own row.
A project always keeps at least one owner. Promote someone else before you change your own role or leave.
Invitations
Pending and past project invitations with their status — pending, accepted, revoked or expired. Revoke a pending invitation sent in error; its link stops working at once. Invitation links expire after 7 days.
Audit log
Visible to owners and organization admins. The project's governance log: a timeline of membership, role, approval-governance and lifecycle changes: who added, removed or re-roled whom (with the old and new role), invitations sent, revoked and accepted, settings updated, and the project archived, restored or deleted.
Tips
- Prefer Add from organization when the person is already in your organization — it is instant.
- Revoke stale invitations rather than leaving them pending.
- Write the description for the co-engineer. Mission, operating environment and key constraints there pay off in every AI answer.
- Archive at end of programme. It freezes the record for audit while keeping it readable.