Platform
The operational surface of Scrydon — organisations, workspaces, identity, settings, licensing, and the controls every administrator works with.
The Platform section covers the operational surface every Scrydon administrator works with — organisations, workspaces, identity, settings, licensing, and the platform-wide controls.
Core concepts
| Concept | What it is |
|---|---|
| Organisation | The top-level tenant boundary. Every user, workspace, integration, and audit event lives inside exactly one organisation. |
| Workspace | A scoped collaboration unit inside an organisation. Workspaces hold workflows, knowledge bases, automations, and team grants. |
| Team | A named collection of users, used for scaling access grants. SCIM groups map to teams. |
| Integration | A connection to an external (or built-in) vendor — OpenAI, Microsoft, Scrydon Core, etc. |
Sections
Marketplace
Browse installed pack content, add Process Templates to an environment, and deploy Workflows.
Bug Reports
Voice-first bug filing — captures transcript, screenshot, console logs, and session replay.
Identity & Provisioning
SSO + SCIM with Microsoft Entra, Okta, OneLogin.
Knowledge base clearance
NATO-style document clearance — UNCLASSIFIED through TOP SECRET.
Identity providers
OIDC / SAML provider configuration and test flows.
Licensing
How the platform validates entitlements and enforces them.
Marimo notebooks
Python notebooks scoped to a workspace.
Related
- Security — authorisation, secrets, audit, mTLS.
- Compliance — how platform controls map to framework requirements.
- Deployment — install, license, upgrade.