Private workspace
Store reports, datasets, builds, and other durable artifacts visible to the tenant.
Agent environment
Use the Hermes Hub agent environment by keeping durable tenant artifacts in the private workspace, treating company storage as shared input when granted, and using the documented environment keys for tenant identity and runtime access. Keep credentials, private browser state, and runtime software under the tenant runtime boundary rather than shared storage.
Use each path for its documented purpose.
Store reports, datasets, builds, and other durable artifacts visible to the tenant.
Use shared company or team content only when the tenant has the appropriate grant.
Keep credentials, browser state, skills, cron configuration, and caches in operator-managed runtime locations.
Review paths, environment variables, browser access, skills, cron, and file handling.
Learn moreConnect environment use to tenant identity, access, policy, and runtime controls.
Learn moreDiscuss workspace, company storage, runtime, browser, skill, and cron boundaries for Hermes Hub.
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.