Projects

What it's for

Projects sets one rule: whether new jobs can be created, and existing jobs scheduled or moved, on a project that is not active. A project is not active when it is held, completed or canceled.

Reach it from Settings → How jobs run → Projects in the sidebar, at /settings/projects. The Settings breadcrumb at the top takes you back.

Tabs

This screen has no tabs. It holds one choice and a save button.

Panels and controls

Work on projects that are not active has two options:

• Refuse work on inactive projects. A new company starts here. A company that already existed when this choice was added starts on Allow until an owner changes it. While Refuse is selected, new jobs and scheduling on a held, completed, or canceled project are blocked. The message names the project and the status: Project "Name" is on hold. Reopen the project before adding or scheduling work on it. The status words are on hold, completed, or canceled. A job that is not on a project phase is not blocked.
• Allow work on any project. Jobs can be created and scheduled whatever the project's status.

Save project policy stays disabled until you change the choice. A short Saved. note appears once the change is stored.

What it accepts

How to configure it

• Choose Refuse to stop crews being booked against a project that has been put on hold or closed out.
• Switch to Allow if you routinely schedule warranty or punch-list work after a project completes.
• The rule applies to new jobs and to jobs being placed on the schedule again. Existing history is not changed.

Who can see it

• Owners can open the screen and change the rule.
• Office managers can open the screen and read the current rule, but the choice is locked and only an owner can save a change.
• Dispatchers and technicians cannot reach Settings at all. The change is checked on the server, so the gate holds regardless of what the sidebar shows.

The full role matrix is on Roles & permissions.