Assignment Role
An actor, role and membership held together for one subject.
Subject (Task), Subject (Procedure) and Subject (Recurrence Configuration) are real links. Actor and Membership fields are text, so they do not enforce referential integrity. Start Date and End Date describe validity. Ownership Of is the inverse of Procedure ownership assignments. Do not treat a role record as an Airtable permission grant.
Use and boundaries
Field names below are the current product labels. * and ° are UI markers, not database constraints. A preferred single-record selection is not a global cardinality constraint either. The related guide explains operational rules.
Fields
| Field | Storage | Source, options or boundary |
|---|---|---|
| Assignment # | Auto number | Generated by Airtable. |
| Subject (Task) | Linked records | Task |
| Subject (Procedure) | Linked records | Procedure |
| Subject (Recurrence Configuration) | Linked records | Recurrence Configuration |
| Role Name | Text | Stored value. |
| Actor (Person) | Text | Text reference; not a linked record. |
| Actor (Position) | Text | Text reference; not a linked record. |
| Actor (Team) | Text | Text reference; not a linked record. |
| Actor (Department) | Text | Text reference; not a linked record. |
| Membership | Text | Text reference; not a linked record. |
| Start Date | Date | Stored value. |
| End Date | Date | Stored value. |
| Evidence | Text | Text reference; not a linked record. |
| Ownership Of | Linked records | Procedure |
| Tags | Linked records | op:tags · optional labels from the Core Tags catalog; classification only. |
Example and maintenance
Illustrative example: a reviewer role on one Procedure has a start date and documented actor context.
Use the existing fictitious records to inspect relationships in the guide. Before changing fields, check lookups, formulas, intakes and workflow contracts. This page documents structure; a field does not prove that an integration populates it.