Organizations & workspaces
The two-level home of everything — orgs hold workspaces, workspaces hold the work, and roles decide who can do what.
Everything in GoRunner lives in a two-level hierarchy:
Organization → roles: owner / admin / member
└─ Workspace → roles: admin / editor / operator / viewer- An organization is the top of the tree: its members, its security settings, its AI provider for Keel, and any number of workspaces. You can belong to — and own — several.
- A workspace is where the work lives: workflows, connections, runs and folders are all workspace-scoped. Switch between them (and between organizations) from the switcher next to the logo.
Isolation
Workspaces are the isolation unit. Nothing in one workspace can see or reference another's workflows, connections or runs — and cross-tenant reads answer 404, never 403, so even existence is not disclosed across boundaries.
Roles
Org roles govern management (members, workspaces, settings); workspace roles govern the product surface (what you can build, run and read). A person's rights are the union of the two. API tokens carry only the scopes stamped on them — never their creator's live role — and can neither manage tenancy nor mint further tokens.
Security model
- Envelope encryption: each organization has its own data key wrapping every credential, sensitive variable and paused-run state. Deleting an organization destroys the key — its secrets become unrecoverable by construction.
- Audit trail: every credential decryption, every Keel apply and every tenancy change is recorded, org-scoped, readable by org admins.
- Sign-in: accounts with email verification, password reset, and TOTP MFA with recovery codes.
Enterprise
For larger organizations: OIDC and SAML 2.0 SSO (per-org, with just-in-time provisioning), SCIM 2.0 user lifecycle (Okta / Microsoft Entra driven, with real deprovisioning), audit export, and embed sessions for building GoRunner into your own product. Talk to us to enable these for your organization.