Authorized user
Completes the workflow
ProductsUse case · Company AI governance
Give more people and agents access to AI. Keep control of the company.
Manage who can use which knowledge, skills, tools, credentials, projects, agents, and actions without reducing AI adoption to a policy document.
Start free. Test one role-based knowledge and capability boundary.
Company policy in the workflowPeople, groups, access, approval
Shared in HQRole-appropriate AI capability
Scoped agent
Uses only granted context
Reviewer
Approves the sensitive action
The boundary travels with the company work instead of sitting in a policy document beside it.
Role-appropriate knowledge and tools
Credentials stay out of prompts
Sensitive actions retain clear approval ownership
The broken workflow
The policy says one thing. The workflow is configured somewhere else.
As AI adoption grows, every individual setup becomes another place where context, credentials, customer data, and authority can drift away from company intent.
Access becomes all or nothing
Teams either withhold useful context or share too broadly because the operating system does not reflect roles and groups.
Credentials enter the conversation
Keys and tokens are copied into prompts, files, or messages when governed tool access is not built into the workflow.
Approval happens after the action
Sensitive communication or system changes reach people only after an agent or user has already acted.
The HQ workflow
Put governance inside the company workflow.
HQ connects membership, groups, knowledge, projects, skills, tools, secrets, agents, and review boundaries so useful access can expand deliberately.
- 01Operations / IT
Define the company boundary
Separate companies, clients, or brands and assign people and agents to the right membership and groups.
- 02System owner
Grant the minimum useful capability
Provide only the knowledge, project, skill, tool, credential, and action scope required for the role.
- 03Security and workflow owner
Test access and approval
Verify the authorized workflow succeeds, the unauthorized path fails, and sensitive output reaches the right reviewer.
Why HQ
A policy describes the boundary. HQ carries it into the work.
HQ does not claim to inspect every private prompt in every external tool. It governs the company-owned context, capability, and workflows that teams operate through HQ.
The layerIndividual AI accountsWith HQ
KnowledgeFiles attached or uploaded by each userCompany-owned access by membership and group
ToolsPersonal keys and per-user configurationGoverned company integrations and secret access
ActionsApproval depends on user judgmentReview boundaries attach to the shared workflow
What the team can inspect
Governance is proven by access behavior, not policy language.
A useful test shows that the right person or agent can complete the job, the wrong one cannot reach the protected context, and the sensitive action still reaches its accountable reviewer.
Membership and groups
People and agents belong to the correct company and role-based access group.
Scoped capability
Knowledge, projects, skills, tools, and secrets are granted for a specific workflow.
Approval boundary
Draft-only, review-required, and escalation behavior are explicit where the business needs them.
What changes
AI adoption expands with clearer control.
- 01
Give teams useful access by role
- 02
Reduce raw credential sharing
- 03
Keep accountable people in the approval path
Your first win
Test one real boundary from both sides.
Start with a single knowledge area and capability, then prove that company access behaves the way the policy intends.
Set up your first governed workflow- 1
Create one group for a real team or role
- 2
Grant one knowledge area plus one tool or skill
- 3
Verify authorized use, denied use, and the required review step
Built for company work
Govern what the company owns and operates.
HQ gives companies control over HQ-owned knowledge, memberships, projects, skills, agents, integrations, secrets, and workflows without claiming surveillance of private activity elsewhere.
- Explicit company and client boundaries
- Revocable role-based access
- Inspectable company-owned workflows and approval paths
HQ is not positioned as a monitor of every private prompt or unsupported third-party activity outside company-owned HQ work surfaces.
Start with one workflow
Make useful access the default and excess access the exception.
Start with one group, one shared capability, and one access test that proves the company can move faster without giving up its boundaries.