You know what systems you have. You know what information you store. But do you know exactly who has access to it and when they got it?
For many organizations, the answer is varied. Not because they are sloppy with security, but because authorization management is rarely a process. It is a state.
The difference between a state and a process
A state is that permissions exist. A person has access to a system. It happened at some point. Maybe when they were hired, maybe when they changed roles, maybe because they asked the right person at the right time.
A process is that you know why the asset exists, who approved it, and what happens when the need ends.
Most organizations live in a state. It works, until it doesn't. Until an auditor asks. Until someone wants to see your access control. Until a terminated employee's login is still active six months later.
Information classification as a basis
Before you can manage who reaches what, you need to know what you have and how sensitive it is.
Information classification is about categorizing an organization's information based on the consequences of unauthorized access. A simple model has three levels: open information, internal information, and confidential information. The classification then controls the authorization structure, who needs access, in what form, and under what conditions.
It's not a technical job. It's an operational job. IT can support with infrastructure, but the decision about what is confidential is made by the business, by those who own the information.
In Easit GO, the classification can be documented as part of a case. For information classified as confidential, such as personal data, it also matters where the system is operated, something we cover in the article about GDPR-safe digitization with data in Sweden. Each asset can be linked to a classification level, and the authorization process can be built around it.
Authorization management as a structured process
A structured authorization process in Easit GO looks something like this:
Someone in the organization needs access to a system or dataset. They create a case in the self-service portal. The case contains what they want access to, why, and for how long.
The case goes to the correct approver – the system owner, data protection officer or manager depending on the classification level. The approval is documented. Access is granted. The case is closed with a timestamp.
This doesn't require any technical integrations with the current system to be valuable. The value lies in the documentation: you can show who has access to what, who approved it and when. That's what an auditor is looking for. That's what GDPR requires.
The connection to onboarding, offboarding and the treatment register
Permission management is not an isolated process. It is connected to three other processes you probably already manage – or should manage – in Easit GO.
Onboarding. When a new employee starts, the onboarding process defines what permissions they need. With a structured process, the initial permission assignment is documented from day one.
Offboarding. When an employment is terminated, authorization revocation is one of the most important tasks. We have written about why offboarding is a security issue – and it is in authorization management that the risk is greatest. A structured process in Easit GO can automatically generate revocation tasks when an offboarding case is opened.
The processing record. Your personal data processing record is static – it describes what you do. The authorization process is dynamic – it shows who actually has access to the information. The two complement each other. Together, they provide you with the documentation required for supervision.
Relationship models – get an instant picture of who is reaching what
A structured process gives you documentation. But sometimes you don't need to dig into cases – you need a quick overview.
In Easit GO you can build relationship models that visualize the connections between objects: which systems exist, what levels of information they contain, and which roles or people have access to them. All in one view.
It’s especially useful for periodic reviews—the quarterly review of permissions that most organizations should do but rarely do because it’s too time-consuming. With a relationship model, you can see right away if something looks wrong: a person who has access to a system they left six months ago, a role that has been given more access than its classification warrants, a connection that no one can explain anymore.
And when you find an error, you correct it immediately. Easit GO's quick functions let you update permissions, trigger a correction request or flag for follow-up without having to navigate to a separate system. Overview and action in the same view.
This turns the authorization review from a project into a routine.
Frequently asked questions
What is information classification? Categorizing an organization's information based on sensitivity – what is public, what is internal, what is confidential. The classification controls what permissions are required to access the information.
How does authorization management relate to GDPR? GDPR requires that access to personal data is limited to those who need it. A documented authorization process – who was granted access, when and by whom – is a direct requirement for oversight.
Can this be handled in Easit GO? Yes. Application, approval flow, assignment and documentation – all in one trackable case. Configured by your designer, without code.
What are relationship models in Easit GO? Relationship models are visual views that show the connections between objects in the system – for example, which systems exist, what level of information they contain and who has access. This provides an immediate overview and the ability to correct errors directly via quick functions, without navigating to separate views.
Do you know who has access to your sensitive information? Can you show it to an auditor?
Authorization management and information classification are not issues for IT alone. They are organizational issues and they require a process, not a permit.
Want to see how it can be built in Easit GO? Book a demo
Read also:

Henrik Traveler
Commercial Product Manager
henrik.resare@easit.com
+46 70 249 36 06