Who sees what, in one sentence.
Rules in Vortner read the way you’d say them out loud. Your teams, your IT and your works council read the same sentence the system runs.
Team leads can see absence dates of their team.
One page shows who can see what.
Every rule adds up to one overview, per team and per tool. It’s the page people screenshot when someone asks “who can actually see this?”
| Tool | Sales | Finance | Team leads | Working students |
|---|---|---|---|---|
| HubSpot | Their accounts | Deal values | None | Their own accounts |
| DATEV | None | Everything | None | None |
| Personio | None | None | Their team | None |
| Google Drive | Sales folder | Finance folder | Their team | Templates only |
Try it before it goes live.
Pick a person and ask a question as them. You see what they’d get, and which rule decides.
Safe by default, easy to change.
You don’t start from an empty page, and you can’t accidentally open everything up.
No rule, no access
If no rule allows something, the AI doesn’t get it. Nothing is open by accident.
Starts from templates
Starter rules per role, so the first useful answer comes on day one.
Uses the groups you have
Microsoft Entra groups, roles from your tools or single people. No second user list to maintain.
Read and send, decided separately
Let the AI read deals but only draft emails. Or send, but never read the inbox.
Temporary access ends by itself
Covering for a colleague? Access runs out on the date you set.
Limiting is instant, widening is checked
Taking access away works right away. Giving more goes through approval.