Offboarding of [Kevin London]

[elizabethmkoch]

Instructions

Fill out name of individual and Description section below.

(Please add only one individual per form)

Description

Please provide the following information about the individual being offboarded:

• name:

  Kevin London

• team name:

  identity-product-team (login.gov adoption team)

• role on team:

  Program Management / Executive at Frog Design

• expected last day: (MM/DD/YYYY)

  12/23/2022

• company they work for:

  Frog Design

• email: (Multiple emails listed in order of relevance to VA business, VA, Company, Personal, etc....)

  kevin.london@frogdesign.com

• GitHub username: (Please include @ symbol)

  @godovino71

• additional access they may have: (First line formatted with access titles only. Additional notes may be added on second line after the list.)

Acceptance Criteria

The following steps are performed by the Platform Support team. Detailed instructions found here

• [x] Requested removal from DSVA Slack (if applicable. Search for them in Slack)

  A comment on this ticket prefixed with /request (i.e. /request FirstName LastName) will send a message to the Slack admins automatically!

• [x] Requested removal from Confluence (if applicable. Check confluence members)
• [x] Remove from VFS Team Roster (if applicable)
• [x] Remove from global/config.yml / SOCKS Access removed (if applicable. Search their email in config.yml)

  Use the Remove SOCKS and AWS access Github Workflow to create a PR to update the global/config.yml file and remove the public SSH key. You'll need the user's email address associated with their public key (found in config.yml).

• [x] AWS Access removed (if applicable. Search their name in AWS IAM)

  Use the Remove SOCKS and AWS access Github Workflow to remove user's entry from DSVA AWS. You'll need the user's AWS username (typically First.Last).

• [x] User removed from the VA GitHub Org (if applicable. Check department-of-veterans-affairs/people)

  Fill out request found here.

• [x] Pagerduty access removed (if applicable. Check pd users)
• [x] Datadog account disabled (if applicable. Check Datadog users)
• [x] Sentry access removed (if applicable. Check Sentry members)
• [x] Google analytics and Domo access removed (if applicable. Make sure the analytics-insights label is on this Issue)
• [x] Bot (va-bot, va-vfs-bot, and va-vsp-bot) user GitHub account(s) YubiKey(s) removed

  This is rare. See documentation for current users and removal process.

• [x] Sketch editor access removed (if applicable. Check Sketch settings)

• [x] Removed from Monday Design Meeting invite

  CC: @department-of-veterans-affairs/vsp-operations , @department-of-veterans-affairs/platform-analytics-insights-team , @department-of-veterans-affairs/confluence-admins, @department-of-veterans-affairs/platform-design

[michelle-dooley]

No Domo or GA.

[SrfFshn]

/request Kevin London Please remove from DSVA Slack

[CoryTrimmUSDS]

Removed from DSVA Slack

[SrfFshn]

/request Kevin London Please remove from Confluence, Datadog, Sentry, AWS, SOCKS, Sketch and Monday Design Meeting

[CoryTrimmUSDS]

Again - the /request command will only run this GitHub Action to notify Slack Admins (VA Employees) to remove an individual from the DSVA Slack instance.

My understanding is that on-call engineering support (Contractors) + tool owners (typically contractors) will remove individuals from the various tools in ~24 hours.

[holdenhinkle]

no Confluence no SOCKS no DD no PG no Sentry

@naomimarcussen Sketch + Meeting :-)

[naomimarcussen]

Removed from Sketch and meeting invite. :)