Skip to content

Platform · Layer 2 of 3

Permission LayerYour org chart becomes rights.

Every person and every AI agent sees only what they may see. The rights come from your org chart, and demi never widens them on its own.

The problem

AI may do too much to be safe. Or knows too little to be useful.

An assistant with full access shows the trainee the salary list. One without access does not even know the data sheet. Either way, AI stays out of the real work.

What research and practice say

Agents need rights before they act.

Our own analysis

In demi's analysis of 196 use cases

  • 83%

    163 of 196 work with data that only certain roles may see, and 43 of 196 with strictly confidential data such as personnel, contracts and margins.

Method and all sources

How it works

From the org chart to AI with your rights.

  1. Step 1 / 6

    Your org chart, your roles.

    demi maps how your company is built: departments, teams and who has which role. The rights follow from these relationships and inherit along the org chart.

    Management
    Engineering
    Sales
    HR
    Agent for Jonas
    Inside salesJonas
    Key accounts
  2. Step 2 / 6

    Rights by role. Never widened on their own.

    Department, team, role: what your org chart sets applies in demi, and demi never widens it on its own. Private documents stay private.

    Management
    Engineering
    Sales
    HR
    Agent for Jonas
    Inside salesJonas
    Key accounts

    Jonas in the org chart

    1. DepartmentSales
    2. TeamInside sales
    3. RoleClerk
    4. Jonas

    Rights inherit along this path

  3. Step 3 / 6

    Every query checks every record.

    When Jonas from inside sales asks about a gear motor, demi checks for every single document whether he may open it. If someone can't open a file today, they won't see it in demi either.

    Management
    Engineering
    Sales
    HR
    Agent for Jonas
    Inside salesJonas
    Key accounts

    Jonas' rights

    Never widened on their own
    • Data sheets
    • Quotes and orders
    • Key account termsno access
    • Personnel filesno access
  4. Step 4 / 6

    The AI has the rights of the person who asks.

    An AI agent never has more rights than the person it works for. demi checks every right on the server, not in the AI model. So the AI cannot get around the check.

    Management
    Engineering
    Sales
    HR
    Agent for Jonas
    Inside salesJonas
    Key accounts

    May the GM-2040 run at 50 °C?

    • Data sheet GM-2040, rev. C
    • Terms Stadtwerke Nord
    • Operating manual GM-2040
    • Personnel file M. Berger

    2 of 4 visible

  5. Step 5 / 6

    Sign-offs: who approves what.

    If an agent has read content that may carry instructions from third parties, every send, publish or share to the outside needs a person's click, here inside sales for the answer to the customer. Deleting is blocked for agents.

    Management
    Engineering
    Sales
    HR
    Agent for Jonas
    Inside salesJonas
    Key accounts
    Jonas
    =
    His agent

    never more rights

    Key account termsno access
  6. Step 6 / 6

    Traceable: who saw and approved what.

    The log names person, agent and time, for every request and every sign-off. It is protected against change and deletion.

    Management
    Engineering
    Sales
    HR
    Agent for Jonas
    Inside salesJonas
    Key accounts
    • Deletingblocked for agents
    Waiting for sign-offApproved by JonasEmail

    Answer to the customer: GM-2040 runs at 50 °C (IP65, −20 to +60 °C)

    ApproveEdit

    Sent to the customer

What you get

AI that can only do what you can.

  • Never more

    rights for the agent than for the person

    An AI agent never has more rights than the person it works for. Checked on the server, not in the AI model.

  • Every

    request checked, record by record

    For every request, demi checks document by document whether the person may open it. If someone can't open a file today, they won't see it in demi either.

  • 0

    possible edits to the log

    The log names person, agent and time, for every request and every sign-off. It is protected against change and deletion.

One case

Answer technical customer questions with sources

Today

Inside sales answers the same technical questions day after day and forwards every second one to engineering. The answers differ depending on who replies.

In the Permission Layer

The agent answers each person only from documents they may see, and customer-specific prices stay with the account owner. Inside sales reviews and approves every answer that goes out, and this is recorded.

What it brings

  • Inside sales answers without waiting for engineering
  • Consistent answers across the team
  • Engineering gets fewer routine questions
See the whole case

The three layers

Data first. Then rights. Then AI. For each use case.

The whole platform
  1. Layer 3Intelligence LayerAI, traceable
  2. You are hereLayer 2Permission LayerOrg chart as rights
  3. Layer 1Data LayerYour data, connected

FAQ

What IT, data protection and the works council want to know

  • Can the AI see or change what a person may not?

    No. An AI agent never has more rights than the person it works for. If an agent has read content that may carry instructions from third parties, every send, publish or share to the outside needs a person's click. demi checks every right on the server, not in the AI model. Each company sits in its own tenant, deleting is blocked for agents, and a log names the person, the agent and the time.

  • Where do the rights come from?

    From your org chart: departments, teams and roles. demi never widens rights on its own, and private documents stay private. That holds for people and their agents.

  • When does an agent need a person's click?

    If an agent has read content that may carry instructions from third parties, every send, publish or share to the outside needs a person's click. Deleting is blocked for agents, and actions by external AI clients need their own sign-off.

  • Who may see the log?

    The log names person, agent and time and is protected against change and deletion. It is there to trace what happened, not to monitor performance. Your company decides who may see it, for example in a works agreement.

Next · Layer 3 of 3

Intelligence Layer

AI that calculates instead of guessing.

On to the Intelligence Layer

On your case

See your org chart as rights.

In 20 minutes we show you the Permission Layer on a case from your industry, such as a technical customer question: who may see the answer, and why.

Your configurator

No use cases yet

Your configurator is still empty

Add a use case from any card or case page and see what it brings per year, with the calculation. Free, no sign-up, no commitment: try it out and change any number.

Browse use cases