Skip to main content

Set up a project

A newly created project is in setup mode. While it's in setup, only organization admins can see it, and issues can't be created yet. This is your chance to configure the project before your team comes in.

Required role: Organization Admin.

What a project needs before it can go live

Builddar checks your project's readiness. To activate a project, it must have:

These two are required. The following are recommended but won't block activation:

Check readiness

  1. Open the project and look at its health or readiness indicator.
  2. Builddar shows a readiness score, what's still missing (required items), and recommendations (optional improvements).

Result: you can see at a glance whether the project is ready to activate and what to add next.

Activate the project

Once the required items are in place, activate the project to open it up to your team.

  1. In the project, open Settings (or the project overview).
  2. Select Activate.

Result: the project becomes active. All its members can now access it and create issues.

caution

If activation is blocked, Builddar tells you what's missing — almost always a zone or a company. Add the missing item and try again.

note

If you ever need to reconfigure a live project in isolation, an organization admin can send it back to setup mode by deactivating it. See Project lifecycle.

Tailor the project

Activation is the floor, not the finish. Once the project is live you can customize how issues are logged, what the workflow looks like, who gets notified, and what your documents print — see Project settings for the full map.

tip

You don't have to configure a project from scratch. Creating one from an existing project copies its workflow, issue form, phases, escalation rules, document structure, and checklist templates. See Copy settings from an existing project.