44 lines
1.2 KiB
Markdown
44 lines
1.2 KiB
Markdown
# Channels
|
|
|
|
Channels are configured social destinations inside a workspace. They represent the account, handle, page, feed, newsletter, or other publication destination where content will eventually be handed off for publishing.
|
|
|
|
Channels are workspace-owned data. Organization-owned connectors may provide credentials for external systems, but the workspace owns which destinations are available for content planning.
|
|
|
|
## Model
|
|
|
|
A channel has:
|
|
|
|
- `id`
|
|
- `workspaceId`
|
|
- `name`
|
|
- `network`
|
|
- optional `handle`
|
|
- optional `externalUrl`
|
|
- `createdAt`
|
|
|
|
`network` is a controlled string matching the frontend channel network options:
|
|
|
|
- `Instagram`
|
|
- `TikTok`
|
|
- `Facebook`
|
|
- `LinkedIn`
|
|
- `YouTube`
|
|
- `X`
|
|
- `Reddit`
|
|
- `Website`
|
|
|
|
Channel names must be unique inside a workspace for the same network.
|
|
|
|
## Behavior
|
|
|
|
- Authenticated users with workspace access can list channels for their active workspace.
|
|
- Workspace managers can create channels.
|
|
- Content planning uses configured channels as selectable destinations.
|
|
- Development seed data should create real workspace channels instead of relying on content target labels as fake channels.
|
|
|
|
## Not In Scope
|
|
|
|
- External connector credentials.
|
|
- Publishing directly to social networks.
|
|
- Channel deletion, archiving, or editing.
|