Identity Governance & Administration
sara.next
  1. sara.next
  2. Solutions
  3. Large organisations

Who it is for · 500 – 5,000 identities

Large organisations

Several dozen systems, a dozen or so application owners and an IT department that makes hundreds of permission changes a month. The tools are usually there — what is missing is a single process that connects them.

  • 500 – 5,000 identities
  • several dozen systems

Expert view

The problem is not a lack of tools but a lack of an owner

Organisations of this size usually already have a ticketing system, a user directory and a procedure for granting permissions. And yet answering the question "who has access to the finance system and who approved it" takes weeks. The reason is mundane: the ticketing system records requests, the directory records accounts, and nobody records the link between them — the decision.

The second typical phenomenon is privilege creep. An employee changes department, receives new access, and the old access stays because nobody has a reason to revoke it. After a few years experienced employees have access to everything — not because someone decided so, but because nobody decided otherwise.

Where to start

The first step is not configuration but a conversation: for each significant application you need to establish the application manager, the list of roles and what determines the access scope — department, location, company. These are exactly the arrangements that are later carried over into the system during application onboarding.

The second step is replacing lists of approvers with rules. With several thousand people, a list of "who approves for whom" becomes outdated faster than it can be corrected. A rule — "approved by the head of the department named in the request" — stays true despite staff changes.

Where to automate

Automatic execution of changes pays off in the systems with the highest volume and a mature interface. For the rest, a model in which the application support team receives an approved work order and confirms its execution is entirely sufficient. The process, history and reviews are then the same.

Typical order

Implementation in stages

  1. Stage 1Process reviewHow access is granted today.
  2. Stage 2Priority applicationsRoles, attributes, owners.
  3. Stage 3Import and requestsRecords and a single workflow.
  4. Stage 4First reviewWith a questionnaire.
  5. Stage 5AutomationsThe systems with the highest volume.
  6. NextFurther applicationsBased on the qualification card.

Project risks

Where implementations most often stumble

How implementation works

Worth planning in advance

  • Application owners who find out about their role on the day of the launch
  • Organisational structure dictionaries that nobody maintains
  • Trying to automate an application that has no interface for managing permissions
  • A first review with no communication to reviewers and users

Let's talk about your scale

Tell us the number of users and systems — we will prepare a proposal for the scope of the first stage.