BDS0.1

Department (mirror)

Local Department usage in KPIs & OKRs; shared definition in Core.

Reviewed 2026-10-28Markdown

The shared definition and source fields are in Core / Department. This page explains only usage in KPIs & OKRs.

Use and boundaries

Parent Organization and Head Membership identify its context and owner. Channel Identifier is text used by the Task intake check when a department executor is selected. The current Daily Digest still sends direct messages to resolved people; the existence of a department channel does not imply departmental routing is implemented.

Locally used fields

Parent Organization, Head Membership, Channel Identifier.

These are consumer labels and may differ from the source. Local operational links and derived values:

Field Storage Local usage
Membership: Head Names Lookup Head Membership → unresolved source field
Task Linked records Task
Metric Target Linked records Metric Target
Tags Linked records op:tags · local label; does not update Core
Procedure Linked records Procedure · inverse of Owner (Department)°

The Membership: Head Names lookup does not point to a resolvable source field. Verify that lookup before relying on it.

Where to correct

Correct shared data in Core Record Types[Department]. Adjust links to tasks, targets and other operational records here. Check the column mapping, refresh interval and write-back behavior in the sync settings before relying on them. Do not assume editing a mirror updates Core. See Maintain shared records.

Next steps

People and workspaces · All entities.