DocsBuilding forms

Where a form is available

By default a form is on every project — narrow it to specific projects or a branch of your organisation.

Every project by default

A new form template is available on every project in the workspace. For many teams that's exactly right. When it isn't — a form that only belongs to one region, or one client's sites — you can narrow where it appears.

Set the scope

Open the template and set its Availability:

  • All projects — the default.
  • Specific projects — pick the projects it belongs to.
  • An organisation branch — choose a node in your org tree, and the form is available on every project beneath it.

What scoping does

Availability controls where a form can be started: out-of-scope projects simply don't offer it in the new-record picker, and neither the API nor the assistant will create one there. It never hides or freezes records already filed — a record created before you narrowed the scope keeps its place.

The assistant respects it

Ask the assistant to start a form on a project it isn't available on, and it tells you the form exists but isn't available there — rather than filing it in the wrong place. You can widen the scope again any time.

Availability is about which projects a form appears on. Who can use it on those projects is still governed by roles and permissions — the two work together.