The setup, before the first build
01 · Environments
Nothing goes straight into production. We build in a sandbox, test separately and move to production as a managed solution, so you always know which version runs where.
02 · Access
Skills, plugins and connectors are rolled out per team or role through security groups. Existing SharePoint permissions remain in charge: through a skill, a user never sees more than they were already allowed to see.
03 · Connectors
Only approved sources, within your DLP policies. Custom connectors we build per source, with the permissions that source needs and no more. External tools stay out. If you work with Claude, we configure the skills correctly and agree together which connectors may be linked and which may not.
04 · Administration
Every step can be traced in the audit log. Delivery includes a handover document, a maintenance guide for IT and an evaluation set, so your team can manage it themselves.
Built on Microsoft 365 · Copilot Studio · Power Automate · Claude
What we do not do
- No extra platform. We build on what you already have: Microsoft 365, Copilot Studio and Power Automate, or Claude.
- No connectors you did not approve. In Microsoft 365 they follow your DLP policies. With Claude we configure the skills correctly and agree together which connectors may be linked and which may not.
- No permissions you did not already grant. A skill sees what the user was already allowed to see, no more.
- No dependence on us. Handover to your IT is part of delivery, not of an SLA.
What it looked like
At a healthcare software company we built a documentation agent across seven knowledge sources: a security group for access, existing SharePoint permissions respected, built in a sandbox and moved to production as a managed solution, an evaluation set of 70 questions, handover to the internal administrator.
A version to forward internally (PDF) is coming soon. Want to discuss this with your IT team now? Book 30 minutes