Onboarding

TTS Onboarding

TTS Talent has their own onboarding checklist in Google Drive that they share with new employees. The Login.gov tab on that document has one item, a link to this page in our handbook.

Login.gov team onboarding documents

Each Login.gov team has their own personalized GDoc/Onboarding Template / Checklist, you’ll get one of these documents when you start at Login.gov.

The following onboarding tasks are applicable to all employees.

For new Login.gov team members to complete themselves

  • Familiarize yourself with the Login.gov Handbook
  • Watch a Login.gov authentication overview
  • Watch a Login.gov identity verification overview
  • Watch a Login.gov security overview
  • Review the Login.gov org chart
  • Review the Login.gov Design System
  • Complete GSA OLU IT Security Awareness Training, including accepting the GSA IT Rules of Behavior, which is required before we can give you access to any Login.gov systems. If you joined GSA more than two months ago, you’ve already completed this task. (Detailees must complete similar organization driven training and provide as proof to Login.gov team members)
  • Schedule virtual tea/coffee meetings with your team lead, other members of your team, and anyone else! Tea is just a short (~20 min) one-on-one video meeting with the purpose of getting to know each other.
  • Once you’ve been added to Slack:
    • Make sure your account is set up like this.
    • Make sure to join #login, the main announcement channel for our team
    • Contractors with full Slack access should add the word “contractor” to their Slack profile for the benefit of the wider TTS audience.
  • Make sure your GitHub account is set up like this.
  • Add the Login.gov Shared Calendar to your Google Calendar:
    • Under “My calendars” list, click “Other Calendars +”
    • Select “From URL”
    • Then paste in gsa.gov_6ovul6pcsmgd40o8pqn7qmge5g@group.calendar.google.com.
  • Add yourself to the team.yml file
  • Request access to relevant Google Groups, the handbook has a list of active groups
  • Add a signature to your GSA email account like this:

    Human Person
    Login.gov Chief of Kittens
    Technology Transformation Services
    U.S. General Services Administration

  • Request Admin rights on your TTS Macbook if you require it, e.g. if you are a developer.
  • (Optional) Add your gpg key to github

For the on-boarding buddy to complete

As an on-boarding buddy you’ll be a new employee’s main point of contact and Login.gov guide for a couple weeks. Look at this work as a power multiplier, you are helping someone gain a firm foundation to work upon, you are starting up a new engine.

  • Add a new JIRA Issue to the People-Ops board to track completion of onboarding tasks.
    • Create Bulk Sub Tasks on the new issue and use the Login.gov Onboarding Buddy Tasks template.
  • Request that the new user to be invited to the 18F org on GitHub in #admins-github on Slack. Cc @github-admins-slack on your request.
  • Create a new issue in the identity-devops Github repository using the onboarding template and ping @login-devops-oncall in Slack to alert them to the new onboarding issue.
  • Schedule a daily pairing session in GCal for an hour or two. Use the time to walk through project details, cooperate on environment setup, work on a ticket, etc. Taper off in a way that makes sense to you and your buddy.
  • Give intro to weekly ceremonies and team workflow
  • Request Slack access with ServiceNow
    • Federal employees are added as full Slack members by default.
    • Contractors who are working on TTS projects most or full-time can be added as full Slack members.
    • Other collaborators should be added as multi-channel guests.
    • Full Slack access for Contractors is at the discretion of Login.gov’s Contracting Officer. Please see TTS Handbook guidance for more info.
  • Add to appropriate Login.gov Slack groups like login-feds or login-appdev-team.
  • Using the JIRA Portal, choose Application Access and request a new JIRA account. Under Access Details ask that they be added to the Login.gov project.
  • Approve their PR to update team.yml with their info
  • Verify their membership in all appropriate Google Groups. This will grant them permission to see the Login.gov Team Drive and other Google Docs
    • Add everyone to login-all@
    • Add feds to login-team@, and contractors to login-team-contractors@
  • Update the Login.gov org chart
  • Verify they have been added to all team events like
    • Sprint ceremonies
    • All-hands / Demo-day
    • Retros / IRLs
  • Add user to Figma if appropriate (e.g. on UX team or implementing interfaces)
  • Help your buddy double check that they have a Performance Plan in HRLinks
  • Ensure that your buddy has working VPN access. For contractors the request originates with our CO.
  • Ensure that your buddy’s lead has 30, 60, and 90 day check-ins scheduled with the new employee. Any concerns during these reviews should be raised to the Contracting Officers Representative or the employee’s supervisor.

For non-GSA employees

Physical access to GSA HQ at 1800 F

Any government employee or contractor can present a PIV card to the guards to gain access to the building.

To get card-reader access to the building, visit OMA Security and have them configure your PIV card to open the turnstiles. OMA Office Hours are Monday - Thursday 7:00 am - 3:30 pm, room B338.