ENABLAYER / ADMIN STUDIOSetup overview
Customer workspaceBack to workspace
SETUP

Get the workspace ready without losing control.

Connect approved systems, shape the workspace in Space Builder, define records governance and verify launch readiness.

Launch readiness0%
1Connect systems

Choose the customer-owned sources Enablayer may query.

2Shape the workspace

Use Space Builder for organization, branding, layout, content and the default home experience.

3Verify before launch

Identity, permissions, source boundaries and write safety must pass.

ORGANIZATION

Define the customer workspace.

These labels shape the experience without changing customer source data.

BRANDING

Make it feel like their workspace.

Use customer-owned brand signals. Enablayer remains visible as the product layer.

ORG
WorkspaceWorkspace preview
CONNECTIONS

Connect the stack without becoming the system of record.

Start read-only. Each connector explains prerequisites, approved capabilities and customer-authorized scope before anything is connected.

RECORDS HUB

Decide where the truth lives.

Enablayer moves and presents information, but the customer chooses the system of record for every domain. Derived Sheets and dashboards are clearly labeled operational views.

AUTHORITY MAP

Choose a source of truth

Customer-owned
DOCUMENT HOME

Choose the central repository

System of record
DATA FLOW PREVIEW

See exactly what an import will do before it runs.

No changes yet
Preview how records will move while preserving the selected customer-owned source of truth.
Enablayer is the traffic controller, not the filing cabinet. Files and rows are processed transiently inside the customer runtime, written to the selected customer system, verified there, then purged from temporary Enablayer processing. Only governance and run metadata remain.
USERS & ROLES

Loading workspace membership…

Enablayer roles limit the interface. The customer identity provider and source-system permissions remain authoritative.

LAUNCH

Run the pre-flight check.

We do not call a workspace live until identity, configuration, connections and zero-custody boundaries are ready.