Tenant files
Keep tenant home files, workspace content, and runtime artifacts within the tenant-owned workspace boundary.
Files and storage
How do I use Hermes Hub tenant files and company storage?
Use Hermes Hub tenant files for data and operational artifacts belonging to a private tenant workspace, and use dedicated company storage for shared company or team content when access is explicitly granted. Keep the two scopes separate so company data does not collapse tenant boundaries or expose a legacy agents workspace.
Two storage scopes
Storage design starts by identifying who owns the data and who should access it.
Company storage
Migrate shared company and team content separately while preserving team-relative paths and intended share-group controls.
Explicit access
Grant company or team access deliberately; do not infer access from a shared legacy workspace tree.
Hermes Hub storage FAQ
Should company data be copied into every tenant workspace?
No. Company and team content should be migrated separately into dedicated company storage and shared only where access is granted.
What should remain tenant-scoped?
Tenant workspace files, runtime artifacts, credentials, sessions, and operational records should remain associated with the tenant boundary.
Why avoid the legacy agents tree?
The documented migration boundary keeps the legacy agents workspace out of company storage to avoid exposing tenant-specific workspace content.
Design tenant and company storage
Map tenant files, shared company content, access groups, migration boundaries, and operational artifacts.
Architecture conversation
Tell us what your team needs to control
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.