2 min read · Updated
Approvals
Approval workflows add a layer of oversight to your projects. When enabled, certain actions — like advancing a project phase or completing a milestone — require sign-off from authorized team members before they take effect.
How Approvals Work
A team member initiates an action that requires approval (e.g., moving a project from Design to Installation).
The system creates an approval request and notifies the designated approvers.
Approvers review the request and either approve or reject it, with optional comments.
If approved, the action proceeds. If rejected, the requester is notified with the reason.
When to Use Approvals
Approval workflows are most valuable in environments where:
- Change control is required — Government facilities, regulated industries, or enterprise clients with strict compliance requirements
- Multiple teams are involved — When coordination between design, installation, and project management is critical
- Quality gates matter — Ensuring each phase is complete before moving to the next
- Budget oversight is needed — Requiring manager approval before advancing to costly phases like installation
Approvals are optional. Smaller teams or fast-moving projects may not need them. You can enable or configure approval requirements based on your organization's needs.
Approval Inbox
When you're an approver, pending requests appear in your notification feed. You can review the request details, see who submitted it, and respond directly — approve, reject, or request more information.
Best Practices
- Define clear approval criteria — Your team should know what's expected before requesting approval
- Respond promptly — Pending approvals can block progress. Set expectations for response times.
- Include context in requests — Attach relevant notes or references so approvers can make informed decisions