Vortner is in its test phase. We're looking for a few more teams to try it with.Get in touch ›
Product
ConnectionsRulesApprovalsRecordUsage
How it worksSecurityBlogGet updates
DEEN
Book a call →
‹ All posts

Why your works council should see the AI rules first

By Paul Karrmann2 min read
The rule this post argues for

The works council approves every change that lets anyone see more about people.

Waiting for the works council

I've sat in a lot of AI kickoff meetings by now, and most of them end the same way. IT has a tool picked out, management wants it live by spring, and then someone from the works council asks a simple question: what will it be able to see?

Nobody in the room can answer. Not because they're hiding anything, but because "it sees what the user sees" sounds fine until you remember what some users can see. The meeting ends with a follow-up meeting. The rollout slides a quarter.

The question is fair

In Germany the works council has a say over technical systems that can monitor how people work. An AI assistant connected to your HR tool, your CRM and your inbox is exactly that kind of system. So the question isn't an obstacle. It's the job.

The real problem is that most setups give them nothing to look at. Permissions live in five tools, each configured a bit differently, and the AI quietly inherits all of it.

Show them sentences, not settings

What changed things for us was writing every rule as one sentence a person can read out loud. Team leads can see absence dates of their own team. Anyone can check that sentence. Nobody has to understand role mappings or scopes to say yes or no to it.

And then, the part people don't expect: the works council doesn't only read the rules once. They're part of the approval for every change that would let someone see more.

Finance can see deal values in HubSpot.5 people in finance would see more for 214 deals.
  1. TM
    Tom MeierProposed the change
    Proposed
  2. LH
    Lea HoffmannSecond admin
    Approved
  3. TK
    Thomas KellerWorks council
    Waiting

That sounds slow. In practice it's the opposite. Once the works council knows nothing can widen without them, they stop needing to approve the whole system up front. The first meeting gets shorter, not longer.

Limiting never waits

One detail matters a lot here: the approval only applies in one direction. If someone wants to take access away, it happens right away. Nobody should have to wait for a signature to make things safer.

So the rule at the top of this post is the one I'd start with. It costs the works council a few minutes a month, and it saves you the follow-up meeting.

Want to see what this rule looks like with your tools?

Book a callGet updates