- sara.next
- Integrations
- Application qualification card
Integrations · Getting started
Application qualification card
Not every application is worth automating straight away. A few questions help establish which integration level is right for it.
Questions
The integration level depends on the answers
| Question | If yes | If no |
|---|---|---|
| Does the application have an official API for users, roles or groups? | L3 — REST | L4, L5 or the manual model |
| Can access be managed safely in the database? | L4 — SQL | L5 — adapter |
| Can the access state be checked after a change? | Auto-implementation with verification | Manual model or adapter |
| Is there a test environment? | Pilot | Import and reviews first |
| Does the user have a stable identifier? | Import and automation | Cleaning up identifiers |
| Is the access critical or privileged? | Separate control, cautious automation | Standard process |
Expert view
The honest answer is sometimes: we do not automate this application
Solution vendors are keen to show lists of "hundreds of ready-made connectors". In practice the success of an integration depends not on the number of connectors but on whether a specific application, in a specific version and configuration, provides an interface for managing permissions — and whether it lets you check the result.
That is why before every integration we go through a few simple questions with the application owner. The answers lead to one of six levels. A "level zero" result is not a failure: the application is covered by the process, approvals, history and reviews, and the change is made by a person based on an unambiguous work order.
Treat privileged access separately
Administrative accounts require particular caution. Automatically granting administrator rights based on a request is technically possible, but usually requires additional safeguards outside the IGA system. This is one of the warning signs for which we recommend the manual model with a second approval level.
Result
Six possible answers
- Process and history in sara.next, change made by an administrator.
- Application covered by records and reviews.
- Reference data from source systems.
- REST, Graph API, SCIM.
- SQL, procedures, permission tables.
- Complex and non-standard 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.