Tenant-scoped access
Company context, work, integrations, brand assets, documents, and team members are kept within the named tenant. An invitation grants access to one workspace—not the whole platform.
SECURITY & TRUSTBusiness context is valuable.
Business context is valuable.
It should stay that way.
CompanyMateHQ is designed around a simple idea: an AI workforce must be useful without becoming an unaccountable way to move sensitive company information or real-world decisions.
THE OPERATING MODEL
Permission, scope, and a visible record.
Security is not one setting. It is a set of choices in the product: separate tenants, scoped integrations, explicit permissions, approved external actions, and the ability to understand what happened later.
Role-aware permissions
Standard members can use the workspace. Read-only members can view it and complete their checklist, without changing company data or directing the AI team.
Approval for real-world action
Agents may prepare internal work, but sends, publishing, payments, filings, bookings, and irreversible changes remain an explicit human responsibility.
Server-side integrations
Connected service credentials are held server-side. Finance is read-only by design, and dedicated Reception connections keep customer-facing access separate from an owner's personal mailbox.
Working-hours controls
Each tenant controls its own operating hours and can pause the AI workforce. Pausing preserves the queue and checklist rather than letting work continue invisibly.
Audit-minded workflow
Work moves through a visible operating queue, and completed work remains in an archive so owners can see the work, source, and review status.
RESPONSIBLE USE
Good security needs good operating habits.
- ✓Keep the email account used for CompanyMateHQ secure and remove access promptly when a colleague leaves.
- ✓Connect only the business accounts and mailboxes appropriate for the role.
- ✓Check every output before it becomes a customer, financial, legal, or public action.
- ✓Contact us promptly if you suspect an account or security issue.
Let's discuss the boundaries before the build.
We can talk through the agents, data, integrations, and approval points your business needs before you put meaningful context into the workspace.
Talk to us →