Concepts
Workspaces
The unit of multi-tenancy. One workspace = one site = one API key.
A workspace is the unit of multi-tenancy in Brandfine. Each
customer site (each consumer integration) maps to exactly one
workspace; that workspace's API key is what
/external/* endpoints accept.
What a workspace owns
- Posts — articles, blog entries, service pages, visa guides. Grouped by post type.
- Post types — generic taxonomy of post families. The
default is
blog; you can define custom types per workspace (services,visas,guides, etc.). - Categories — workspace-scoped tags. Optional grouping layer over posts.
- Navigations — named tree structures (
header,footer-services) the consumer site renders. Each item is either a link to a post, a custom URL, or a heading. - Locales — BCP47 codes the workspace serves. The first one is the canonical fallback.
- Settings —
customConfig(free-form JSON the consumer interprets) andschemaOrg(workspace-level structured data merged into every page's JSON-LD).
What a workspace doesn't have access to
A workspace's API key can only read its own data. It can't list other workspaces, can't read other workspaces' posts, and can't write anywhere (the external API is read-only — writes happen via the CMS UI).