Find the unanswered questions.
“Retrieve my profile questions and follow every page. Use the documents available in this workspace to propose supported answers. Include references and flag anything you cannot resolve.”
Your AI.
Connected to context.
Bring your firm's regulatory picture into your AI workspace.
Spend less time explaining the background. More time exploring the question.
Company-scoped access. Read-only retrieval.
In pilot validation · compatible AI clients only.
How the connector works
The connector lets a compatible AI client request information from Compliance OS during a conversation. Your firm’s recorded context, profile questions and regulatory requirements become available where you already work.
Authorise a company connection
During the pilot, connection details are provided for the supported client and environment. Add the connector in your AI client, sign in through the authorised flow and connect the intended company context.
Access is bound to the authorised user, client and company. Your AI client retrieves records within that scope; asking about another firm does not grant access to it.
Access within your firm
The connector retrieves records within your authorised company scope. Use the connection controls to disconnect when access is no longer needed.
Retrieve the relevant records
When your AI client calls the connector, Compliance OS returns structured records. The client can then use those records in its response, alongside other capabilities available in that environment.
- Company context. Recorded profile facts and assessment context for the connected firm.
- Profile questions. Question wording, answer options, recorded values and items needing attention.
- Regulatory requirements. Obligations, controls and associated source references.
- Research checks. Bounded checks that help review external-source support for a draft.
Complete the retrieval.
Large results arrive in pages. Ask the client to follow every required page and state what it has not retrieved. A partial result is not a complete review.
Example requests and evidence review
Ask the AI to connect the records to the question, explain its basis and identify what still needs review. These are example requests, not generated results or guarantees.
Trace the reasoning.
“Retrieve the relevant obligations and company context. Explain the recorded applicability position, the source references and any missing facts or review conditions.”
Know what to examine.
“Retrieve the relevant control requirements. Help me identify what evidence I would need to review, separating a written policy from evidence that a control actually operated.”
Working within your AI workspace’s limits
Your AI workspace determines which files it can read and whether it can browse the web. The connector supplies regulatory context; it does not extend those capabilities. Ask the AI to flag unread material and conclusions it cannot support.
Review proposals before confirming changes
AI output is a proposal for review. Check the company, supporting material, dates and unresolved questions before accepting an answer.
Confirm profile changes through the authorised OS workflow, then refresh applicability against the intended profile version. Retrieving a question or generating an answer does not save it.
- Keep contradictions visible. A document may conflict with an existing answer or another source.
- Leave unknowns unresolved. Missing evidence should remain a question to investigate.
- Separate different conclusions. Applicability, control design and operating effectiveness require distinct consideration.
Where information is processed
Compliance OS
Supplies public regulatory sources and structured company context needed for the applicability workflow.
Your AI workspace
Holds the private documents you choose to make available there. The connector workflow does not require uploading them to Compliance OS.
You
Review the analysis, resolve unsupported proposals and confirm changes. Your client's own data settings apply to the material you share with it.
Connect your AI
Compliance OS connects to AI assistants through MCP, the Model Context Protocol. Think of it as a shared language that lets your AI request the company facts, regulatory sources and requirements it needs from the OS. Choose your platform below for setup steps and account requirements.
ChatGPT Plugins
Plans: Plus, Pro, Business and Enterprise on the web. Organisation permissions may apply.
- Open ChatGPT on the web. In Settings, open Security and login and enable Developer mode. Follow your organisation’s admin process if access is managed.
- Open ChatGPT’s Plugins page and use the plus button to create a developer-mode app with the connection details supplied for your Compliance OS account. Complete the authorised sign-in and review the available tools.
- In a conversation, choose Developer mode from the plus menu and select the app to retrieve your firm’s regulatory context.
Claude Connectors
Plans: Free, Pro, Max, Team and Enterprise support remote MCP connectors. Provider usage limits and organisation permissions apply.
- On an individual account, open Customize, then Connectors, and use the + menu to add a custom connector. On Team or Enterprise, an owner first adds it through Organisation settings, then Connectors.
- Enter the name and connection URL supplied for your Compliance OS account. Add the connector and complete the authorised sign-in.
- Enable the connector in your conversation before asking Claude to retrieve your firm’s regulatory context.
Gemini Gemini Spark
Google’s custom-app route currently requires Gemini Spark access, a personal Google Account, age 18 or over, US availability and Keep Activity enabled. It is not currently available for work or school accounts. Check Google’s current eligibility requirements before setup.
- On the Gemini website, open Settings & help, then Connected Apps. This may appear under Personal Intelligence.
- Under Custom apps for Spark, add the MCP server URL supplied for your Compliance OS account. If required, use Advanced features for the supplied OAuth configuration.
- Continue through the authorisation prompts. In Spark, use @ to select the connected app when making a request.
Coordinate the account connection details with Symmorphosis before use. This provider setup route has not yet been verified with Compliance OS.
Google setup guideCopilot Copilot Studio
Access: A Copilot Studio subscription or an eligible trial for evaluation, with the required organisation permissions. This guide is for Copilot Studio agents, not a general Copilot chat subscription. Check Microsoft’s licensing requirements.
- Open your agent’s Tools page. Choose Add a tool, New tool, then Model Context Protocol.
- Enter the server name, description and Compliance OS server URL supplied for your account. Select OAuth 2.0 and use the authentication configuration agreed with Symmorphosis.
- If a callback URL is generated, provide it to Symmorphosis for registration before completing sign-in. Create the connection, then select Add to agent.
- Use the agent’s test conversation to request your firm’s profile and inspect the retrieved records.
This provider setup route has not yet been verified with Compliance OS.
Microsoft setup guideStart with your firm’s profile
Try: “Use the Compliance OS connector to retrieve my firm’s profile. Summarise the recorded activities and identify any unanswered profile questions.”
Look for retrieved records and source references in the response. This first request checks retrieval; it does not confirm that all requirements or documents have been reviewed.
Connector questions
What is MCP, and how does the connection work?
MCP stands for Model Context Protocol. It is a standard way for AI applications to discover and use tools supplied by another service. Compliance OS exposes tools that retrieve your firm’s regulatory context. When you ask a question, your AI can call those tools and use the returned records in its response.
What happens when I sign in?
OAuth handles the authorisation: you sign in through the authorised flow and grant access to the connection. MCP handles the requests that follow. Access remains scoped to your authorised user and company. Your AI uses the retrieved context to support analysis, while you review conclusions and confirm changes through the OS.
Which AI models can I use?
The connector integrates with the AI application, rather than a fixed list of model versions. Use a model and conversation mode that your provider makes available with custom MCP tools. A paid plan alone does not establish that every model or mode can use the connector. The guides cover ChatGPT, Claude, Gemini Spark and Copilot Studio; Gemini and Copilot setup still requires verification with Compliance OS.
Does the connector change my company profile?
No. The current connector retrieves information and supports external-source research checks. It does not provide a general endpoint for saving profile answers or submitting audit findings. Use the authorised OS workflow for those changes.
Does it search the web for me?
The connector can provide regulatory records and bounded official-source evidence checks. Broader online research depends on the AI client's available browsing capabilities. Retrieving OS records alone is not a fresh web search.
What do the evidence checks establish?
They can help check whether a cited official-source passage supports the supplied quotation under the tool's bounded rules. They do not certify legal interpretation, applicability or every statement in a client's final answer.
Do I need to fine-tune an AI model?
No custom model training is required by this approach. The connector supplies maintained context to a compatible client. Clear questions, complete retrieval and professional review still matter.
Can I connect every AI client?
Compatibility is being validated through the pilot. Clients differ in connector support, browsing and document handling. Supported connection instructions will be provided for the pilot environment.
Can I stop the connection?
Yes. Use the authorised connection controls to disconnect. Revocation prevents further authorised retrieval through that connection; it does not erase material already retrieved into your AI client's conversation.
Trying the connector in the pilot
The pilot is being used to validate supported AI clients, complete record retrieval and document-supported proposals. Connection details will be provided for the supported environment.
Public enquiries will open soon.