Open adborden opened 3 years ago
This came up with @JJediny @rocheller123 's pairing on Ops Rotation about why there are so many users in Mural who should be cleaned up.
Duplicate of https://github.com/18F/handbook/issues/2019.
😕 I'm not sure what this has to do with the handbook page? I'm talking more about the offboarding checklist, and identifying the triggering action that starts the offboarding process.
…and that the notification can be done by the supervisor or someone else on the team, if not the person leaving.
On that page lists several steps
@afeld not sure what you want to do, I can update either issue so that the details are captured. Personally I think combining them is combining two separate aspects of a large problem and we would end up splitting the story anyway.
Background Information
In order to prevent access from being abused when the access is no longer needed, TTS programs want the Tech Portfolio to trigger the offboarding process when 18F projects end and partners no longer need access.
Currently, TTS folks request access for partners in an ad-hoc fashion e.g. folks request access to Mural in #admins-mural. There is no similar ad-hoc offboarding and access gets left behind in most cases.
Implementation Steps
Acceptance Criteria