166 lines
4.5 KiB
Markdown
166 lines
4.5 KiB
Markdown
# Product Glossary
|
|
|
|
Use these terms consistently in product docs, specs, UI copy, and code discussions.
|
|
|
|
## Organization
|
|
|
|
SaaS account boundary that owns billing, subscription, limits, organization-level users, connectors, data mappings, and workspaces.
|
|
|
|
An organization may be an agency, an in-house brand company, or a professional's business account.
|
|
|
|
Use:
|
|
|
|
- billing and subscription boundary
|
|
- ownership boundary for workspaces
|
|
- connector and integration configuration boundary
|
|
- organization-level membership and permission boundary
|
|
|
|
Do not use as:
|
|
|
|
- synonym for a brand workspace
|
|
- synonym for a single human user account
|
|
- synonym for an external reviewer
|
|
|
|
## Workspace
|
|
|
|
Brand, client, or operating workspace where content workflow happens.
|
|
|
|
Each workspace belongs to exactly one organization and is not shared between organizations.
|
|
|
|
Use:
|
|
|
|
- brand/client workflow boundary
|
|
- scoping boundary for content items, assets, comments, approvals, and notifications
|
|
- channel configuration boundary
|
|
|
|
Do not use as:
|
|
|
|
- top-level SaaS account boundary
|
|
- billing or subscription boundary
|
|
- synonym for internal role
|
|
- synonym for team member role
|
|
|
|
## Organization Member
|
|
|
|
User access relationship at the organization level.
|
|
|
|
Organization membership can grant organization-level permissions and inherited access to all workspaces owned by that organization.
|
|
|
|
## Workspace Member
|
|
|
|
User access relationship at the workspace level.
|
|
|
|
Workspace membership grants direct access to one workspace and can classify the user's relationship to the owning organization as `Organization Member` or `External Collaborator`.
|
|
|
|
An `Organization Member` is part of the organization that owns the workspace. They may have access through organization membership, direct workspace membership, or both.
|
|
|
|
An `External Collaborator` is not part of the owning organization but has direct workspace access. This includes subcontractors, providers, clients, and external reviewers.
|
|
|
|
Workspace membership can override applicable inherited workspace permissions.
|
|
|
|
## Agency
|
|
|
|
Type of organization that manages one or more brand/client workspaces for customers.
|
|
|
|
Use `Organization` for the product model unless specifically describing an agency customer.
|
|
|
|
## 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.
|
|
|
|
Channels are configured inside a workspace. The connector or integration credentials used to access external systems are owned by the organization.
|
|
|
|
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.
|