Feature
Organization access
Roles, teams, scoped API keys, org policies and an audit log.
Each member has a role in the organization (owner, admin, editor or viewer) and may belong to teams as a member or lead. Role mappings map external identity-provider role names to Workloom roles.
API keys are bearer credentials issued to one user in one organization and limited to granular scopes written verb:resource; there is no admin super-scope. The token is shown once at creation. Org policies are named rules toggled from the admin dashboard, and the admin API exposes an audit log.
More features
All features →- 01
Organization packages
Scoped, immutable packages of skills, agents, prompts and configs, owned by your org.
- 02
Workspace desired state
Each workspace declares which packages, versions and providers every target gets.
- 03
Provider rendering
Assets become each provider’s native files, from a deterministic render plan.