Skip to content
Assenta

Security and integration

Security, deployment and integration, on your terms

For bank IT, security and risk teams: where Assenta runs, how staff sign in, what is recorded, how AI is governed and how Assenta connects to the systems you already run.

Deployment

Your data stays with your bank

Assenta runs where your bank decides. Customer data stays inside the bank.

Your data centre

Install Assenta on your own servers, inside your own network and under your own security controls.

Your own Oracle Cloud (OCI) tenancy

Or run it in your bank's own OCI tenancy, under your account and your access policies.

No vendor hosting

Assenta does not host your system or keep a copy of your data. Customer data stays with the bank.

Identity and access

The right people see the right data

Access follows your directory, your organisation chart and the approval limits you set.

Single sign-on

Staff sign in with their Microsoft Entra ID or Active Directory accounts, under your own password and access policies.

Access by role

18 roles, from agent and team leader to back office, trainers and head of sales. Each role sees only the menus and pages it needs, and the pages it must not use stay closed to it.

Scoped to the reporting line

Every list, report, search and AI answer is limited to the user's part of the organisation. A team leader sees their team, a sales manager their teams, a regional manager their region.

Approvals with limits

Exceptions, pre-approvals and transfers follow the approval chains you set. Each approver decides up to their limit, larger requests go to the next level, and late approvals are escalated to the approver's manager.

Audit and compliance

Every action on record

The controls your risk team and your regulator's rules expect, built into the daily work of every agent and manager.

Full audit trail, kept for 2 years

Changes (before and after), deletions, owner changes, exports, approvals and AI actions, each with who, what and when. Nobody can change or delete an audit record.

Sign-in audit

Every sign-in, successful or failed, with device and location. Repeated failures, a new country or a new device raise an alert. Locations are worked out on your own server.

Do-not-call register

A customer on the register is not called by anyone in the bank, on any product. Planned calls are cancelled, and every blocked attempt is recorded.

Calling hours

A call outside your calling hours asks the agent for a reason, which is saved with the call. Automatic retries stay inside calling hours.

Exception caps

Your risk team sets a monthly cap on policy exceptions, by type, product, region or team. At the cap, requests are blocked or escalated to a higher authority.

Turnaround clocks

Every stage runs on a clock in working time, with your public holidays and Ramadan hours. Files past their standard time are flagged and chased.

AI governance

You decide how AI is used

Your bank picks one of three AI modes, and can change it at any time.

  • On

    Assenta AI features and the chat use the AI model your bank approves.

  • Masked

    Before anything reaches the model, ID numbers, mobiles, IBANs, e-mails, account and card numbers and customer names are replaced with placeholders. Names are put back in the answer. The AI chat is turned off in this mode.

  • Off

    Nothing is sent to any model. Morning briefings, approval notes and Needs Attention findings use standard text, and AI buttons are hidden.

Your model, your country

Point Assenta at the AI model you approve, in your own country or cloud.

Every AI call logged

Each call records the feature, the user, the time, the mode, how many items were masked and the result.

People approve the fixes

Fixes drafted by Needs Attention wait for a manager's approval, and every decision is logged.

Integration

Connects to the systems you already run

REST APIs connect Assenta with your loan system, core banking and CRM.

  • Sits beside your loan system. Applications are keyed and decided in your loan system. Assenta tracks every stage and chases what is stuck. Your credit team still makes the final decision in your loan system.

  • Your stage codes, mapped once. Your loan system's stage codes are mapped to Assenta stages, per product or for all products.

  • Works with your CRM, or as your CRM. Keep your CRM for the customer view and service, or use Assenta as your CRM.

  • Single sign-on. Through Microsoft Entra ID or Active Directory.

How Assenta connects with your systems
  • Loan system

    Applications and stages

  • Core banking

    Customers and accounts

  • CRM

    Customer view and service

REST APIs

Assenta

In your data centre or your own OCI tenancy

  • Microsoft Entra ID / Active Directory

    Single sign-on

  • E-mail

    Updates and alerts for staff

  • Your AI model

    In your country or cloud

Arabic built in

Arabic as a first language, not a translation pack

Full right-to-left screens

Every screen is laid out right to left in Arabic, from the moment it opens.

Arabic search

Search in Arabic, including the names on your approved employer list.

Arabic AI answers

Assenta AI answers in the language of the question.

Each user's choice

Each user picks English or Arabic, and Assenta remembers it.

FAQ

Questions from IT teams

Where is our data stored?

In your bank. Assenta runs in your own data centre or in your bank's own Oracle Cloud (OCI) tenancy. There is no vendor hosting, and customer data stays with the bank.

Can AI be switched off?

Yes. Assenta has three AI modes: On, Masked and Off. With AI off, nothing is sent to any model, and features such as briefings and alerts use standard text. With Masked, ID numbers, contact details and customer names are replaced before anything is sent.

How do users sign in?

With single sign-on through Microsoft Entra ID or Active Directory, under your own access policies. Every sign-in, successful or failed, is recorded in the sign-in audit.

How does Assenta connect to our systems?

REST APIs connect Assenta with your loan system, core banking and CRM. Applications and final credit decisions stay in your loan system, and Assenta tracks the stages around them.

How long is the audit trail kept?

For 2 years. It records changes, deletions, owner changes, exports, approvals, AI actions and sign-ins, and nobody can change or delete an audit record.

Talk to us about your security review

We walk your IT, security and risk teams through deployment, access, audit and integration, in English or Arabic.