Skip to content
Back office: finance, HR, legalFor every industry

Who may do what? Access rights at a glance

demi shows who can access what, finds excess rights and checks every access request against the org chart.

Today

Rights grow over the years: people change roles and keep their old access. Nobody can say for sure who may see salaries, prices or drawings. The annual access review is a spreadsheet nobody wants to fill in.

An example

At Talwerk Antriebstechnik the quarterly review shows 14 people with access to the folder HR/Salaries 2026. Five of them have since changed roles, and a former student worker can still open the customer price list for geared motors. The head of HR revokes 5 rights in two clicks, and the head of sales revokes the sixth.
Fictional company, typical workflow.

Your data, wherever it lives

Who may access what is spread across many places today: accounts and groups in the directory, roles in the ERP, folder rights on the drives, permissions in the DMS, the org chart in the HR system, new requests in tickets and e-mails. demi reads, understands and links them per person across these systems, with your rights. The AI prepares the access review for each owner and checks every new request against role and department at once; only the person who owns the data confirms or revokes access.

Where the data lives today

  • ERP
  • Folders & drives
  • DMS & archive
  • HR system
  • Tickets
  • E-mails
Data LayerOne view of everything, with your rights

How demi solves it

Three layers in this order: connect the data first, then the rights, then the AI.

  1. 1 · ConnectData Layer

    The case needs data from the directory, ERP, file share and DMS. demi replaces nothing and builds, per person, one view of their actual rights across these sources. demi writes back only after approval.

  2. 2 · PermitPermission Layer

    This is the Permission Layer itself: rights mirror the org chart. The data owner confirms or removes rights and approves requests, and every change is recorded.

  3. 3 · ActIntelligence Layer

    The agent works with effective rights exactly, including groups and inheritance, and checks them and new requests by fixed rules against role and department. It prepares the periodic access review for each owner.

How it runs

  1. 1

    demi evaluates users, groups and rights from your data.

  2. 2

    Rights are compared with role and department from the org chart.

  3. 3

    Unusual rights go to the data owners, with the reason.

  4. 4

    They confirm or revoke; demi applies the change and records it.

  5. 5

    New requests are checked against role and rules right away.

What changes

  • Oversharing found and fixed

  • Access reviews you can prove at any time

  • A safe basis for AI on company data

What does it bring you?

Check it with your own numbers

Every starting value is an assumption you can change. The calculation sits right below, step by step.

Assumption, editable

Your numbers

Result

+128 hfreed per year

Assumptions and calculation

demi checks each request against the role and finds excess rights; you decide on access.

20 min → 12 min per case

How does it run today?

What is already digital saves less: the factor lowers the share demi brings.

How we calculate

80 access requests × 20 min × 40% × 1.0 (manual) × 12 months = 7,680 min = 128 h

Value per year, before demi costs

Freed per year+128 h

Assumption: labour cost of €49.50 per hour in German manufacturing in 2025 (Destatis), plus workplace, IT and overheads.

= Value per year, before demi costs

+€8,320

gained per year

128 h ÷ 1,760 h per role = 0.1 full-time roles

An estimate, not a promise. The starting values are assumptions for an industrial company with 150 to 500 people.

Combine with more cases and get the package

Questions about this use case

Where do the rights that demi evaluates live?

Rights live in your directory, ERP, file share and DMS. demi evaluates effective rights, including those that come from groups and inherited folder permissions. How the data from these sources reaches demi, we clarify in a conversation. Nothing is assumed: every entry shows the system it came from.

Does demi change rights automatically?

No. demi proposes, the data owners decide. demi writes back only after approval or opens a ticket for IT. Every change is recorded with person, time and reason.

What does this have to do with AI on company data?

An AI agent in demi only works with the rights of the person it works for. If those rights are too broad, the AI also finds what that person should never see. Clean rights are the precondition for using AI widely in the company.

Does this help with internal and external audits?

Yes, as evidence. Every review is documented with its result, the person who confirmed it and the date, and every change can be traced. Which audit requirements apply to you is for your internal audit and your auditors to judge.

See this case with your data

In the demo we show you the workflow on your own systems.

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