Connect an AI clientAI client
An AI assistant or coding agent, such as Claude, ChatGPT, Claude Code or Codex, that you connect to Mitratech Comp. It reads and acts on your comp data as you, within your role and the connection scopes you grant it.
, such as Claude, ChatGPT, Claude Code or Codex, and it can read and act on your comp data from inside the assistant you already work in. Anyone with a roleRole
What a person does in a compensation cycle, and what the product lets them see and do. There are seven, they are lateral rather than a ladder, and everyone who signs in holds one.
in the workspace can connect one. You need an account in the AI client and a sign-in on your workspace.
Mitratech Comp runs a Model Context ProtocolModel Context Protocol
The open standard AI clients use to connect to other software. Mitratech Comp offers an MCP server, so a client that supports it connects with nothing to install.
Read more (MCP) server, so there is nothing to install. Connecting Claude, ChatGPT or a coding agent walks through it.
Everything a connected client does, it does as you. Your role, the part of the organization you can see, and the fields hidden from your role all apply exactly as they do when you use Mitratech Comp yourself. A client can never see or change anything you can’t.
When you connect a client, you choose which connection scopesConnection scope
One of the nine permissions you choose when you connect an AI client, such as reading worksheets or generating the payroll export. A client can use only the scopes you granted, and never more than your own role allows.
Read more it gets, and it can use only those. A scope can only narrow what you can already do; it never adds to it. When a client asks for something outside the scopes you granted, the request is refused and the client is told which scope is missing. What each access scope covers lists all nine.
Within your role and your grant, a client can:
look up, add and correct employee records, departments, custom attributes and pay bandsPay band
The pay range for a job level — a minimum, a midpoint and a maximum.
Read more , and run an employee dataEmployee data
The record of your employees, their managers, departments, pay and ratings that pay bands, cycles and reports all read from.
Read more import;
create and configure a merit cycleMerit cycle
One round of planned pay changes, from the snapshot of your workforce through manager worksheets and approvals to the payroll file. A cycle on its own means a merit cycle.
Read more , including its funding poolsFunding pool
The money a cycle authorizes for pay changes, usually a percentage of eligible payroll. A cycle can carry three — merit, promotion and bonus — and each becomes a budget for every manager at launch.
Read more , merit matrixMerit matrix
The grid that turns a performance rating and a compa-ratio into a recommended increase, so every manager starts from the same guidance.
Read more , guardrailsGuardrail
The limits your compensation team sets on what a manager can recommend, a soft range inside a hard range. Outside the soft range a recommendation is allowed but has to be explained; outside the hard range the worksheet cannot be submitted until the number comes back in.
Read more and timeline, and launch it;
draft recommendations on a worksheetWorksheet
A manager's planning page: their own people, the inputs for each pay change, and every derived number recalculated as they type.
Read more , submit it, and approve or return the worksheets waiting for you;
read your cycle home and your notifications;
generate and send award lettersAward letter
The PDF letter that tells one employee what a finalized cycle decided for them — their current and new base pay, any increase or bonus, and the date it takes effect. An employee whose pay did not change gets one too.
Read more , and produce the payroll exportPayroll export
The CSV file of approved pay changes a finalized cycle produces for your payroll system, one line per employee whose pay changes, each carrying the pay effective date.
Read more .
Some actions stay in Mitratech Comp, where they have their own confirmation. No scope reaches them:
inviting, suspending or removing members, and changing their roles;
your workspace’s settings, single sign-onSingle sign-on
Signing in with your own company's identity provider instead of a password kept here, so joining and leaving stay under your control.
, SCIMSCIM
The standard your identity provider uses to create, update and switch off people's access here automatically as they join, move and leave.
, two-step verificationSecond factor
A second proof of who you are at sign-in, on top of your password — a code from an authenticator app, a text message, or an email.
Read more and field-level permissionsField-level permission
The setting that decides which roles can read each field on an employee record, such as current pay or the performance rating. What someone may see and change about themselves is set separately.
;
moving a cycle to its next phase, finalizingFinalize
Closing a cycle for good, once every worksheet is approved and every funding pool is within budget. A finalized cycle is read-only and can never be reopened.
Read more it, or cancelling it;
reading the audit trailAudit trail
The record of who did what and when, with the before and after of every change. Entries are added and never edited or deleted.
;
your own profile and sign-in settings.
A change a client makes is on the audit trail under your name, like a change you make yourself, and connecting, reconnecting and revoking a client are each recorded too. See How AI activity appears on the audit trail .
A connection lasts 90 days. After that the client asks you to sign in and choose its scopes again. You can revoke a connection at any time; see Reviewing and revoking a connection .
