Modular Content Architecture
BFF uses a composable content model — controlled documents are independent of tasks, and you snap them onto tasks via Linked Content. This means:
- One document can serve many tasks across your company
- Each document has its own version history, lifecycle, and role assignments
- Tasks link whichever documents they need — not all tiers are required
Linking Content to a Task
- Open the task and click Edit
- Find the Linked Content section
- Click “Link Content”
- Pick a document tier, then select the document from the dropdown
- Click “Link”, then “Save Changes”
You can star one linked document as the Primary document for the task — it’s badged Primary on the task detail page.
Linkable Document Tiers
All four controlled-document tiers can be linked to a task:
| Tier | Purpose | Use When |
|---|---|---|
| Policy | The “what and why” — governing rules and standards | The task is bound by a company-level rule |
| SOP | The “how we operate” — procedures | You need to document the procedure around the task |
| Work Instruction | The “exactly how” — step-by-step execution | You need detailed execution steps (supports both human and AI format) |
| Training | The “learn” — onboarding material | New team members need to learn before executing the task |
Removing Content Links
- Open the task and click Edit
- In Linked Content, click the remove button on the link row
- The document itself is not deleted — just the link
Why This Matters: Document-Publish-Driven Change Control
Change control in BFF runs off document publishes, not task edits. When a published document that’s linked to your task is republished:
- Every human task assignee gets a Document Changed notification
- AI agent assignees get a webhook, routed to the agent’s responsible human
- Separately, document↔document links carry the change to each connected document’s owner via Impact Cascade Alerts — see Linking Documents in the Document Control section
Example: If you republish the “Email Handling SOP,” every person and AI agent assigned to a task that links it is notified — without you tracking down who uses it.
Tip: Task↔document links are different from document↔document links. Task links route changes to the people doing the work; document links route changes to the people owning related documents. A well-governed task usually benefits from both.