Intigate core · security, access & audit

The right access.
A traceable action.

Bring identity, roles, session controls and traceable actions together, with hosting aligned to your requirements.

Explore the workflow

The operational detail

Control the access. Keep the evidence.

Access controls matter most when they follow the organisation. Define who can work in each module and keep a trace of the actions that follow.

See the connection

Identity, permission and audit in one view.

Explore the stages to see how the records, checks and teams connect.

ILLUSTRATIVE INTERFACE · SAMPLE DATA
ACCESS & AUDIT CONTROL

Identity view

1Identity2Permissions3Session4Audit
Sample rolePolicy viewApprovalAudit
UnderwritingAssigned scopeBy authorityRecorded
FinanceAssigned scopeBy authorityRecorded
Internal auditRead scope—Authorised access
FocusCentral identity
EvidenceTraceable actions and record changes

Illustrative role matrix. Permissions are configured for your organisation.

Module capabilities

The detail that makes the difference.

Capabilities shaped around the records and workflows your team uses every day.

  • Identity and roles

    One sign-on across Intigate Core applications, with roles and permissions by module, branch and business line.

  • Single active session

    Banking-style control: a user has one active session at a time, and a new sign-in ends the old one.

  • Audit trail

    Every create, change, approval and posting is recorded with user, time and before-and-after values.

  • Data protection

    Encrypted connections, protected credentials and backups aligned with your information-security policy.

  • Hosting choice

    SQL Server on your premises, in your private cloud or on Azure; the same application either way.

  • Operations

    Monitoring, scheduled jobs and release management handled by Intigate under a support agreement, or by your own team.

A clearer operating model

From workarounds to connected records.

Common constraints in older custom applications, and the corresponding Intigate Core workflow. Your current implementation may differ.

Full comparison
Legacy application constraintIntigate Core
Shared logins and generic accountsNamed users, roles and one active session each.
Changes with no record of who or whenFull audit trail across modules.
Oracle estate that must stay on premiseSQL Server on premise or in the cloud.

Your questions

Start with
better questions.

Can we use our existing Active Directory?

Yes. The identity service can federate with your directory so users sign in with their corporate credentials and leavers are disabled centrally.

Where is the data hosted?

Where you decide: SQL Server on your premises, in your private cloud or on Microsoft Azure. Data residency requirements in Kuwait and the Gulf are respected.

Who can see the audit trail?

Authorised roles such as internal audit and compliance; the trail itself cannot be edited.

Let’s build what’s next

Your next chapter starts here.

Contact number