Core concepts
Learn the terms used for content, publishing, access, and delivery.
These terms describe the objects and states you see throughout Jetrepo.
| Term | Meaning |
|---|---|
| Organization | Owns members, reusable roles, service principals, and Backends. |
| Backend | The boundary for a content model, content, publishing, delivery, Releases, and schedules. |
| Data Type | A Content type or Asset type with one ordered Field Set. |
| Entry | An authored Content record with Draft, Published, Changed, or Archived status. |
| Asset | A Media record with fields and a file. |
| Component | An embedded field structure without its own lifecycle or publishing status. |
| Delivery locale | A public Backend language key with a configured fallback chain. |
| Vocabulary | A Backend-scoped set of Taxonomy Terms. |
| Taxonomy Term | A stable, localized classification concept inside a Vocabulary. |
| Release | An atomic set of whole-item Publish and Unpublish actions. |
| Release-staged version | A Release item copy edited separately from the live Draft. |
| Review state | The current review stage, assignments, and approvals; it is separate from content status. |
| Preview target | A trusted frontend destination configured for preview. |
Access terms
An Organization role combines fixed permissions with explicit resource scopes. A member’s effective access is the union of grants from all assigned roles, but one role must contain both the permission and a matching scope. Roles are additive; there are no deny rules, ranks, or direct user exceptions.
Taxonomy classifies content; it does not create navigation, folders, URLs, or page trees. Release preview also differs from Draft preview because it uses Release-staged versions first.