Customization

Every entity type is editable. Open the entity's Fields tab in settings and add a new field. Pick a type — text, number, boolean, enum, date, or reference — and Based adds it to every existing record with a null value.

Reference fields link to other entity types. A task with a customerId field pointing at Customers becomes a two-way link: open the customer and the task shows up in the related records panel.

The top of every entity page shows pinned fields as inline-editable chips (status, priority, assignee, targetDate by default on tasks). You can change what's pinned at two levels:

• Per entity type — open the type's settings and set headerFields. This becomes the default for every record of that type.
• Per page — open any record, click the pin icon next to a property in the Properties popover. The page stores its own override without touching the type.

Each page stores a viewConfig that remembers which views exist, which fields drive grouping / coloring / dates, and which is active. Edits are shared — the team sees the same board you set up.

If you want a personal view without touching the shared one, use filters on top of the shared view; filters are stored per-user.

Workstreams feel too corporate? Call them “Areas.” Initiatives sound like a consulting deck? Call them “Bets.” The workType key stays stable in the data; only the display label changes, so nothing breaks.

Edit the label in the entity type's settings. Existing pages, board columns, and breadcrumbs update instantly.

You don't have to use initiatives, workstreams, and cycles. A two-person team might delete all three and just have tasks. Based won't warn you — the template is just seed data.

If the template starts feeling like a cage, you've got two exits:

• Create a new entity type from scratch for the thing that doesn't fit. Tasks and initiatives can reference it like any other.
• Export the bucket. Every record is JSON in a bucket you own — pull it into a script, a warehouse, or another tool without asking permission.