Foundry Control

Control is Foundry’s managed collaboration and operations layer. It surrounds portable Core sites with the safeguards and shared context a team needs when more than one person is building, reviewing, approving, or publishing.

What Control adds

• People and permissions: accounts, roles, scopes, and private context.
• A safer review loop: drafts, diffs, previews, approvals, and durable review history.
• Managed operations: publishing, provider integrations, credentials, contacts, analytics, automation, and recovery state.

What remains Core

Core still owns the portable Hugo source, templates, blocks, theme and brand contracts, validation, rendering, and the site’s ordinary build path.

Boundary note: Control can make the workflow feel like a calm cockpit, but it is not a proprietary replacement for the repository. A team can leave the managed layer with its site source intact, and a site can render without Control.

When to choose it

Choose Control when the cost of coordination, approval, private context, or operational recovery is higher than the cost of running those concerns alone. Keep routine Core work in the repository and use the managed layer where it adds real safety or shared visibility.

Public documentation explains the boundary and the value. Detailed operator, Composer, forms, and integration contracts belong in the authenticated internal handbook because they describe permissions, provider setup, and operational state.