Project settings

What you configure on a project — details, team, workflow, tags, attachments, and its compliance profile.

Opening a project gives you everything that governs it, organized into tabs. These settings shape how the project behaves and who can work in it.

Details

The Details tab holds the project’s identity — name, code, description, visibility — and its current status. This is where you adjust the essentials set at creation.

Team

The Team tab manages who belongs to the project and the role each member holds. Roles determine what a person can see and do inside the project, so the team list and project permissions work together. Adding and removing members here is the day-to-day way to control access.

Workflow

The Workflow tab governs how items in the project move through their lifecycle states. Where your organization allows it, a project can carry workflow overrides so a specific project’s process matches its needs while still inheriting organizational defaults.

Tags and attachments

The Tags tab manages the tags available for classifying items in the project, and the Attachments tab holds files associated with the project itself. Both keep project-level context in one place rather than scattered across records.

Compliance

The Compliance tab ties the project to the compliance profile and frameworks it’s developed under, which drive the controls — controlled states, signatures, and checks — applied to its records. The frameworks themselves are defined organization-wide; see the Compliance section for what each enforces.

Some controls live alongside the project rather than on it — most importantly which modules the project uses, covered next in Module access.

Was this helpful?