Solutions · By size and sector
Choose the path for your organisation
A city hall with three hundred employees and a capital group operating in twenty countries need the same thing — knowing who has access to what. But they get there by completely different routes.
Three questions
Where it is worth starting
Choose the type of organisation and the approximate number of identities and systems. The recommendation changes immediately.
Commercial company · 500 – 5,000 identities
Put roles and application owners in order
With several thousand identities the problem is no longer the lack of a tool, but scattered responsibility. The key is to designate application owners and the rules by which the system itself finds the decision-maker.
- Define roles and scope attributes for the main applications
- Calculate approvers from rules instead of entering them manually
- Automate access in the systems with the most traffic
The most common reasons: an external audit, SOX or NIS2, the cost of unused licences and the speed of onboarding new employees.
With several dozen systems, divide them into groups: automation for the most frequently changed ones, import and reviews for the rest.
The numerical thresholds are indicative — they help choose a starting point and do not define the limits of the product.
Expert view
Why scale changes the way you implement, not the goal
In conversations about access management we most often hear two opposite statements. Smaller organisations say: "this is a solution for corporations, we can't handle it organisationally". The largest ones say: "we have so many systems that we don't know where to start". Both stem from the same assumption: that IGA is implemented either in full or not at all.
In reality the value appears in stages. The first stage — access records and periodic reviews — requires no technical integration and is achievable both for a company with a few systems and for a group with several hundred. The next stages, i.e. requests with an approval workflow and automatic execution of changes, are added where the volume is greatest.
What really depends on size
The number of identities primarily determines how decision-makers are designated. With a hundred people, it is enough to name them. With five thousand, they must follow from rules — from the structure, company, country — because no list survives a quarter without changes.
The number of systems, in turn, determines the integration strategy. The more applications there are, the more important it is that each gets its own deliberately chosen level of automation, instead of one ambitious plan to "connect everything".
What depends on the sector
Commercial companies usually start from external pressure — an audit, a client, a regulator — and from licence costs. Public bodies more often start from responsibility for citizens' data and the requirement of accountability: you have to be able to show on what basis someone had access to a register. This translates into different reporting priorities and a different implementation model.
Paths
Five starting points
Small and medium-sized companies
A small IT team, a few to a dozen or so systems. Order and reviews first.
500 – 5,000 identitiesLarge organisations
Many departments and application owners. Roles, rules, the first automations.
over 5,000 identitiesCorporations and capital groups
Many companies and countries. A shared model and implementation in waves.
SectorPublic bodies
Government offices, local authorities, municipal companies, essential and important entities.
SectorCommercial companies
Audit, regulations, licences, pace of hiring.
SectorEnergy and industry
Experience from three implementations.
Comparison
How the paths differ
| Small and medium | Large | Corporations and groups | |
|---|---|---|---|
| Identities (approximate) | up to 500 | 500 – 5,000 | over 5,000 |
| Typical number of systems | a few to a dozen or so | several dozen | over a hundred, global and local |
| Main problem | Access "on someone's word", no records | Scattered responsibility | Many dimensions of scope, audit requirements |
| Decision-makers | Named directly | Derived from rules | Multi-dimensional rules: company, country, function |
| Integrations at the start | Import, possibly Microsoft 365 | Directory + 2–3 systems | A pilot, then waves based on qualification |
| Reviews | One simple quarterly review | Quarterly with a questionnaire | Quarterly, with escalation and reports for audit |
| Implementation model | With a partner, ready-made templates | Project team + application owners | A phased programme, a support team on the client side |
The comparison shows typical starting points. We agree the specific scope after a conversation about your systems.
See sara.next on your own scenarios
During the presentation we will walk through an access request, approval, automatic execution of the change and a review — using examples from your organisation.