Configure Project-Specific Settings
Configure settings specific to a project including custom fields, team roles, integrations, and defaults. These settings apply only to this project and can override organization defaults.
This guide is designed for project-manager.
Steps
Step 1: Navigate to Project Settings
From the project, click Settings in the sidebar, then select Project Settings from the menu. This shows all settings specific to this project. Only Project Admins can modify project settings.
Project settings override organization defaults for this project only.
Step 2: View project information
The Project Settings page displays: project name, dates (start, end, deadline), budget, assigned license, project status (active/archived), and project template used (if any). Some information can be edited, some is locked.
Project name and dates can usually be edited. License and template are usually locked.
Step 3: Customize enabled custom fields
View all available custom fields (from organization). Select which ones to enable for this project. Disabled fields don't appear in project forms. You can enable/disable fields anytime - disabled fields' data remains.
Disable fields not relevant to this project to reduce UI clutter.
Step 4: Configure project roles
View all available custom roles. Select which roles are used in this project. Other roles can still be assigned but won't be suggested. You can also set default roles for when people are added.
Pre-select roles to speed up team member setup.
Step 5: Set project defaults
Configure defaults specific to this project: Default priority, default status, default task duration, default work package folder structure, naming conventions, and other project-specific defaults. These appear when creating new items.
Project-level defaults override organization defaults.
Step 6: Configure team access levels
Define access level defaults for different roles in this project: What can Viewers see, what can Editors change, what can Managers approve, what can Admins do. These permissions apply to all people with those roles.
Access levels can be customized per-person if needed.
Step 7: Enable project integrations
View integrations configured at organization level. Enable/disable specific integrations for this project. Some projects may not need all integrations. Click to configure project-specific sync settings.
Organization integration must exist before it can be enabled in a project.
Step 8: Configure project notifications
Set notification defaults for this project: Email notifications for task assignments, document uploads, milestone completion, etc. Team members can override these on their accounts.
Project defaults can be overridden by individual user preferences.
Step 9: Set project collaboration settings
Configure: Document sharing (who can view/download), Task assignment (who can assign), Approval workflows (required approvals), Comment/discussion settings (who can comment), and export/download permissions.
Stricter permissions ensure data security; looser permissions improve collaboration.
Step 10: Manage project team
From Project Settings, click Team to manage project-specific team members. Add/remove people, change roles, adjust access levels. This is different from organization-level Team Management.
Project team members are people assigned to this specific project.
Step 11: View project statistics
At the bottom of Project Settings, view project statistics: Number of tasks, number of team members, number of documents, project completion percentage, and active status. This helps monitor project size and complexity.
Use statistics to understand project scope and resource allocation.
Step 12: Archive project
When a project is complete, click Archive Project. The project remains accessible for review and reporting but team members lose write access (unless specifically allowed). Archived projects don't count against active licenses.
Archiving is reversible - you can restore a project anytime.
Video Tutorial
Last updated: 2025-12-08