Client configuration

Everything Nexus stores for a client in one place — identity, team, content and publishing settings, capacity, the strategy files onboarding produced, and every connector with its health. Most settings edit in place; API keys only ever appear as a masked fingerprint.

served at

/dashboard/<client>/client-config

access

token-gated link

fed by

a Slack tool

branding

the client’s owner

Where the data comes from

The client's configuration, its files on the volume and the connector health checks.

How it works

A link that is the current state, not a snapshot.

Rendered from the client model on request; the link a strategist shares is never stale.
Every dashboard link carries a per-client token; nothing is indexed or public.
Branded to the client’s owner: an agency’s partner sees their own byline and accent.

Evidence for this dashboard

0 agents keep it current48 agents in the registry19 live dashboards6 governance claims with code behind them

No sandbox sample is published for this dashboard yet; live dashboards are client data and are never linked here.

Customer evidence appears here only with a client's written consent. System facts are generated from the same model this page renders from.

Machine twin: /dashboards/client-config.json · /nexus.json · /llms.txt

Early access

Put a team on an operating system.

Nexus is rolling out to a first cohort of agencies and go-to-market teams. Tell us about yours and we will be in touch as access opens.

Prefer to tell us more first? Run the two-minute readiness assessment →