Claude Relativity connectorWhat Claude can do in your Relativity account.

Confirms that Claude is connected to Relativity and shows which instance and which identity the session is bound to: instance URL, tenant ID, sign-in method and your user.

Pulls every client in the instance, page by page, with name, number, status and creation date. Relativity's own example request is simply to show all clients in your environment.

Returns the matters in the instance with their name, number, status, parent client and creation date. You can ask for the ones under a single client.

Shows the people in the instance along with their email, client, user type and access details. The results come back as a paginated list, and Relativity's table attaches no confirmation to this lookup.

Brings back the user groups that exist in the tenant, with client, status and creation date. Groups are how Relativity hands out workspace access.

Lists the templates you can build a new workspace from, with their client, matter, status and use case. Relativity's example asks which templates can serve a new matter.

Tells you which security groups one person belongs to, looked up by their email. Relativity's example looks a person up by email address, and the answer is a paginated list.

Goes the other way round: given a security group, it returns its members with their ID, full name and email, as a paginated list.

Returns workspaces with their client, matter, status, use case and state. It's also how you check whether a long workspace build actually finished, by searching for its name. Results come back page by page.

Opens the full record of one workspace: name, status, its matter and client hierarchy, and timestamps, all in one answer.

Checks how far an ongoing workspace creation has got, with its state, progress steps and the new workspace's ID once it's done.

Holds until a workspace creation job finishes or fails, then reports the final state and the workspace ID. Relativity's example: wait until the new workspace is fully provisioned, then report back.

Shows which user groups currently have access to a given workspace, as a paginated list of security groups you can read through in the chat.

Lists all object types defined inside a workspace, with their name and type ID. Claude learns what kinds of records a workspace holds.

Retrieves the fields defined on one object type, with name, field type and object type ID, page by page.

Returns the options available on a single-choice or multi-choice field, each with its name and display order, page by page if the list is long.

Describes the metric and origin fields you can build a usage report on, listing every one of them so Claude knows what's measurable before any report gets requested.

Lists the usage reports already existing for the tenant. No confirmation applies to it in Relativity's table, since it only reads what already exists. Its answer covers the whole tenant.

Fetches one usage report's metadata and status: ID, name, type, date range and selected fields. It's a quick check, without opening the data inside.

Reads the row-level data inside a usage report, as paginated table data with column headers. The rows arrive page by page, and Relativity's table lists no confirmation for reading them.

Hands back a completed usage report as a CSV string, ready to paste or save. Relativity's example asks for the Q1 storage report as a CSV, and only a completed report can be downloaded.

Blocks until a usage report finishes generating and then returns its completed metadata. Relativity's own example chains it with the download: wait for the Q1 report to finish, then fetch it.