The workflow

Watch this workflow run through Kroy.

  1. The request.

    “Microsoft Entra ID”

  2. Who is asking.

    Kroy identifies the person in people and it and Microsoft Copilot acting for them, within the delegation they gave it.

  3. Only what the task needs.

    Kroy retrieves staff handbook, HR policies and IT guides (SharePoint) and the employee’s own role, office and team (Microsoft Entra ID) from SharePoint and Microsoft Entra ID.

  4. Excluded by design.

    HR case files, Salary bands and pay reviews and Sites the employee cannot access in SharePoint never reach Microsoft Copilot. That boundary is Kroy’s, not an instruction to the AI.

  5. The proposed action.

    Permitted: search and read permitted policy content (sharepoint.search, sharepoint.file.read) and raise a request to HR or IT (request.create).

  6. What Kroy refuses.

    Refused: read HR case files or salary data, edit policy documents and read content the employee cannot access.

  7. State changes. Everything is recorded.

    The work is updated in Kroy, and every request — allowed or refused — is written to the audit trail.

Microsoft Copilot
People and IT
Kroy
SharePoint
Microsoft Entra ID
Search and read permitted p…
Read HR case files or sal…
AUDIT · STATE

Retrieved

  • Staff handbook, HR policies and IT guid…
  • The employee’s own role, office and tea…

Excluded

  • HR case files
  • Salary bands and pay reviews
  • Sites the employee cannot access in Sha…
Microsoft Copilot
People and IT
Kroy
SharePoint
Microsoft Entra ID
Search and read permitted p…
Read HR case files or sal…
AUDIT · STATE

Retrieved

  • Staff handbook, HR policies and IT guid…
  • The employee’s own role, office and tea…

Excluded

  • HR case files
  • Salary bands and pay reviews
  • Sites the employee cannot access in Sha…
Employee self-service from SharePoint with AI: the workflow through Kroy. The request.. Who is asking.. Only what the task needs.. Excluded by design.. The proposed action.. What Kroy refuses.. State changes. Everything is recorded..

What the AI can and cannot do

Data accessed

  • Staff handbook, HR policies and IT guides (SharePoint)
  • The employee’s own role, office and team (Microsoft Entra ID)

Data excluded

  • HR case files
  • Salary bands and pay reviews
  • Sites the employee cannot access in SharePoint

Actions permitted

  • Search and read permitted policy content (sharepoint.search, sharepoint.file.read)
  • Raise a request to HR or IT (request.create)

Actions refused

  • Read HR case files or salary data
  • Edit policy documents
  • Read content the employee cannot access

Business situation

ABC Limited, a professional services firm, keeps its staff handbook, HR policies and IT guides in SharePoint. People ask HR and IT the same questions repeatedly: how much leave they have left under the policy, how to claim an expense, how to set up a new laptop. Some staff use Copilot, others ChatGPT.

Why existing tools alone are insufficient

A general AI does not know the firm’s policies. Uploading the handbook to each AI tool creates copies that go out of date. Connecting an AI broadly to SharePoint risks returning content that happens to be over-shared — such as a pay review spreadsheet in the wrong folder — to anyone who asks.

Systems involved

  • SharePoint — the handbook, HR policies and IT guides.
  • Microsoft Entra ID — who each employee is, their role, office and team.
  • KroyDB — HR and IT requests.

Kroy architecture

Copilot and ChatGPT connect to Kroy. Microsoft 365 and Entra ID are connected to Kroy by IT. The Answer Policy Question Skill may search and read the designated policy sites, as the signed-in employee. The Raise HR or IT Request Skill may create a request. HR case files and salary data are classified confidential and excluded from both Skills.

Workflow

  1. An employee asks Copilot: “What’s our policy on working from abroad?”
  2. Kroy checks the employee’s identity through Entra ID, the agent and the Skill, then searches the policy sites with sharepoint.search and reads the relevant page with sharepoint.file.read.
  3. Copilot answers from the current policy and links to it.
  4. The employee asks: “What’s the salary band for a senior manager?” Kroy refuses: salary data is outside the Skill.
  5. Another employee asks ChatGPT: “How do I get a second monitor?” Kroy returns the IT guide. ChatGPT explains the process.
  6. The employee asks: “Raise that request for me.” ChatGPT requests request.create. Kroy creates an IT request linked to the employee.

Agent permissions

Each AI acts under the signed-in employee’s delegation and sees only what that employee can already read, within the policy sites. It can raise requests, but not edit policies.

Human permissions

Employees can read the policies SharePoint already lets them read. HR and IT own the policy sites and handle requests.

State changes

  • An IT request is created, linked to the employee.
  • Nothing in SharePoint changes.

Audit outcome

Kroy records each question’s sources, the refused salary request and the request raised — with the employee, the agent and the policy.

Security considerations

  • Answers come from the live policy, so there are no stale copies in AI tools.
  • Confidential classifications are enforced by Kroy, even where SharePoint permissions have drifted.
  • Microsoft 365 credentials stay in Kroy.

Setup requirements

  • Microsoft 365 and Microsoft Entra ID connected to Kroy.
  • Policy sites designated and confidential content classified.
  • Copilot and ChatGPT connected to Kroy.
  • Both Skills enabled for all staff.

Try this with your own systems.

Try Kroy with Microsoft 365