Connect Claude to your business software, and let it do the work as you

Orbiz gives a connected assistant 81 actions across 9 of its tools, plus a handful that belong to no single tool: who you are in Orbiz, finding a colleague by name, and searching and fetching content. In practice that means Claude can do the following, when your role allows it:

• In Cadence: report a bug, create, update, move and close issues, comment, and create, start and complete sprints.
• In Trackline: create and update projects and milestones, log hours and total them.
• In AMS: read your day, timesheet and leave balance, request leave, and decide your team’s requests if you approve leave.
• In HRMS: list your HR tasks, jobs and candidates, complete a task step, add a candidate and move one on.
• In Ledgr: read your own pay summary and payslips; payroll managers can propose a salary revision.
• In Notely, Filespace and Grabr: notes and checklists, files and folders, and your recordings with their share links.

Each tool’s page says exactly what an assistant can reach there and what it cannot. The fuller write-ups are the pages on the HR MCP server, the payroll MCP server, the time tracking MCP server and the project management MCP server.

Custom connectors are part of Claude itself, not something Orbiz installs. Claude’s own help pages list them for the Free, Pro, Max, Team and Enterprise plans, with the Free plan limited to a single custom connector. On Pro and Max you add the connector yourself. On Team and Enterprise an Owner adds it for the organisation once, and after that every member connects individually, which is what keeps each person’s Claude limited to what that person can reach in Orbiz.

Orbiz is added as a custom connector, by address. It is not a listing in Claude’s connector directory, and Claude’s help pages say of every custom connector that it is a service Anthropic has not verified. The check that matters here is your own: the address comes from inside your Orbiz organisation, and the approval page is Orbiz’s.

Claude Code is the assistant developers run beside their repository, and it connects to Orbiz too. The difference is where it runs: on your own machine, signing in through your browser. Orbiz gives you a ready-made setup line for it on the same Settings screen as the address; you run that line once and approve in the browser window that opens.

Because a local app is asking, the Orbiz approval page adds a warning it does not show for the hosted Claude apps: only approve if you started it. Once connected, the natural uses are in Cadence: report the bug you just reproduced, with the error still in the conversation, and close the issue with a comment when the fix ships.

The approval page names Claude, your organisation and your account, and lists access tool by tool with reading and changing as separate ticks. You can untick anything before you approve, and it only offers what your role could already do. Changing pay is its own tick with its own warning. A sensible first connection is read-only: see how Claude answers questions about your work, then reconnect with changes.

Afterwards, Settings → Connected AI apps lists your connections and every action taken through them, with the outcome and the time. Admins see the same for the whole organisation, can disconnect any connection, and can switch AI assistants off for everyone with one control. The platform’s wider safeguards are on the security page.