OAO Insight

OAO Insight connects your organisation's AI assistant (such as Claude, ChatGPT, Microsoft Copilot Studio or Langdock) to OAO. Ask it about a topic, and OAO answers from your organisation's OAO workshops: what your people raised there, which workshops and dashboards fit, and how to request a new workshop.

Each person signs in with their own Microsoft work account. That sign-in decides which organisation's OAO they reach.

Sign in to see whether your organisation is connected, or to ask us for it.

Sign in with Microsoft

With a work account you see your organisation's status. With a personal Microsoft account you can send us a note.

Add OAO Insight to your AI assistant

OAO Insight is your gate to Lyman, OAO's agent in your organisation's OAO workshops and dashboards. It is for people at organisations that work with OAO. Your organisation needs to be connected to OAO, and your organisation and OAO decide together who uses it. Add it to your AI assistant as below. When your tool asks you to sign in, use your Microsoft work account, not a personal one.

Claude

  1. Free, Pro and Max: go to Customize → Connectors, find OAO Insight in the directory and connect.
  2. Team and Enterprise: an Owner adds OAO Insight for the organisation, in Organization settings → Connectors or with 'Connect for your team' on its directory page. Members then connect under Customize → Connectors. On Team, members can ask an Owner for it with the Request button.
  3. In the connector's tool settings, keep Ask OAO, OAO next steps and Propose an OAO workshop on Needs approval.
  4. Already added OAO Insight by hand? That connector keeps working. To use the directory entry instead, the Owner removes it and adds it from the directory.
  5. When Claude asks you to sign in, pick your Microsoft work account in Microsoft's account picker.

ChatGPT

  1. A workspace admin adds OAO Insight as a custom app, with the server address https://mcp.oao.co/mcp, OAuth, and the client ID and secret OAO sends.
  2. If ChatGPT shows a callback address of your own workspace, the admin sends it to OAO and keeps the draft open. OAO then registers a client for your organisation and sends its ID and secret.
  3. The admin sets approval to Always ask. If ChatGPT lets you exempt OAO card text alone, it may run without asking.
  4. Each person finds OAO Insight among the workspace's apps and connects.
  5. When ChatGPT asks you to sign in, pick your Microsoft work account in Microsoft's account picker.

Microsoft Copilot Studio

  1. The agent's maker adds OAO Insight to the agent as a new tool with OAuth 2.0. They use the server address https://mcp.oao.co/mcp and the values OAO registers for your organisation.
  2. Keep authentication on End user, so each person signs in with their own account. With Maker-provided, everyone using the agent gets the answers OAO would give the maker.
  3. After Create, the maker sends OAO the redirect URL Copilot Studio shows. It works once OAO confirms.
  4. The maker sets the tool to Ask the end user. If Copilot Studio lets you exempt OAO card text alone, it may run without asking.
  5. Each person uses the agent and signs in with their Microsoft work account when asked.

Langdock

  1. An Editor or Admin of your workspace adds OAO Insight under Integrations → Add integration → Start from scratch → Connect remote MCP, with OAuth 2.0 Manual. They enter the server address https://mcp.oao.co/mcp and the values OAO registers for your organisation: client ID, secret, authorization URL, token URL and scopes.
  2. After Create, Langdock shows a callback URL. Send it to OAO. Connect works once OAO confirms.
  3. Turn on per-tool confirmation for Ask OAO, OAO next steps and Propose an OAO workshop. If Langdock lists OAO card text, it may run without confirmation.
  4. Keep connections personal. If an agent uses a preselected connection, everyone using that agent gets the answers OAO would give the connection's owner.
  5. Each person connects and signs in with their Microsoft work account.

What it does and doesn't do

If it doesn't work

For IT admins. Once per organisation: (1) A Microsoft admin who can grant tenant-wide consent approves 'OAO Insight' for your organisation. If your organisation isn't connected yet, signing in on this page shows a 'Give admin consent' button; your OAO contact can also send the link. OAO's page then shows your tenant ID to send us. (2) Send your OAO contact that tenant ID and your company's mail domain. OAO checks it and connects your Microsoft organisation to your company. (3) OAO lets in the people it knows at your company: the people from your OAO workshops and access grants. Tell your OAO contact who is missing. The email address Microsoft has for a person must be the one OAO has. Once per AI tool: OAO sends whoever sets up the tool the client ID and secret, through a separate channel. That person doesn't need to be known to OAO. Approval: the three question tools are Ask OAO (oao_ask), OAO next steps (oao_next_steps) and Propose an OAO workshop (oao_propose_workshop). Approval stays on for them wherever your tool offers it, so each person sees and approves what goes to OAO: a short topic. OAO card text (oao_card_text) is the card's own call. It sends only an answer ID, and it may run without approval where your tool allows that for a single tool. What you can control: in Microsoft Entra, your admin can set 'Assignment required' on the 'OAO Insight' enterprise application and assign only the people who may use it. Removing the connector stops it in that tool's organisation. To stop it everywhere, set Assignment required in Entra, or ask your OAO contact to switch OAO Insight off for your company. Personal Microsoft accounts don't work.