Platform · Configuration
Administration panel
Applications, roles and processes are configured in the panel, without touching the code. The needs of the business and of individual applications determine how the process runs.
- configuration export and import
- a ticket number for every change
Scope
Four areas of the panel
| Area | What is configured there |
|---|---|
| Applications | Applications and categories, roles, access attributes, request processes, approver blocks, validators. |
| Import | Initial access, access archiving, dictionaries — from Excel files. |
| Configuration | Reviews and questionnaires, reports, parameters, scheduled jobs, dictionary synchronisation, access tokens. |
| Communication | News, release notes, notifications and their schedules, user instructions. |
Expert view
Configuration instead of programming — and why it matters
In many enterprise-class systems every process change means an order for the vendor: analysis, quote, deadline. As a result the process in the system drifts away from reality, because a change is too expensive to make as you go.
In sara.next applications, roles, workflows, notifications and reports are configured in the panel. A new application can be brought under control by an administrator on the client side — after agreeing the rules with its owner. More complex logic, such as rules for deriving approvers, is written in short scripts that can be moved between environments.
Flexibility requires discipline
Being able to change everything can be a risk. That is why the panel enforces two practices. Every save requires a ticket number — you cannot change a rule "quietly". And the configuration is prepared in the test environment and moved to production as a file, rather than clicked through a second time.
In companies subject to controls, this is not a formality. Changing a rule that decides who approves access to a finance system is itself an auditable event.
Application onboarding
A new application under control in seven steps
Dictionaries
Reference data: companies, countries, departments — added manually or imported.
Attributes
Access dimensions linked to dictionaries: list, multiple choice, computed value.
Application
Name, category, how the user is identified, flags: SOX, expiry date, requests.
Roles
Allowed request and review types, attributes, limits and validators.
Approvers and reviewers
Rules that derive the decision-makers for each role.
Request process
A workflow modelled graphically and imported as a process file.
Access import
Loading existing entitlements from a file, without triggering approval.
Flexibility
Rules where a form is not enough
Rules in scripts
Deriving approvers, attribute values and notification recipients is described in scripts.
Notification templates
Subject, recipients and content of e-mails — separately for each event, also on a schedule.
Dictionary synchronisation
Dictionaries refreshed from source systems by priority.
Scheduled jobs
A list of jobs run regularly, with the option of starting them manually.
Moving configuration
Export and import between test and production environments.
Change control
Saving a change requires a ticket number; subsequent actions are assigned to it.
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.