Boring user administration processes are out.
Now, MIA is in.

Connectors (also called “integrations”) in MIA refer to the various SaaS software that you link to the platform to manage them. There are different types that do not allow the same actions to be carried out, here are the details:

• full integration : is a connector for which all access and identity management options are available from MIA. As a reminder, these options are: retrieving the user listing from SaaS, creating and deleting a user, moderating their access rights (adding or removing access to a SaaS) and editing their information.

• Partial integration : it is a connector for which only certain options are available. Retrieving the user listing is a prerequisite, and will therefore be available for all full and partial integrations. In terms of creation or deletion, it will depend on the functionalities offered by the developers of the SaaS in question. The available options will be visible on the presentation page of the integration concerned.

• The reminder connector (called universal connector): is an MIA feature that allows you to create a “reminder” in the form of a connector for a third-party service. Although it is not an integration like the previous two, this connector helps you centralize your user management.

Find the complete list of integrations available on MIA and the steps to set them up.

One of the main functional aspects of MIA is user management. Among the functionalities included in this module, the detection of anomalies requires some clarification.

In MIA, Is considered an anomaly the connection to a SaaS of an email address whose domain name does not correspond to the one entered during registration. to the platform.

Example: your company is called collaboration.fr. The employees of your company all have a professional email address that ends in @collaboration .fr. You therefore enter the domain name “collaboration.fr” when you register on MIA.

From there, all email addresses that do not end with this code and that attempt to connect to your SaaS will be cataloged as anomalies by MIA.

When this happens, you have several actions to deal with the anomaly:

1. Create a user from a detected email address.

2. Delete permanently the address detected.

3. Merge the detected address with an existing account.

In order to better identify the role of the users that make up your organization, we created types.

These types with specific colors and names will allow you to classify your users according to their status: external or internal to the company, but also according to the duration of their presence with you, especially for users who are not employees.

How do you create and view your user types?

Go to the “Settings” tab of the application, then “User Types”. You can create a new type by directly typing the name of the type you want and then clicking on “Create”.

Note that the colors assigned to the types you create are generated randomly. You can use up to 10 different user types to meet your organizational needs. All the types you have already created will be visible and editable on the page mentioned above.

Bridge API is an Open Banking protocol. It is approved by the ACPR and DPS2 certified.

The DPS2 certification (2nd Payment Services Directive) is a European directive that aims at the modernization and supervision of payment services. Among the measures it provides, there is the requirement of strong authentication* for payments exceeding €30.

This Bridge API protocol is a secure system which allows you to synchronize the bank of your choice in order to be able to monitor banking data in real time.

‍

*Strong authentication refers to a system that requires two authentication factors to connect to a service (for example a password plus a fingerprint).