Features gated by plan
A feature is one capability. Each is either on or off for a project, seeded from your organization's template when the project was created.
Everything not listed here is available on every plan — issues, zones, drawings, companies, basic reports, notifications and the mobile app are core.
The list
| Feature | What it unlocks | Guide |
|---|---|---|
| Custom Workflow | Add, edit and delete workflow statuses and transitions | Customize the issue workflow |
| Custom Report Templates | Create and manage your own report templates | Report templates |
| Scheduled Reports | Schedule recurring report generation and distribution | Scheduled reports |
| Custom Issue Form | Change which issue fields are required, per organization or per project | Project settings |
| Document Versioning | File version history, download and restore | Versioning |
| Document Approval Workflow | Submit documents for review, with approval and rejection | Document approval workflow |
| Document Activity Log | An immutable audit trail of every document action | Documents overview |
| Checklists | Checklist templates, auto-created issues, and zone lock gates | Checklists overview |
| Advanced Analytics | Flow trends, burndown and custom date ranges on the dashboard | Advanced analytics |
Without a feature
The surface is still visible, but the gated action isn't available. You'll see a notice explaining that the capability depends on your plan rather than a silent failure or a missing button.
Turning a feature on is done by a Builddar administrator. Ask your organization admin to request it.
Why a colleague has it and you don't
Two common reasons:
- Different project. Features are per project. A project created before your organization gained a feature doesn't get it retroactively — the template is copied once, at project creation.
- Different role. The feature may be on while your role doesn't include the permission. See Roles & permissions.
Related
- Products — whole surfaces, gated separately
- Limits and quotas