How to Create Projects

Last updated: September 1, 2026

Background

Projects give your team a shared workspace in Document Crunch to organize everything tied to a single job or contract — crunches, documents, chats, reviews, and playbooks — in one place. Creating a project keeps related work grouped together and controls who can view, edit, and manage that content through Document Crunch's role-based permissions. Team Admins and Team Editors create projects for their team; each new project automatically inherits the team's members and their roles, and access can be fine-tuned on a per-project basis when specific people need more access than their team role provides.

Things to Consider

  • Who can create projects: Team Admins and Team Editors can create projects. Team Viewers can see projects but cannot create them.

  • Projects belong to a team. A project is always created inside a team, and it inherits that team's members and their roles as its starting point.

  • Access is role-based at three levels — Organization, Team, and Project. The Organization level has a single Admin role; the Team and Project levels each have Admin, Editor, and Viewer roles.

  • A team role is the baseline on every project in that team. A Team Editor starts as an Editor on all of the team's projects, and a Team Viewer starts as a Viewer, unless they are elevated on a specific project (see Managing project-level access below).

  • Project roles can elevate a user, never reduce them. A project assignment can raise someone above their team baseline on one project, but can never lower them below their team role. Team Admins are locked to Admin on every project in the team.

  • Managing users is Admin-only. Adding, removing, or changing a user's role requires a Team Admin (or Organization Admin); Editors and Viewers cannot manage users.

Steps

Create a project

  1. From your Dashboard, click the +New button.

  2. Select Project.

  3. Enter a project name.

  4. Choose the team this project belongs to (if you have access to more than one).

  5. Set any optional project attributes — region, department, architect, project type, and owner — to keep your projects organized and searchable.

  6. Click Create.

Note: New projects start with your team's existing members at their current team roles. You don't need to add teammates individually unless you want to give someone more access than their team role provides.

Managing project-level access

Every project inherits its team's members and roles as a baseline. Use project-level roles when one person needs more access on a specific project than their team role gives them — for example, giving a Team Viewer Editor or Admin access on a single project without changing their access anywhere else.

  1. Open the project and go to its user/access settings (Manage Users).

  2. Find the teammate you want to adjust.

  3. Set their project role to Editor or Admin as needed.

Tip! Overrides are per-project and independent, so the same person can be an Editor on one project and an Admin on another at the same time, while staying a Viewer everywhere else.

Note: Project roles can only raise a user above their team baseline — they can't lower anyone below their team role. Team Admins remain Admin on every project and cannot be reduced. Managing project users requires a Project Admin, Team Admin, or Organization Admin.

Tip! For a full breakdown of what each role can do at the Organization, Team, and Project levels, see the Permission Matrix and Understanding Roles & Permissions.