- sara.next
- Integrations
Integrations
Integrations that turn decisions into executed changes
Approved access changes can be passed automatically to target applications — with verification of execution and a full audit trail. The scope depends on the interfaces a given application provides.
Integration models
Six levels — separately for each application
Not every application is equally ready for automation. You can start with records and reviews and switch on further levels gradually.
- Process and history in sara.next, manual change.
- Records and reviews.
- Reference data from sources.
- REST, Graph API, SCIM.
- SQL, procedures, permission tables.
- Non-standard systems.
| Level | Model | When | What sara.next does | Interface |
|---|---|---|---|---|
| L0 | Manual handling | An application without a secure API or without the ability to change access automatically. | sara.next runs the process, approvals, history and reviews. The change is made by an administrator. | — |
| L1 | Initial import | The application's access state can be loaded at the start. | The application is brought under records and reviews. | data import |
| L2 | Dictionary synchronisation | The source system provides reference data. | Lists of roles, companies, departments, locations, projects, cost centres. | depending on the source |
| L3 | REST auto-implementation | A cloud application or a system with an official API. | Access changes made through official endpoints. | REST, Graph API, SCIM |
| L4 | SQL auto-implementation | Access can be managed securely in the database. | Changes via SQL, procedures or controlled permission tables. | SQL |
| L5 | Adapter / middleware | A complex or non-standard system. | sara.next talks to the adapter, and the adapter performs operations in the system. | REST → adapter |
Auto-implementation
From request to a verified change
Automatic execution does not skip control: it is preceded by a request and approval, and ends with verification and a record in the history.
Creating a request
A request to grant, change, swap the user of or revoke access.
Approval workflow
Approval in line with the requirements of the organisation and the application owner.
Auto-implementation queue
The approved request goes into the task queue.
Execution
A change in the target application via REST, SQL or an adapter.
Verification
Checking whether the expected state has been reached.
Audit trail
The result recorded in the history, available in reports and reviews.
Systems
What sara.next can be integrated with
With applications that provide official interfaces for managing users, groups, roles, teams or resources. The scope always depends on the available API, the permission model and the client's security policy.
Microsoft 365, SharePoint, Teams
Microsoft 365 groups, security groups, Teams teams, SharePoint resources.
Active Directory and LDAP
The source of data about users, accounts and groups.
in progressSalesforce
Permission sets and user assignments.
in progressServiceNow
User roles and the link to ITSM processes.
in progressGoogle Workspace
Access based on Google groups.
in progressGitHub, GitLab, Azure DevOps
Repositories, projects and development teams.
in progressOracle Fusion
Application roles and user assignments.
in progressSQL databases and in-house applications
Integration via SQL or a dedicated REST adapter.
in progressTechnical assessment
Not every application is worth automating straight away
If an application does not allow the state of access to be changed or checked securely, the manual model, data import or an adapter is better. sara.next still runs the process, approvals, history and reviews.
Application qualification cardWarning signs
- no official API for users, roles or groups
- the API handles business data, but not permissions
- no way to verify the change made
- no test environment
- no stable user identifier
- the vendor does not allow direct SQL changes
- critical or privileged access requiring separate control
Find out which applications can be automated first
During the consultation we will establish which applications are suitable for auto-implementation, which require an adapter and which should remain in the manual model.