125 lines
2.7 KiB
Markdown
125 lines
2.7 KiB
Markdown
# Product Glossary
|
|
|
|
Use these terms consistently in product docs, specs, UI copy, and code discussions.
|
|
|
|
## Workspace
|
|
|
|
Top-level working container for a client account.
|
|
|
|
An agency may manage multiple workspaces.
|
|
|
|
Use:
|
|
|
|
- ownership boundary
|
|
- membership boundary
|
|
- scoping boundary for content items, assets, comments, approvals, and notifications
|
|
|
|
Do not use as:
|
|
|
|
- synonym for internal role
|
|
- synonym for team member role
|
|
|
|
## Agency
|
|
|
|
Operating organization managing one or more workspaces.
|
|
|
|
An agency is above the workspace level in the business model.
|
|
|
|
## Client
|
|
|
|
Business, brand, or organization represented by a workspace and participating in review and approval flows.
|
|
|
|
## Campaign
|
|
|
|
Client-owned body of content work that groups related content items, notes, and timelines.
|
|
|
|
## Content Item
|
|
|
|
Primary reviewable unit in the system. Contains metadata, copy, due dates, networks, channels, and linked assets.
|
|
|
|
Examples:
|
|
|
|
- one Instagram reel package
|
|
- one newsletter draft
|
|
- one campaign asset for approval
|
|
|
|
## Asset
|
|
|
|
A file or file reference attached to a content item, such as a video, image, or document.
|
|
|
|
## Asset Revision
|
|
|
|
Specific version of an asset with traceability to who linked or uploaded it and when.
|
|
|
|
## Approval Workflow
|
|
|
|
End-to-end process from draft creation to final approval and publishing handoff.
|
|
|
|
## Approval Request
|
|
|
|
Explicit request for one or more reviewers to review a specific content item or revision state.
|
|
|
|
## Approval Decision
|
|
|
|
Decision recorded by a reviewer, such as:
|
|
|
|
- approved
|
|
- rejected
|
|
- changes requested
|
|
|
|
## Reviewer
|
|
|
|
Any person asked to review and approve work, whether internal or external.
|
|
|
|
## External Reviewer
|
|
|
|
Client or partner reviewing content without being part of the internal operating team.
|
|
|
|
## Provider
|
|
|
|
External production contributor such as a photographer, videographer, editor, or designer.
|
|
|
|
## Comment Thread
|
|
|
|
Contextual discussion attached to a content item, asset, or revision.
|
|
|
|
## Status History
|
|
|
|
Audit trail of workflow states and transitions over time.
|
|
|
|
## Network
|
|
|
|
Publishing platform or distribution surface, such as Instagram, Facebook, YouTube, LinkedIn, or a newsletter system.
|
|
|
|
Examples:
|
|
|
|
- TikTok
|
|
- Instagram
|
|
- Facebook
|
|
- YouTube
|
|
- LinkedIn
|
|
- Newsletter
|
|
- X
|
|
- YouTube
|
|
|
|
## Channel
|
|
|
|
Specific destination, account, handle, page, or feed within a network.
|
|
|
|
Examples:
|
|
|
|
- `@MyBrand` on Instagram
|
|
- `My Brand Page` on Facebook
|
|
- `#Brand` if used as an internal destination label
|
|
- a specific YouTube channel
|
|
|
|
## Ready To Publish
|
|
|
|
State meaning the required review/approval workflow is complete and the item can move to downstream publishing or handoff.
|
|
|
|
It does not mean the item has already been published.
|
|
|
|
## Audit Trail
|
|
|
|
Chronological record of uploads, comments, approvals, and status changes.
|