Offboarding of [Jeremy Stitz]

[jjzang]

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:

  Jeremy Stitiz

• team name:

  CDSP

• role on team:

  Project Manager

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

  3/31/2023

• company they work for:

  Thoughtworks.inc

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

  Jeremy.Stitz@va.gov; jstitz@thoughtworks.com

• GitHub username: (Please include @ symbol)

  n/a

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

  Slack

:raised_hands: :tada: All done. Don't fill out or modify anything below here. :tada: :raised_hands:

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] Okta account disabled (if applicable)
• [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

[ChristineYoungZA]

No Domo/GA Access

[flooose]

/request Jeremy Stitz no confluence no SOCKS no AWS

[flooose]

No github No pagerduty No sentry No datadog

@rmtolmach I was able to check that the user didn't have access to datadog, but do we just request that they get removed from Okta, even if we're not sure they ever had access? It just seems like it might confuse the Okta people.

[jjzang]

Please remove him from VA Slack space. Up till now, I am still seeing him on VA Slack

[CoryTrimmUSDS]

Removed from DSVA Slack.

This is a manual process @jjzang. Please ensure any/all other ThoughtWorks members are appropriately filed for offboarding - seeing that this individual's last day was over 4 months ago...

[jjzang]

Thank you so much. Really appreciate it. I actually came onboard in June, after this person rolled off. I would make sure folks rolling off are appropriately filed for offboarding moving forward. Thanks again!

[rmtolmach]

@rmtolmach I was able to check that the user didn't have access to datadog, but do we just request that they get removed from Okta, even if we're not sure they ever had access? It just seems like it might confuse the Okta people

@flooose yeah, we do. I asked this same question. See this thread if interested.

[Kshitiz-devops]

https://jira.devops.va.gov/servicedesk/customer/portal/1/DOTSD-31969