An artifact is published.
An agent can use information from a local file to create an artifact that is then published or shared.
Review available artifact publication and sharing events.Check Claude and ChatGPT conversations against your policies. Find sensitive information, flag risky requests and focus review where it matters.
Book a demoYour conversations → Your rules → Findings to review
Start with a curated pack. Tailor the rules to your firm. Review each match in context.
Identify customer details, confidential code and restricted projects in connected conversations.
Apply regulatory and internal rule packs. Review the message, the person and the reason it was flagged.
Prioritise by severity. Acknowledge, resolve or reopen each finding as the review progresses.
Keep findings linked to the person, source and rule. Each run records the review period, policies and coverage — so you can explain what was checked and what action followed.
Walk through a review ↗The record keeps findings, reasons and source metadata. Raw message text is not retained in the activity record.
AI can read permitted files, reuse them in an output and pass information to other tools. Review the available sharing events alongside the conversation.
An agent can use information from a local file to create an artifact that is then published or shared.
Review available artifact publication and sharing events.Files and working context brought into a project can become accessible to others when project access changes.
Review project sharing and external-access signals.A custom GPT can draw on uploaded knowledge. Its sharing settings and connected actions change who or what it can reach.
Inspect available GPT sharing state and recipients.An agent with file access can pass information to an external service through an MCP-connected tool, where its permissions allow it.
Discover configured MCP servers; review tool activity where available.Coverage depends on the source and permissions. A configured connection shows access; an observed event shows activity.
Report on the work people use AI for. Identify where training, policy or closer oversight is needed.
Group conversations by task, team or audience. See where AI is being used and where support or closer review is needed.
Choose a category to see how the report changes.
Select a dimension to regroup the report.Draft a customer email explaining the new savings account features.
DraftingAnalyse these policy changes and identify the review steps our team needs to update.
AnalysisDraft an internal handover note explaining how our deployment workflow works.
Drafting| Task | Conversations |
|---|---|
| Drafting | 2 |
| Analysis | 1 |
| Research | 0 |
| Conversations in this view | 3 |
Use recurring tasks and team patterns to target training, prioritise useful AI applications and focus oversight.
Reports cover the conversations available through your selected sources. Usage tags describe the work; compliance findings record a separate concern.
Find supported AI tools, skills and MCP servers on laptops, with the person and application they belong to.
Discuss a laptop scanFind supported applications and their local skill and MCP configuration, including recognised project locations.
Review usage evidence where the application records it. An installed skill or connection is not proof it was used.
Use the inventory to decide which tools, connections and capabilities need investigation or an agreed policy.
Connect custom data sources to apply the same rules beyond Claude and ChatGPT.
Connor connects to available Claude and ChatGPT compliance data, checks conversations against your rulebooks and raises findings linked to the user, source and matched rule. Reviewers can acknowledge or resolve findings and keep a decision record.
Connor can flag content that matches rules for personal data, confidential information or restricted projects. Coverage depends on the activity made available by the connected provider and the rules you apply.
Yes. The EU AI Act pack is one of the rulebooks you can apply to available conversations. A flagged request provides a reason to investigate; it does not by itself establish that a prohibited use occurred.
No. A laptop scan can identify installed tools, skills and MCP connections. An installed connection shows what is configured; evidence of use or sharing requires an observed activity event.
Walk through a conversation review, the matched rules and the record of each decision.
Book a demo Your content. Your rules. A clear next step.