Build a custom project details schema
A project details schema defines custom structured fields that can be applied to projects across the workspace. This article covers building a schema.
Manage schemas from Admin Console → Project Schema. The table lists every schema with its field count, required-field count, creator, and created/updated dates.
Creating a schema
- Click New Schema.
- Optionally start from a system template — expand Quick start from a template and click a tile to pre-populate the name and fields. Applying a template while you already have unsaved fields prompts you to confirm, since it replaces everything currently in the form.
- Enter a Schema Name (must contain at least one letter or number, and must be unique).
- Add fields (see below), then click Create Schema.
The right-hand panel shows a live preview of the project details form as you build it, split into Required and Optional sections.
Adding and arranging fields
Each schema starts with one blank field. For every field, set:
- Label — the name shown to users. A field Key is derived from the label automatically (lowercased, spaces replaced with underscores) and can't be edited directly.
- Type — Text, Number, Date, Dropdown, or Yes/No. Choosing Dropdown reveals an Options textarea — enter one option per line.
- Required — checkbox to make the field mandatory.
Use the up/down arrow buttons on a field to reorder it, or the trash icon to remove it. Click + Add Field to append another blank field. A schema must have at least one field, and every field must have a label, before it can be saved.
Editing or deleting a schema
- Click the pencil icon on a schema's row to reopen it in the same editor and save changes.
- Click the trash icon to delete a schema. If it's currently applied to projects, the confirmation dialog tells you how many — those projects are detached from the schema but keep their existing field values.
Field validation rules (min/max length, numeric ranges, date ranges, regex patterns) are covered in Configure field validation.