herbeID

AI control

AI assistants reach your herbe apps through herbe ID, and herbe ID decides whether they may. Off until an admin switches it on, and never with more rights than the person has.

Off until you say so

Off by default

A new app access starts with AI off. Giving someone an app never opens it to AI by itself.

As the person, never more

The assistant gets exactly the person's rights. The calendar, the portal or herbe service refuses what the person could not do on screen, and what cannot be undone, such as deleting an event, waits for Approve in the browser.

Anonymous mode

Names and codes of customers, suppliers, contacts, employees, items and projects are swapped for codes before the model sees them.

One connector, three assistants

A person adds herbe ID once as a connector in Claude or ChatGPT, or in Codex's configuration, and signs in. The assistant then works in their calendar, portal and herbe.service as that person.

  • A privacy mode per organisation: not offered, person chooses, or always on
  • Amounts, quantities, dates, statuses and document numbers stay real, so the assistant can still add, sort and rank
  • Anonymous mode is pseudonymisation, not anonymisation: herbe can map the codes back, so data protection law still applies, at lower risk
About herbe assist
  • The person chooses the apps

    When connecting, the person sees every app the assistant could reach, all ticked, and unticks any they want left out.

  • Disconnect at any time

    The person or an admin can disconnect an assistant. It also ends when an app's AI switch goes off or the person signs out everywhere.

  • Reading, not changing

    Assistants can read a person's herbe ID account and, for admins, their organisation's people, apps and audit log. Changes are made on screen.

How to start

  1. Switch AI on per app

    An admin turns AI on for a person's app, one at a time. Switching it off, or on for every app at once, asks you to confirm it is you.

  2. Choose the privacy mode

    Not offered, person chooses, or always on. It is set per organisation.

  3. People connect their assistant

    Each person adds herbe ID as a connector and chooses which apps the assistant may reach.

Questions about AI control

Is AI on by default?

No. A new app access starts with AI off. The per-app switch is the only AI switch there is, so nothing opens by accident.

Which assistants and apps are covered?

Claude, ChatGPT and Codex, working in the calendar, the portal and herbe.service.

Can an assistant do more than the person can?

No. It gets exactly the person's rights, and the app refuses what the person could not do on screen. What cannot be undone, such as deleting an event, waits until the person presses Approve in the browser.

Is anonymous mode really anonymous?

No, and we say so plainly. It is pseudonymisation: herbe can map the codes back, so data protection law still applies, at lower risk.

Does anonymous mode cover every AI feature?

No. It covers the assistants reached through herbe ID. Portal message labels, herbe service AI hints and herbe assist decisions still send plain text to an AI provider, whatever the mode says. The admin screen tells you so under the setting.

How do I cut an assistant off?

Switch the app's AI off, or disconnect the assistant. All of the person's AI connections end at once, and the assistant's next request fails.

See it with your own team

30 minutes, live, around the way you want AI to behave.