Solutions · By sector
Public administration: shared rules, distributed units
Access management in government offices, organisational units and municipal companies.
- government offices and local authorities
- subordinate units
- municipal companies
Context
Many organisational units, many systems and different responsibilities
Government offices, subordinate units and municipal companies often use separate applications and user directories. The same employee may carry out duties in several processes, and a change of organisational unit does not always mean that old permissions are automatically revoked.
sara.next makes it possible to unify the process of requesting, approving and reviewing access while preserving the differences between applications. Organisational dictionaries, roles and their dimensions can reflect departments, units, locations and areas of responsibility.
Use cases
Possible scenarios
Domain system
A request for access to a domain system approved by the relevant line manager and the application owner.
Reorganisation
Reviewing permissions after departments are reorganised.
Employees and contractors
Putting in order the access of unit employees and external contractors.
Systems without an API
Importing permissions from systems that do not provide an API.
Internal control
Reporting decisions and changes for internal control.
Scenario
Reorganisation of an office
After two departments are merged, some employees change their scope of duties. Instead of manually reviewing accounts in each application, the organisation initiates processes for modifying and removing permissions. System owners verify which roles remain justified. A centralised history makes it possible to assess the progress of the changes.
An implementation expert's view
Responsibility first, then the system
In public administration what is critical is not the number of accounts but correctly mapping responsibility. You need to establish:
- who owns the application,
- who approves access in the unit,
- who makes the change,
- who is responsible for the review.
Without this, a central system will become just another ticket inbox.
Regulations and practice
Accountability instead of trust
Public bodies work in special conditions. There are many systems from different vendors: finance and accounting, HR, electronic document management, domain systems, registers, cloud resources. Each has its own accounts and its own way of granting permissions. At the same time the structure is formalised — departments, divisions, sections — and responsibility for data follows from the law.
In practice access is often granted on the basis of a paper form or an e-mail, and its record is a spreadsheet kept by an IT staff member. As long as that person works there and remembers — the system works. The problem shows up during an inspection, after an incident or when you need to establish what permissions an employee had who changed position two years ago.
What regulations expect
The requirements for public bodies — from the National Interoperability Framework (KRI), through the national cybersecurity system legislation implementing NIS2, to the GDPR — have one thing in common: permissions must match tasks, be changed promptly when tasks change, and the body must be able to document this. None of these regulations specifies a tool. But all of them require a process that can be shown to an inspector.
What this looks like in sara.next
Every grant, change and revocation of access goes through a request approved by an authorised person — in line with the body's structure. Access rules can be based on department, location or position. A periodic review in which managers confirm the permissions of their subordinates creates evidence that permissions are verified, not just granted.
Infrastructure is also an important issue. sara.next is delivered as a container and can run in the body's own server room or in a cloud the body chooses. Sign-in uses the work account, through the organisation's identity provider.
Typical situations
Where access gets lost in a public office
| Situation | Risk | The answer in sara.next |
|---|---|---|
| An employee moving between departments | Permissions to previous systems remain | Periodic review and information about changes in user data |
| Cover during holidays | Access "borrowed" and never revoked | Time-bound access with an expiry date |
| Interns, trainees, fixed-term contracts | Accounts active after collaboration ends | An access deadline in the request, an automatic removal request |
| An external company's access to a system | No responsible person on the office side | A request with an approver and periodic review |
| Inspection or audit | Manually reconstructing the history from e-mail | Reports and request history |
| An administrator leaves | Knowledge of permissions disappears with them | Records that do not depend on one person |
Who it is for in the public sector
Different bodies, the same obligation
Government offices and ministries
An extensive structure, domain systems, registers.
Cities, counties, municipalities
The office and organisational units with their own systems.
Municipal companies
Water, heating, transport — also as entities covered by NIS2.
Universities, hospitals, agencies
High user turnover and specially protected data.
How to start
The path for a public body
An order chosen so that the first result — records and reviews — appears without integration with domain systems.
System inventory
Which systems process citizens', financial and HR data.
Responsible people
For each system: who decides on access in line with the structure.
Permission import
The current state from files supplied by administrators.
Electronic request
In place of a paper form and e-mail.
Review
Managers confirm the permissions of their subordinates.
Reports
A list of permissions and decision history for inspection purposes.
Frequently asked questions
- Can the system run in our infrastructure? — Yes, it is delivered as a container.
- Do employees need separate passwords? — No, sign-in uses the work account.
- Are the interface and documentation available in Polish? — Yes.
- Can we start without integration with domain systems? — Yes, with an import and the manual model.
- Who implements it? — braf.tech or one of our integrator partners.
Scope
Implementation considerations
Requirements concerning hosting, data protection, integration with domain systems, digital accessibility and the division of responsibilities should be assessed individually.
NoteYou should not assume automatic integration with every system used by public bodies.
Analyse a shared entitlement process for an office and its organisational units
During a technical consultation we will go through your applications, roles and the scope of the first implementation stage.