loripusey commented 10 months ago

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:

Kelly Smith
team name:

Modernized Check-in (aka Check-in Experience [CIE])
role on team:

UX - content writer
expected last day: (MM/DD/YYYY)

02/16/2024
company they work for:

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

kelly.smith23@va.gov kelly.smith@civicactions.com
GitHub username: (Please include @ symbol)

@kellysmith1008
COR:

Cecelia Lee
PM:

Katherine Lawyer - OCTO Lori Pusey - Agile 6
additional access they may have: (First line formatted with access titles only. Additional notes may be added on second line after the list.)

ex: SOCKS, Pagerduty, Google analytics, etc. DSVA Slack Sketch Figma Github Zenhub

: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 Platform Atlas (if applicable)
[x] SOCKS access removed (if applicable. Search their email in config.yml)

Use the Remove SOCKS and AWS access Github Workflow. You'll need the user's email address associated with their public key (found in config.yml). Merge the PR.
[x] AWS access removed (if applicable. Search their name in AWS IAM)

Use the same SOCKS and AWS access Workflow to remove user's entry from iam_users.tf. You'll need the user's AWS username (typically First.Last). Merge the PR and apply Terraform.
[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
[x] Datadog (if applicable. Check Datadog users)
- [x] Disable in Datadog UI (must be done by a datadog admin)
- [x] Submit an ECC request (Only necessary if they were in the Datadog UI)
[x] Sentry access removed (if applicable. Check Sentry members)
[x] TestRail access removed (if applicable, Check TestRail User List)
[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

rmtolmach commented 10 months ago

No datadog 🐕

barbarello commented 10 months ago

/request Kelly Smith No confluence removed from Atlas removed SOCKS No AWS No github No PagerDuty No Sentry

CoryTrimmUSDS commented 10 months ago

Hey @barbarello - please use the /request command after the employee's last day otherwise we risk removing them accidentally before they're done working at VA.