Organization vs Workspace
A workspace always belongs to exactly one organization. Members can exist in multiple workspaces within the same org but are managed through a single identity in Access.
Shared Identity Provider
Organizations can configure a single SSO connection in Access that applies across all child workspaces. Users authenticate once and receive tokens scoped to each workspace they belong to.Inherited Settings
Certain Guard policies and compliance settings defined at the organization level are automatically inherited by all child workspaces. Workspace admins can view but not override inherited settings. Inherited settings include:- Minimum password policy
- MFA enforcement
- IP allowlist ranges
- Audit log retention period
Workspace-level settings take precedence over inherited settings where they are more restrictive. A workspace cannot be configured to be less restrictive than the org-level baseline.
Organization API Object
Managing Organizations
Organizations are managed through the Essal admin dashboard at admin.essal.cloud/org or via the API using a workspace admin token with theworkspace:admin role.