getting started

Customize Every Workflow with Fields

Add and arrange fields for Ideas, Scripts, Calendar Events, Thumbnail Projects, and Video Reviews.

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.

There are two kinds:

  • Base fields are built into Bluprint. For most entities, you can hide optional fields and drag them into a useful order.
  • Custom fields are created by your team. They add details such as sponsor, review owner, expected deliverable, target audience, or approval status.

Choose what you are configuring

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

The Manage Fields window with cards for Ideas, Scripts, Calendar Events, Thumbnail Projects, and Video Reviews.
EntityWhere its fields appear
IdeasThe Idea Window Fields tab and Idea Catalog surfaces
ScriptsThe Fields tab in the Script sidebar
Calendar EventsThe full event editor and configured quick-edit popover
Thumbnail ProjectsThe Fields tab beside the Brainstorm canvas
Video ReviewsThe Meta & Fields tab in a review

Configure base fields

Ideas, Scripts, Calendar Events, and Thumbnail Projects have base-field controls. Required fields stay visible; optional fields can be shown or hidden. Drag handles change the order used by that entity's field surface.

The Script base fields manager with required and optional fields in a draggable list.

Create a custom 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 Custom fields
    Choose Custom fields, then select New Custom 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.
A custom field form with its entity, name, description, type, and default value controls.

Pick the right field type

NeedGood field types
Short labels or notesShort Text, Long Text
Controlled workflow statesSingle Select, Multi Select, Checkbox
Dates and schedulesDate & Time, Date Range
OwnershipTeam Member
Supporting materialImage, File, Link
Scores and measurementsNumber, Currency, Duration, Rating, Progress
Connections between workIdea Reference

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 Custom fields page you can search, reorder, 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 custom field also retains its saved values for undo and restoration. Bluprint shows how many items currently use the field before you confirm.

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.

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

Common mistakes

Creating one field and expecting it on every entity

Fields are entity-specific. Create Sponsor approval for the entities where the team must actually record it.

Confusing field order with calendar popover configuration

Calendar Event field order controls the full field surface. The fields shown after clicking an event are configured separately from the calendar toolbar.

Deleting a field just to declutter a surface

Hide optional base fields, or remove a custom field from the surface where that option exists. Delete only when the Channel no longer needs the definition.

Last updated 2026-08-07