Today
Anyone who needs another team's documents files a ticket with IT. IT does not know who owns the folder and asks around, and three days later someone has full access to the whole project drive instead of read access to four drawings. The time limit existed only in the ticket: the right stays until the next access review finds it.
An example
At Norvelta a customer reports damage to the slide of an 8-cavity mold made of 1.2343. The toolmaker in maintenance writes: “I need the drawings and the 3D model of the slide of mold SW-2207.” demi finds the mold record in the PLM and the project folder in cloud storage and asks the project manager to approve read access to 6 files for 10 days, without the costing or the customer correspondence. She approves after 3 minutes, and on day eleven demi removes the right on its own.
Your data, wherever it lives
Today the documents sit in project folders on the file share, in SharePoint libraries, in the DMS and in the PLM, the rights live in directory groups, and anyone who needs something files a ticket or asks around in the chat. demi reads, understands and links locations, content, owners and rights, and respects those rights throughout. The AI finds in seconds where something is and who may release it, proposes the smallest fitting right, and the owner decides with one click.
Where the data lives today
- SharePoint
- DMS & archive
- PLM
- Folders & drives
- Chats
How demi solves it
Three layers in this order: connect the data first, then the rights, then the AI.
- 1 · ConnectData Layer
This case needs data from the directory, file shares, cloud storage, DMS, PLM and chat. demi replaces nothing and knows the content, the owner and the effective rights of every folder, library and document. A sentence like “the drawings for mold SW-2207” becomes an exact location and a person who may grant access.
- 2 · PermitPermission Layer
This is the permission layer at work: only the owner of the data may grant access, as recorded in the library, the PLM or the org chart. demi proposes the smallest fitting right, such as read access to four drawings for 14 days instead of full access to the whole project. Request, approval, expiry and removal are all logged.
- 3 · ActIntelligence Layer
The agent understands the request, finds the matching documents and proposes scope and duration with reasons. It sets and removes rights only through the permission management of your systems, exactly as approved. Two days before expiry it asks whether access is still needed. An extension again needs the owner's approval; otherwise the agent removes the right on time.
How it runs
- 1
You write in the chat, in one sentence, what you need and why.
- 2
demi finds the location, the documents and the person who owns the data.
- 3
The agent proposes the smallest fitting right and an expiry date, with reasons.
- 4
The owner approves with one click, narrows the scope or declines.
- 5
demi sets the right, sends a reminder before expiry and then removes it on its own.
What changes
Access in minutes instead of days
Temporary rights stay temporary
Every access logged with request, approval and expiry
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.
Your numbers
Result
+200 hfreed per year
Assumptions and calculation
demi finds location and owner and proposes a time-limited right; the owner approves with one click.
25 min → 15 min per case
How we calculate
100 access requests × 25 min × 40% × 1.0 (manual) × 12 months = 12,000 min = 200 h
Value per year, before demi costs
Freed per year+200 h
Assumption: labor cost of $48.62 per hour in US manufacturing in June 2026 (BLS), plus workplace, IT and overhead.
= Value per year, before demi costs
+$13,000
gained per year
200 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 packageQuestions about this use case
How does demi know who owns the data?
From what is already there: the owner of a library or team site, the person responsible in the PLM or DMS, the department in the org chart. If no owner is clear, demi asks the head of the area and suggests settling ownership once. Ownership becomes more complete with every request.
Does demi grant rights without approval?
No. Every right needs the approval of the person who owns the data. For standard cases they can set a rule, for example that design engineers may always read mold drawings. The rule then counts as the approval, and that is logged too.
Do I see in advance what is in folders I may not open?
No. Until approval you only see who your request went to, with no file names and no content. Only the owner who approves sees the list of files. demi does not even name areas marked as confidential, such as HR or management; requests there go to the head of the area.
Are the rights set in demi or in our systems?
In your systems, through their own permission management: groups in the directory, sharing in cloud storage, access lists in the DMS and PLM. demi follows the same rights, so whatever someone may not see never appears in an answer from demi either.
