# ServiceConfiguration

ServiceConfiguration

Service-level configuration for one supported `service` + `channelType`: its
engagement capabilities and `content`. The channel-agnostic baseline — today
the same fields as `ChannelConfiguration` minus `channelId` and the per-channel
`authorizationStatus`. This overlap is incidental, not a contract: it is a
distinct type so the service-level catalog can evolve independently of the
per-channel config (either side may add fields the other doesn't share).

**Status:** ⚠️ Experimental

**Fields:**
- `channelType`: `ChannelType!` - The channel type within the service (e.g. profile, page, business).
- `content`: `[ContentConfiguration!]!` - Content config — one entry per content type, or a single entry
grouping several types that share identical rules. Empty when none is exposed.
- `engagement`: `[EngagementTypeConfiguration!]!` - Engagement capabilities — one entry per engagement type. Empty when
engagement isn't supported for this service + channel type.
- `service`: `Service!` - The social service this config describes (e.g. twitter, instagram).