Users
The Users page is the directory of the people in your organization. Each user groups their application access: their accounts on the various services.
The list
The list can be searched by name, email or username, and filtered by application, type and state. The State column flags what is waiting for you:
- Access to handle: a closing to do by hand whose date has passed, a scheduled access MIA could not process in time, or an opening or closing that failed. Hovering it lists the accesses concerned.
- Breach: an address of the user appears in a data breach you have not marked as read yet (Pro feature).
The filters stay in the page address: a link to a filtered list, such as the ones in MIA's emails, opens it as is.
The user profile
A user carries an email (required, their primary identifier), a last name, a first name, an optional username, and a type (see User types).
Their profile reads from top to bottom:
- their information, which the Edit button changes;
- their accesses: for each application, the identity they hold there, the opening and closing dates, and the state of the access;
- folded, their associated identifiers and the information sent by the applications (job title, department...);
- at the very bottom, the deletion of the user.
The View in traceability button opens the history of their accesses (Pro feature).
What you can do
- Create or edit a user.
- Manage their access: open or close an application access (see Access opening & closing).
- Delete a user.
WARNING
Deleting a user also closes their remote accounts on the applications that allow it.
MIA closes their accesses one application at a time. If an application refuses, the user is kept with the accesses that remain, and the window says what was done on each application; the accesses already closed stay closed. On an application where MIA cannot delete an account, the access is only unlinked: the remote account lives on. If it carried an end date, the window asks you to confirm that you closed the account on the application, and the closing is recorded as such.
Good to know
- The directory can populate automatically: when automatic user creation is on (Configuration → Organization), accounts whose email matches your domain name become users during syncs. Otherwise, they become anomalies.
- Data-breach detection is a Pro feature.