Identity Governance & Administration
sara.next
  1. sara.next
  2. Solutions
  3. Choose the path for your organisation

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.

1. Type of organisation
2. Number of identities
3. Number of systems

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.

  1. Define roles and scope attributes for the main applications
  2. Calculate approvers from rules instead of entering them manually
  3. 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.

Comparison

How the paths differ

How the paths differ
Small and mediumLargeCorporations and groups
Identities (approximate)up to 500500 – 5,000over 5,000
Typical number of systemsa few to a dozen or soseveral dozenover a hundred, global and local
Main problemAccess "on someone's word", no recordsScattered responsibilityMany dimensions of scope, audit requirements
Decision-makersNamed directlyDerived from rulesMulti-dimensional rules: company, country, function
Integrations at the startImport, possibly Microsoft 365Directory + 2–3 systemsA pilot, then waves based on qualification
ReviewsOne simple quarterly reviewQuarterly with a questionnaireQuarterly, with escalation and reports for audit
Implementation modelWith a partner, ready-made templatesProject team + application ownersA 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.