Plans & limits
Four separate things govern what your organization can do in Builddar. When something is unavailable, it's one of these — and knowing which saves a support round-trip.
| Layer | What it controls | Where it's set |
|---|---|---|
| Plan | The baseline: which features are on and what the default limits are | Assigned to your organization |
| Feature | One capability, such as scheduled reports | Per project, seeded from the organization |
| Product | A whole surface, such as site meetings | Per project, inherited from the organization |
| Limit | A ceiling on members, projects, drawings or zones | Plan default, or an override on your organization |
Billing modes
An organization is billed one of two ways, and it changes which limits apply.
Per user (seat-based)
You buy seats. The organization has a member limit and a project limit.
- Guests don't consume a seat — only non-guest members do.
- Plan periods available: 1 month, 3 months, 1 year.
Per project (drawing-based)
You buy drawing credits per project. There's no project limit; each project carries its own drawing quota, and credits are added to it as needed.
- Every add and removal of credits is recorded with who did it and why.
- Plan periods available: 1 month, 3 months, 1 year, 3 years, 5 years.
- Some per-project organizations can self-manage — their admins create projects and add drawing credits themselves. Where that's off, a Builddar administrator does it.
Plan periods and expiry
A plan assignment has a start date, an end date and a status — Active, Expired or Cancelled. The end date is calculated from the start date plus the period.
When a plan expires or is cancelled, access to the whole organization is blocked, not just the gated features. Plan history is kept — each new assignment is a new record rather than an edit of the old one.
How a project gets its features
Feature access lives on the project, not the organization. At project creation Builddar copies the organization's feature template onto the new project. After that the project is independent — changing the organization template doesn't retroactively change existing projects.
Products work the same way, with one restriction: a product can be switched off on a project, but never switched on if the organization doesn't have it.
In this section
Related
- Set up your organization
- Roles & permissions — a different question: not is this feature available, but am I allowed to use it