Governance
AI Employees that answer to people
EmployAIQ is built around one idea: an AI Employee should only do the work it has been given, with the tools it has been allowed, at the level of independence it has earned — and a person can review its recorded actions and stop it at any time.
Reasoning and control
Cognition guides the reasoning. Governance is the code-enforced control layer around tool use.
Step 1: Role
Sets the job
The role becomes the AI Employee's operating brief.
- Responsibilities and operating instructions
- Capabilities and skills
- The tools the role is approved to use
- Reasoning guidance for the role, where configured
Step 2: Context and memory
Informs the reasoning
What the AI model can draw on for the current piece of work.
- Recent conversation context
- Relevant business knowledge from your workspace
- Lessons from human feedback, where available
Step 3: Cognition
Guides the reasoning
The AI model interprets the situation within the operating brief.
- Decides whether to reply or to request an action
- Can only request tools the role makes available
Step 4: Governance
Controls the action
Separate platform code checks each requested tool action before it runs.
- Allowed tools and the AI Employee's trust level
- Human approval requirements and any approval rules you have saved
- Spending caps on actions that move money
- Result: the action runs, is held for approval, or is refused — and is recorded
Step 5: You
Stay in control
People oversee the work and set the boundaries.
- Approve or reject held tool actions
- Set or change trust levels
- Pause workspace autonomy or deactivate an AI Employee
- Review action and approval history
Step 6: Outcomes
Measured and reported
Results can be reported on your dashboard for human review.
- Evidence for people to review — results do not change the AI Employee's decisions on their own
What this means in practice
- Conversational replies are not approved message by message; they follow the role's instructions and your content.
- Applicable tool actions can be held for a person to approve or reject before they run.
- Higher trust does not mean unlimited autonomy: the role's tool permissions always apply, and actions that move money need spending caps.
- Pausing workspace autonomy holds autonomous replies and outbound email for review; a deactivated AI Employee cannot use tools or act on its own.
- Tool actions and approval decisions are recorded and shown in your workspace's activity history.
For technical teams
EmployAIQ composes a role-specific operating brief and runs an AI-model tool-calling loop within a capability-derived tool allowlist. A separate, code-enforced governance layer applies trust and approval decisions before tools execute, while action and approval records provide operational visibility.
Cognition is the role-specific reasoning guidance an EmployAIQ AI Employee uses when interpreting its work. An AI model applies that guidance to the current conversation, relevant business knowledge and available lessons, then decides whether to respond or request an approved tool.
Roles and responsibilities
Who does what
The AI Employee
Approvers
The workspace owner
Capabilities and skills
A defined role, not open-ended access
Role
Capabilities
Skills
Controlled tools
Your knowledge
Human oversight
Trust levels
Autonomy is earned, one level at a time
L1: Supervised
Applicable tool actions — sending an email, publishing content, updating a record — wait for a person to approve them.
L2: Rule-assisted
Works like L1, except where you have saved an approval as a standing rule: matching routine actions can then proceed. Actions that move money honour only narrowly scoped rules.
L3: Trusted
Routine tool actions run without waiting for approval. Actions that move money still wait for a person.
L4: Autonomous
Tool actions run within the role's permissions; actions that move money run only within spending caps you set. Autonomous does not mean unrestricted.
- Every AI Employee starts at L1.
- The system recommends a promotion; a person confirms it.
- The owner can lower an employee's trust level at any time.
- Higher trust never removes the role's tool permissions.
- Conversational replies are not approved message by message; approval applies to tool actions.
- The approval check runs in platform code where tools are executed, not in the AI model.
Controls
What operates today, what is configured with you, and what is in development
- Operates today: available in the platform now.
- Configured per customer: set up for each customer during guided onboarding.
- In development: not yet available.
Controlled tool access
Human approval
Approval rules from your decisions
Action and approval history
Escalation to a person
Stop switches
Workspace data separation
Encrypted credentials
Policies, limits and connected systems
Additional channels
Automatic trust adjustment based on performance
Guided production configuration
Production is configured with you
If your organisation has specific security, identity, data-handling or approval requirements, we discuss them during scoping. Enterprise deployments