Company Admin

This edition is for the people who run the company workspace: owners, studio leads, operations - anyone who decides how Ceruleo is set up rather than only working inside it. It assumes you have read (or will read) the General User edition; everything there applies to you too. What this edition adds is the machinery: the settings, templates, and invitations that shape what everyone else experiences.

Every configuration decision in this edition serves one idea: the work drives the shape. Ceruleo is built for creative, non-linear, iterative projects - the kind that start as a spark, not a scope document - and your job as an admin is to provide scaffolding that supports that evolution, never a cage that prevents it. Templates are starting sketches. Permission grids are guardrails. When this edition shows you a knob, it will also tell you what kind of team each setting fits - look for the ⚙ Make it yours notes.

The one distinction that governs everything

Ceruleo has exactly two kinds of people, and the difference is set at the moment you invite them:

• A company invitation makes someone a company user: they join your workspace, see company tools (Sparks, contacts, programs, statuses), and can be granted company-level capabilities.
• A project invitation makes someone a collaborator on that one project - nothing more. Clients, vendors, and partners belong here. A project invitation never grows into company membership on its own; there is no promotion path except an explicit company invite.

Cost of choosing wrong, in both directions: invite a vendor to the company and they can see your company contacts, programs, and idea pipeline - things you almost certainly did not mean to share. Invite an employee to projects only and they will work for months missing the company half of the platform, usually without knowing it exists. When someone says "I don't see Sparks," this distinction is the answer far more often than permissions are.

Each person belongs to at most one company - a second company invitation will be refused, not merged.

Getting around

Every page inside a project carries the project bar at the top: the project name (click it for recent items, other projects, and the dashboard) plus one-click links to every tool the viewer can open. Worth knowing as an admin: the bar is permission-filtered per member by the same per-project grids you configure - a member's bar shows exactly the tools their grid allows, and the Organizer entry appears only for people who can reorganize.

How this edition is organized

The chapters follow the order in which a company actually gets set up: workspace and branding → members, invitations, and per-member capabilities → permission templates → programs and project statuses → template families (structure, logs, notes, flags, spark categories, asset types) → the company library → contacts administration. The template chapters cross-link into the General User parts they power - structure templates into Part 1, log templates into Part 4 - and the shared material appears in both editions so neither reads with holes in it.