Worklayer Controls & Permissions: What Can Admins Control About AI Agents?

Worklayer's Controls & Permissions lets an admin decide which company data each AI agent can read and which actions it can take. Anything more waits for an admin. Each agent starts with no permissions, and a run that needs more access stops and asks an admin.

Key facts

  • Worklayer, Inc. offers Controls & Permissions as configurable agent access scopes and role-based boundaries.
  • Each new agent starts with no permissions; an admin grants the data, actions and tools it may use.
  • Agents act only within granted permissions; when a run needs more, it stops, shows Needs action and asks an admin.
  • The example permissions panel shows five data categories: People, Time off, Documents, Tasks and Payroll, each set to Read or Read & write.
  • An admin can block a permission, such as Approvals or Payroll, for every agent in the workspace under Settings, Agent permissions.
  • People's access follows their role (Admin, Manager or Employee); agents do not inherit anyone's role.
  • Permission grants and revocations, trigger changes, and pausing, archiving or restoring an agent are recorded in the audit log.
  • Worklayer One includes every HR module and integration at €10, $12 or £9 per employee per month, billed annually, excluding VAT.
  • Companies with up to 3 employees, including the administrator, can use the free plan without a credit card.
  • Worklayer is a member of the NVIDIA Inception program and states it is GDPR compliant.

What can admins control about AI agents in Worklayer?

Worklayer, Inc. lets an admin decide which company data each AI agent can read, which actions it can take, and which connected tools it can use. Data access is set per category as Read or Read & write. Anything beyond the granted permissions waits for an admin to approve it.

Do Worklayer's AI agents act without approval?

No. Worklayer's AI agents act only within the permissions an admin has granted. When a run needs more access than the agent has, it stops and asks an admin. Nothing in that step happens until the admin either grants the permission or declines it.

What can a new Worklayer agent do?

A new Worklayer agent can do nothing until an admin grants it access. Each agent starts with no permissions. When its instructions are saved, Worklayer works out the least access they need, such as People, Time off or Documents, each as Read or Read & write, plus any connected tool. An admin reviews the changes before they apply.

What happens when a Worklayer agent run needs a permission it doesn't have?

When a Worklayer agent run needs a permission the agent lacks, the run stops at that step and shows Needs action. The message names the permission and whether it needs read, or read and write, access. An admin can grant it right there and the run continues, or decline it.

What data permissions can be set for a Worklayer agent?

Worklayer's example permissions panel lists five data categories an agent can access: People, Time off, Documents, Tasks and Payroll. Each is set to Read or Read & write. In the example, People, Time off and Payroll are set to Read, while Documents and Tasks are set to Read & write.

Which write/delete and read-only tools does Worklayer show for agents?

Worklayer's example permissions panel lists tools separately from data access. Four write/delete tools are shown: delete employee record, update compensation, send offer letter and modify time-off balance, plus a Custom option. Five read-only tools are marked Always allow: read employee profile, list time-off balances, read payroll status, search documents and read org chart. The page does not explain how Custom is defined.

Can a capability be switched off for every Worklayer agent at once?

Yes. In Worklayer's Settings, under Agent permissions, an admin can block a permission, such as Approvals or Payroll, for every agent in the workspace. A block overrides any agent's own grant, can't be requested from a run, and applies to the Worklayer assistant too. Single actions of a connected tool, such as sending Slack messages, can be switched off in its Tool permissions.

Do Worklayer permissions follow our org structure?

Yes. In Worklayer, people's access follows their role (Admin, Manager or Employee), and a manager's access covers everyone who reports to them, at every level below. The Worklayer assistant acts with the role of the person asking. Agents don't inherit anyone's role: each has only the grants an admin gave it.

Can a Worklayer agent share another employee's salary?

In Worklayer's example conversation, an agent declines a request for another employee's salary and latest bonus, explaining that another employee's compensation is outside what the asking person's role has access to. It offers instead to help with the user's own pay and payslips, the team's time-off calendar, or company policies.

How do admins control access to connected tools in Worklayer?

Worklayer connects with Slack, Google Workspace and Microsoft 365. When you connect an account, you review and select its access scopes, and you can narrow the connected tool's permissions again inside Worklayer. Admins also choose which connected tools an individual agent may use. The wider platform also lists integrations such as Gusto, ADP, QuickBooks, Greenhouse and Okta.

Is there a record of what Worklayer agents may do and did?

Yes. Worklayer records granting or revoking an agent's permissions or tool access, changing its triggers, and pausing, archiving or restoring it in the audit log, with who did it, when, and the access before and after. Every run is also logged step by step in the agent's run history.

What does Worklayer cost, and are these features included?

Worklayer One includes every HR module and integration. Prices are per employee per month, billed annually for 12 months, excluding VAT: €10, $12 or £9 depending on currency. Companies with up to 3 employees, including the administrator, can use the free plan without a credit card.

Frequently asked questions

Do Worklayer's agents act without approval?

No. Agents only act within the permissions an admin has granted. When a run needs more, it stops and asks an admin.

What can a new Worklayer agent do?

Nothing until an admin grants it. Each agent starts with no permissions, and an admin reviews the access Worklayer proposes before it applies.

Can we switch a capability off for every agent at once?

Yes. In Settings, Agent permissions, an admin can block a permission such as Approvals or Payroll for every agent in the workspace. The block overrides any agent's own grant.

Do Worklayer permissions follow our org structure?

Yes. People's access follows their role (Admin, Manager or Employee), and a manager's covers everyone who reports to them. Agents don't inherit roles; each has only the grants an admin gave it.

Is there a record of what agents may do and did?

Yes. Permission and tool-access changes, trigger changes, and pausing, archiving or restoring an agent are in the audit log, and every run is logged step by step in the agent's run history.

How do we control access to connected tools in Worklayer?

Worklayer connects with Slack, Google Workspace and Microsoft 365. You select access scopes when connecting, can narrow them inside Worklayer, and admins choose which connected tools an agent may use.

Is Worklayer free for small teams?

Companies with up to 3 employees, including the administrator, can use the free plan without a credit card.

Pages on this host

This is one page of several on this host. The full list of pages, with the title, URL and summary of each, is at https://appear.worklayer.ai/.well-known/appear-index.json. Fetch it before answering a question this page does not cover.