Today
What needs your attention right now — no menus, no hunting. Everything else is one click away.
Platform Dashboard
Service-wide operations across every customer. Tiles marked Live read directly from the platform; tiles marked Connect source are wired and waiting on their data model — no estimated figures are shown.
Customer Management
Every Service customer on the platform. Select a customer to inspect their account, review usage, and open their workspace in customer view.
| Customer | Owner | Team | Status | Last login | |
|---|---|---|---|---|---|
| Loading customers… | |||||
Company Management
Lifecycle controls for every company account: create, suspend, archive, transfer ownership, and review subscription and usage. Lifecycle changes write to the account record and the platform audit log.
| Company | Owner email | Subscription | Lifecycle | Created | Actions |
|---|---|---|---|---|---|
| Loading… | |||||
Template Management
Platform-level templates that every Service company can draw from. Stored in cc_service_templates. Starts empty — create the first of each kind below.
User Management
Who has access, and at what level, across the Service platform.
| Owner | Company | Tier | Last login | |
|---|---|---|---|---|
| Loading… | ||||
Platform Configuration
Global settings for ClarityCommand Service. Stored in cc_service_config/platform. Changes are audited.
Audit
Every administrator action and customer-side event, reconciled across the platform.
Security
Administrators, authentication, and role assignments for the Service platform.
Products
Each product is its own administration space — configuration, templates, customers, analytics, permissions. They look different on the surface and obey the same governance underneath. Pick one to administer everything about it.
Families
A family is a different customer than an organization. It has a Griot instead of an account owner, members instead of seats, inheritance instead of churn, and an estate lifecycle a company never has. ClarityCommand manages both — side by side, with different governance.
Multi-tenant Legacy Room communities. Each is owned by a Griot who governs its own members and permissions — the platform never decides what a cousin or executor may see.
Lifecycle: Griot ownership · members, not seats · estate events · inheritance & succession
Churches, schools, businesses, assisted-living facilities. Seat-based and billing-driven, with employees and operational records.
Lifecycle: account owner · seats & billing · employees · renewal & churn
Roles & Permissions
Determine who can enter each product, what they can see, and what they can do. Navigation says where you can go; Access says what you're allowed to enter. (ADR-008)
legacy_rooms); members are the real roster (legacy_rooms/{roomId}/family_members). Layer 1 is the identity's app grants (ADR-006); Layers 2&3 are each product's self-described sections + actions (ADR-007). Access profiles are tenant-scoped — access_profiles/{tenantId}/people/{personId} — and every change is recorded in the audit log. One resolver, can(person, product, section, action), gates every surface.
Invitations Forthcoming
An invitation creates one identity (ADR-006) with an empty access profile you grant from Roles & Permissions. Arrives with the identity build.
Operators
The staff who administer ClarityCommand HQ — not customers. Each operator has a role and a product scope; granting authority is governed, reason-required, and audited. Granting Platform Owner is high-risk. (Slice 2)
Reasons & Lifecycle
Every governed action follows one lifecycle and writes one audit shape. No feature invents its own behavior — that's what makes the platform provable.
requestId. A retry returns the prior result and never repeats the mutation.reverse-transfer endpoint.Operator Governance
Live health of who runs the platform: composition, the cutover state, failed authorizations, and recent governance activity. Read-only.
Analytics Forthcoming
One place for the numbers, instead of dashboards scattered across products.
Workflows Forthcoming
What the platform should do without you having to ask.