Customize Every Workflow with Fields

Fields let each Channel match the way your team actually produces content. You can configure fields separately for Ideas, Scripts, Calendar Events, Thumbnail Projects, and Video Reviews instead of forcing every kind of work into one template.

Each entity has one field list. Bluprint ships a set of built-in fields in it, and any field your team creates — sponsor, review owner, expected deliverable, target audience, approval status — sits in the same list and can be dragged anywhere in it.

Built-in and added fields sit in one list and work the same way: rename either by clicking its name, drag either to reorder it, hide either with the eye icon. They differ only in two things — a built-in field's type is fixed, and only a field your team added can be deleted outright. Title is the one field that can be neither renamed away nor hidden.

Choose what you are configuring

Open Manage Fields from the active Channel menu. The first screen now asks which entity you want to configure.

Expand

Set the field order

Hiding a field takes it out of this Channel and drops it into the Hidden section at the bottom of the list, where Add back returns it with its values intact. Drag handles change the order used by that entity's field surface.

Expand

Add a field

1. Open Manage Fields
   Open the active Channel menu and choose Manage Fields.
2. Choose an entity
   Select the kind of item that needs the field, such as Calendar Events or Video Reviews.
3. Open Fields
   Choose Fields, then select New field.
4. Define the field
   Give it a clear name, choose its type, and add a short description. Configure choices for select fields.
5. Set a default when useful
   A default prefills empty items. Leave it blank when an empty value carries meaning.
6. Create and arrange it
   Save the field, then drag it into the order teammates should encounter it.

Expand

Pick the right field type

Use a select field when values repeat. Free text such as “approved,” “Approved,” and “ready” is much harder to filter than one shared Approval status menu.

Descriptions and defaults

A description explains the rule behind a field at the place teammates edit it. Good descriptions answer what belongs here, who updates it, or what a value means.

A default is displayed for an item that has no saved value yet. It is not written to every existing item. Changing the default therefore changes what still-empty items display without overwriting deliberate values.

Manage fields over time

From an entity's Fields page you can search, reorder, rename, edit, duplicate, move, or delete fields. Moving a field sends its definition to another Channel; saved values in the old Channel remain hidden so they can return if the field moves back.

Deleting a field you added also retains its saved values for undo and restoration. Bluprint shows how many items currently use the field before you confirm. Built-in fields have no delete — hiding one takes it off the Channel and keeps everything saved on it.

Where values are edited

Once a field exists, open an item and use its field surface:

• Fields in an Idea Window.
• Fields in the Script sidebar.
• The full Calendar Event editor or its configured quick-edit popover.
• Fields beside a Thumbnail Project's Brainstorm canvas.
• Meta & Fields in a Video Review.

Every field uses the same types and asset picker across these surfaces, but each value belongs only to the item you edit.

Common mistakes