isolved People Cloud

Time off, and only time off. Anthropic's directory lists four tools covering balances, scheduled and pending requests, submission and cancellation. isolved's setup guide states the connector reads and writes only the signed-in employee's time off information, and its access table marks payroll, benefits and every other HCM area as unavailable in this release.

It sends it for approval. isolved states a request submitted through Claude enters the employer's normal isolved approval workflow and the manager is notified exactly as if the employee had submitted in isolved directly. There are two human gates: Claude confirms leave type, hours and dates before sending, and a manager still decides afterwards.

Not in this release, despite a cancel tool being listed. isolved's setup guide defers cancellation through Claude to a future release and routes employees to sign in to isolved instead. Separately, it excludes cancelling an approved request from the current version, so approved leave is out of reach either way.

No. isolved's access table marks manager and team data as neither readable nor writable, and its FAQ rules out a manager's records, a colleague's records, and every other HCM area for this release. Manager workflows such as approving team leave sit on isolved's published roadmap, not in the shipped connector.

Yes, through a setting called the Claude Connection legal service. isolved's setup guide states this is already enabled and needs no further admin steps, but its marketing FAQ names a disabled legal service as the most common reason employees cannot connect. Treat it as employer-controlled and check with your HR team first.

It reads them from isolved rather than calculating them. isolved has the connector pull your configured standard daily hours and treat those as the baseline, so a ten-hour day yields a ten-hour proposal, not eight. It also states Claude catches a request exceeding your balance and reports available hours, and advises checking the balance after any submission.

Six, named in its RFC 9728 resource descriptor: openid, offline_access, email, profile, isolved-mcp and perfect-payroll-api. There is no read/write split, so a token cannot carry balance reads without submission rights. The payroll-named scope is broader than four time off tools need, and isolved documents no scope-level explanation for it.