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 enable the same actions to be performed, find them below:

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

• The 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 SaaS API. The available options will be visible on the detail page of the integration.

• The reminder connector (called universal connector) is a MIA feature that enables you to create  a connector for a third-party service as a "reminder" of some task. 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 step-by-step tutorials on how to set them up.

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

In MIA, we define an anomaly as the connection to any SaaS using an email address with a different domain name than the one entered during registration to the platform.

For example, let's say 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 name and that attempt to connect to your SaaS will be tagged as anomalies by MIA.

When this happens, you have several actions to choose from 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 all users who are part of your organisation, we have created types.

These types with specific colours and names will enable you to classify your users according to their statuses: external or internal to the company, but also according to the duration of their presence with you. This is especially useful for users that are not part of your internal workforce.

How do you create and view your user types?

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

Note that the colors assigned to the types you create are randomly assigned.
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 modernisation 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 enables you to synchronise the bank of your choosing to a third-party platform in order to monitor banking data in real time.

‍

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