Revoking third party access

[GDay]

In some cases, when a new hire or an existing colleague is terminated, we want to remove their account and their access.
Extending the "onboarding" in "ChiefOnboarding", we should also have an "offboarding" part. For revoking access, we can fairly easily do this when we try to remove a user utilizing the existing integrations:

It will check if the account exists, if it does, it will list it above to be removed. One requirement would be that the manifest of the integration has a revoke key (or maybe delete or remove). The revoke key would be a dictionary where we can specify the URL to call as well as the method. Similar to how we currently have the execute part in the manifest: https://docs.chiefonboarding.com/integrations/

This will also work for when we would want to revoke the permissions from someone that is not leaving. For new hires, this option to remove an account would be on the access page. Other employees will get a separate page to remove existing accounts (through people -> colleagues -> user).

[joenilson]

Hi, there is a way to add a notification by email about the offboarding and to schedule the offboarding?.

Example:

• Is june 13th and the employee will do offboarding 15th june, schedule the offboarding and notify IT department to close other access and collect assets assigned to the employee in the offboarding date.

[GDay]

@joenilson that's kind of a reverse of the normal sequences, I guess? That would be nice to have, but is quite a bit more complicated to create. Currently, COB is mainly focussed on the onboarding part. When there is demand for offboarding too, then we can definitely make it happen though.