Agentverkstad
Menu

Guide · Last updated 11 November 2026

Security and permissions for AI agents

Give an AI agent the least permission the task needs, let it read before it may write, and keep an approval where a person looks before anything is sent or changed. That is the foundation. The rest comes down to knowing what the agent can reach, being able to see what it has done and being able to shut the access quickly if something goes wrong.

Six rules for safe agents

What can go wrong

Questions to ask a provider

How to set permissions step by step

First write the task down in one sentence and list what the agent needs to see to do it. Then give read access to exactly that. Run it for a week and read everything the agent suggests.

When the result holds, you can add a write permission, always with approval from a person. Widen in small steps and write down every change. That makes it easy to know where you stand.

Write down every permission, who decided it and why. The list makes it easy to review and to shut what is no longer needed.

When something goes wrong

If the incident involves personal data there may be a duty to report it. Ask a lawyer or your data protection officer what applies to you.

An example: an agent that writes the weekly report

The task is to compile status from three systems into one page every Monday. The agent gets read access to the three, an account of its own and no ability to send. The result is placed in a folder where the project manager reads it.

If the agent writes something wrong it shows in the trail, and the access can be shut at once. If you later want it to send the report itself, that is a new step with an approval of its own.

Who owns security in your company

Appoint one person who owns the permissions for each agent. She knows what the agent may do, approves changes and shuts the access if something goes wrong. Without an owner, permissions remain long after the task has changed.

Go through the list of agents and permissions regularly and delete what is no longer needed.

How we work with this

With us, every step has a stop point where you look at the result before we move on. The price is fixed per step, with a cap, and is set before the step begins. We sign a data processing agreement before we touch any information.

The text here is general information and does not replace legal or technical advice for your business.

Common questions

What is least permission?

That an agent only gets access to what the task requires. If it only needs to read a calendar, it should not be able to read email.

Should an agent be allowed to write in our systems?

Yes, but start with reading. Add write permission only when the agent has shown that it does the right thing, and let a person approve what it writes.

Why should the agent have its own account?

Then you can see what it has done and withdraw the access without affecting any colleague's account.

Can an agent be tricked by text in an email?

Yes, text in emails and documents can try to steer an agent. That is why you treat content as material to read and let nothing be sent or changed without approval.

What should we ask a provider?

Where the information is stored and for how long, whether there is a data processing agreement, how the agent's actions are logged and how you shut the access.

Do we need a lawyer?

For questions on personal data and liability, yes. Ask a lawyer or your data protection officer to assess what applies in your business.

Read also

Tell us where the time goes.

Book a first call straight away, 30 minutes and free of charge. Or leave a few lines and we will get back to you.

Fetching available times …

Other ways in