User must exist in a roster before SOCKS access can be granted
[ ] If the roster check automation doesn't run, search for the VFS team member in Atlas. If user is on a VFS team but not in Atlas, add the 'NOT YET' label and instruct them to start Platform orientation. Otherwise, leave a comment saying they were found in Atlas and then grant access.
[ ] If the roster check automation doesn't run and the requester is on the Platform team, search for user on the Platform Team Roster. If they're not listed, add the 'NOT YET' label and instruct them to reach out to their Product Manager to be added. Otherwise, leave a comment saying they were found on the Platform roster and then grant access.
[ ] If the requester is on a Lighthouse team and not found in Atlas, search for their name on the Lighthouse Team Roster. If they're not listed, add the 'NOT YET' label and instruct them to reach out to their Product Manager to be added. Otherwise, leave a comment saying they were found on the Lighthouse roster, add them to Atlas, then grant access.
Your Name
Sarah Wheeler
Your Email
sarah.wheeler@wilcore.io
Your GitHub Handle
sarahwcodes
Your Role and Team
Rails Engineer on VA Notify
Product Manager (PM) name and email
Samantha Jennings, samantha.jennings@oddball.io
Product Owner (PO) name and email
Dave Conlon, david.conlon@va.gov
Access Type Requesting
developers
Public SSH Key
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIJDbnxh3BF5VNCvDiMYqR2rgbJlRMonuVqzHxTUOQjwq sarahwheeler@Work.local
e-App (aka E-QIP) Transmittal Confirmation
Lighthouse?
User must exist in a roster before SOCKS access can be granted