Identity and access
Create or select the tenant, inspect access state, and define lifecycle ownership.
Hermes Hub configuration
Configure a Hermes Hub tenant by setting its identity and access state, then reviewing its runtime, storage, environment keys, policies, skills, schedules, and operational evidence. The public Hermes Hub contract exposes these as tenant-scoped control-plane surfaces rather than one shared agent configuration.
Keep configuration tied to the tenant boundary and document the operator who owns each change.
Create or select the tenant, inspect access state, and define lifecycle ownership.
Review agent state, policy boundaries, skills, flavors, and environment key scope.
Configure tenant-visible files, shares, schedules, and the evidence used to verify runs.
Understand tenant-visible workspace, company storage, environment keys, and runtime boundaries.
Learn moreReview tenant, agent, files, skills, cron, shares, and policy endpoint groups.
Learn moreSee the control plane's lifecycle, A2A edge, releases, policies, and usage evidence.
Learn moreDiscuss tenant identity, access, policy, storage, and runtime configuration with Bewize.
Architecture conversation
Share your deployment boundary, number of agents, work surfaces, and governance requirements. We will reply by email to arrange a focused technical discussion.
Email the Bewize teamThis opens your email application. Read our Privacy Policy.