Skip to content

Access opening & closing ​

From a user's profile, MIA can open (provision) or close (deprovision) their application access and, when the application allows it, do so directly through the service's API.

Opening access ​

On the user profile, Add to an application opens a side panel: choose one or more applications, or a kit, then fill in what each service asks for. If some applications refuse, the panel stays open on them, with the reason for each failure; the other accesses are opened. The behavior depends on the application:

  • Write-capable application: MIA creates the account on the service. You can open the access immediately or schedule it for a start date.
  • Manual or read-only application: MIA records the access in the inventory but doesn't act on the service. It's up to you to create the account on the application side.

An application kit lets you pre-select a set of applications at once.

Closing access ​

Two options, depending on the case:

  • Unlink: removes the link in MIA without touching the remote account (useful for an access linked by mistake).
  • Delete: closes the remote account on the service (if the application allows it).

You can also schedule a closing for an end date: MIA will close the access automatically when the time comes.

On an application where MIA cannot close accounts (a manual or read-only one), the end date is kept, but MIA never withdraws the access automatically: closing the account on the application is up to you. MIA reminds you by email on the first three days from the date, then every Monday as long as the access exists in MIA, and the user list shows it "to do manually", with the Access to handle chip once the date has passed. Once the account is closed, delete the access in MIA: the deletion asks you to confirm the closing, which is then recorded as such.

If the application refuses the deletion, the access stays in place marked "Failed": the remote account is still open. You can try the deletion again, or set an end date so that MIA retries it automatically.

Accesses to handle ​

In the users list, the State: Accesses to handle filter gathers the people with an access waiting for you:

  • a closing to do by hand whose date has passed;
  • a scheduled access MIA could not process within two days of its date;
  • an opening or a closing that failed.

The reminder of the accesses awaiting action and the email that reports a failed access lead straight to this filtered list.

Good to know ​

  • Manual opening and closing are included in the free plan.
  • Automating this cycle, when a person joins or leaves, is a Pro capability: see Leader application and Access requests.