Onboarding Book

A complete multi-chapter guide for teams adopting GyroX for the first time—workspace design, data model, roles, and your first automation in one flow.

1. Overview

GyroX is an AI-native operating platform where the app is built before the conversation ends. This onboarding book walks you through everything from creating your first workspace to shipping a real automation—in one continuous flow.

This book is meant to be read in order. Each chapter assumes the output of the previous one.

Time: ~18 min reading + ~30 min hands-on
Audience: adoption leads, admins, first builders
Prerequisite: org email domain, one target ERP module

2. Designing your workspace

A workspace is the operating unit of an organization. Within a single workspace you activate multiple ERP modules (GL, AP, AR, P2P…), invite members, and grant roles.

1Create a workspace with your organization email.
2Activate just one ERP module first (the pilot principle).
3Invite 2–3 core operators.
4Set branding (logo/theme) via design tokens.

Design tokens flow DB → API → CSS variables → Tailwind. Never hardcode colors in code.

3. Mapping the data model

GyroX represents assets, facilities, and spaces in a single resource ontology (instance + classification + dynamic schema + properties) rather than separate tables. Existing classifications are absorbed as typeKeys instead of new tables.

json

{
  "resourceType": "ASSET",
  "typeKey": "HVAC.CHILLER",
  "props": {
    "capacityRt": 350,
    "installDate": "2021-03-12",
    "siteId": "SITE-001"
  }
}

Normalize asset classes into typeKeys, not new ASSET_CATEGORY codes.
Absorb the 9-level space hierarchy into dynamic schema.
Set audit subjects to ACTOR (human, AI, system).

4. Roles and SSO

Start the pilot with least privilege, then integrate SSO and role mapping during expansion. All access follows a deny-by-default posture.

1Start with three base roles: admin, operator, viewer.
2Connect your Entra ID / OIDC provider.
3Automate role-group mapping via IdP group claims.

5. Ship your first automation

In the final chapter you describe your first operational screen in natural language, review the generated widgets, and ship them to your team via a share link. Every AI call routes through the AI Gateway, so cost and audit logs are unified.

If your automation mutates external systems, design approval gates and idempotency keys first. Preventing duplicate execution is the foundation of operational stability.

Once complete, your single-module pilot is production-ready. Next: measure KPIs over 30 days.

1. Overview

This book is meant to be read in order. Each chapter assumes the output of the previous one.

Time: ~18 min reading + ~30 min hands-on

Audience: adoption leads, admins, first builders

Prerequisite: org email domain, one target ERP module

2. Designing your workspace

A workspace is the operating unit of an organization. Within a single workspace you activate multiple ERP modules (GL, AP, AR, P2P…), invite members, and grant roles.

1Create a workspace with your organization email.

2Activate just one ERP module first (the pilot principle).

3Invite 2–3 core operators.

4Set branding (logo/theme) via design tokens.

Design tokens flow DB → API → CSS variables → Tailwind. Never hardcode colors in code.

3. Mapping the data model

json

{
  "resourceType": "ASSET",
  "typeKey": "HVAC.CHILLER",
  "props": {
    "capacityRt": 350,
    "installDate": "2021-03-12",
    "siteId": "SITE-001"
  }
}

Normalize asset classes into typeKeys, not new ASSET_CATEGORY codes.

Absorb the 9-level space hierarchy into dynamic schema.

Set audit subjects to ACTOR (human, AI, system).

5. Ship your first automation

If your automation mutates external systems, design approval gates and idempotency keys first. Preventing duplicate execution is the foundation of operational stability.

Once complete, your single-module pilot is production-ready. Next: measure KPIs over 30 days.