Connect Tiercord to Claude, ChatGPT or Microsoft Copilot

Before you start

An owner or admin has to turn AI assistant access on for your company, in Settings, then Integrations, then AI assistants. A current eligible subscription and the company's sign-in requirements also apply. Until the switch is on, nobody can connect an assistant.

Once it is on, each person who connects chooses their own scope on the approval screen: every project they can already see, which is the default, or only the projects they pick from a list. The choice applies to that one connection and is recorded on it. An assistant never sees a project the person connecting could not already open in Tiercord.

If you belong to several eligible companies, choose the company first. Its current project list appears on the same approval screen, and changing company clears any project choices from the previous company.

Check your project contracts, confidentiality obligations and applicable data-location requirements before connecting. If a project restricts disclosure to an assistant provider, resolve that restriction before granting access, because the default scope includes all projects the connecting person can see.

Connecting Claude

1. In Claude, open Customize, then Connectors, then +, then Add custom connector.
2. Paste the connector address shown in Tiercord under Settings, Integrations, AI assistants. It looks like https://tiercord.ca/api/mcp.
3. Click Connect. A Tiercord tab opens.
4. Sign in to Tiercord if you are not already signed in.
5. Read the approval screen, choose your company, and click Allow read access.

Available on Claude Pro, Max, Team and Enterprise. On the Free plan you can hold one custom connector at a time. For Team or Enterprise, an Owner first adds it under Organization settings, Connectors, Add, Custom, Web; members then connect individually. Current Claude instructions.

Connecting ChatGPT

1. In ChatGPT on the web, open Settings, then Security and login, and turn on Developer mode.
2. Open Plugins, select +, and paste the same connector address for the new MCP server.
3. Choose OAuth. Use dynamic client registration if asked; no manual client ID or secret is needed.
4. Approve the connection on the Tiercord screen that opens.
5. In a chat, open +, choose Developer mode, and select Tiercord.

OpenAI currently lists Plus, Pro, Business, Enterprise and Education accounts for developer mode on the web. Workspace policies can limit availability. Check your plan and administrator permissions if the option is missing. Current OpenAI instructions.

Connecting Microsoft Copilot

These instructions connect Tiercord through a Copilot Studio agent.

1. In Copilot Studio, open your agent, go to Tools, then Add a tool, then New tool.
2. Choose Model Context Protocol and paste the same connector address as the server URL.
3. Set authentication to OAuth 2.0 with dynamic discovery, then Create.
4. Create a new connection and approve it on the Tiercord screen that opens.
5. Before sharing the agent, choose User authentication for the tool and check that your publishing channel supports it.

Copilot Studio requires an eligible license; its trial supports testing, not publishing. If you share an agent that uses your connected credentials, other people using it may receive records within your authorized scope. For shared Copilot agents, choose User authentication so each person connects their own Tiercord account. Power Platform data policies can restrict the connection. Microsoft setup instructions, authentication and supported channels, and licensing.

What an assistant can read

• The projects chosen when the connection was approved, and the contracts and payment terms on them
• Invoices, amounts, status and holdback, and the payments recorded against them
• Holdback positions and release dates
• Statutory deadlines, each one carrying the statute, section and day count Tiercord computed it from
• Notices of non payment as facts: form, amounts, dates and delivery
• Your directory of the companies you work with: legal name, city and province, payment terms, how many contracts you have with each and how much is open. Their names also travel with the projects, invoices and holdbacks above.

What travels with the answers

Alongside the records themselves, Tiercord includes two things in what it sends back. First, links to Tiercord's published guides and articles for the provinces and topics the answer touches, with a request that the assistant review the relevant page before explaining how the law works and share the link with you, so an answer about Ontario holdback draws on the guide Tiercord wrote about Ontario holdback.

Second, Tiercord's own computed analysis where one exists: the statutory position of an invoice, with every remedy window, its citation and the basis it was computed from, exactly as the invoice page in Tiercord shows it. That analysis is labelled as Tiercord's reading, and assistants are asked to attribute it that way, in words like what Tiercord thinks, rather than presenting it as their own conclusion. It is computed information, not legal advice.

What it can never do

• Change, create, send or delete anything at all
• Issue a notice, send an invoice, refer an adjudication or record a payment
• Open or download a document, or read the text Tiercord extracted from one
• Read the written reasons or notes recorded on notices, payments, counterparties or disputes
• See your connected accounting or email credentials
• See a project outside the scope recorded on the connection, or any other company's data

The last two are enforced inside Tiercord's database rather than by the assistant, so they hold even if an assistant is asked to ignore them.

Where your data goes, and what we cannot promise

When your assistant requests records within the connection's authorized scope, Tiercord sends the answer to that assistant. The assistant's provider and its service providers may store or process the information outside Canada, including in the United States. Locations and safeguards depend on the provider, product, agreement and account settings. Courts and government authorities in those countries may be able to require access.

Storage location, model inference location and connected-service processing can have different controls and exceptions. Review the settings and agreement for the product you use before sending records with location restrictions. See Anthropic's commercial processing locations, OpenAI's cloud security and residency guidance, and Copilot Studio data locations and exceptions.

Once information is inside a Claude, ChatGPT or Copilot conversation, what happens to it is governed by your own settings and agreement with that provider, not by Tiercord. That includes how long it is kept, who else in your assistant workspace can see it, and whether it can be exported. Enable only the connectors you actually need in the same assistant, and review your provider's retention settings.

Tiercord is not a law firm and an assistant's answer is not legal advice. Confirm anything you intend to rely on against the record in Tiercord and with your own counsel.

Disconnecting

Removing the connector in Claude, ChatGPT or Copilot stops that assistant using it. Disconnecting in Tiercord, under Settings, Integrations, AI assistants, is what actually revokes the access, and it takes effect immediately. Do both.

Neither action recalls information that has already been sent. That is worth knowing before you connect rather than after.

What is recorded

Tiercord confirms an audit entry for an authorized read request before reading records. It then confirms a second entry for the prepared response before returning workspace information. This records the operation, time, evidence-row count and a limited list of related record identifiers. Evidence counts include supporting rows and pagination checks, so they can exceed the records shown in the response. If either entry cannot be confirmed, Tiercord does not return workspace information. A prepared-response entry does not prove network delivery or that anyone read the answer.

Your Activity history page lists connections and recorded refusals, rather than every individual read request. The request and result entries remain in the sealed record and its entry count. Workspace audit exports include them; an adjudication bundle includes the audit evidence its authorized scope covers.