Employee Onboarding: Get New Hires Into the Right Groups on Day One

A new engineer's first day usually goes like this. Their laptop works and they can sign in to Google and Slack. Then the small failures start. They're not in #team-platform, so they miss the standup thread. Nobody added them to @platform, so they don't see the "welcome Priya" message. GitHub says they don't have access to the repo they're supposed to be onboarding into. Jira won't show them the team's board. Each fix takes one Slack message and twenty minutes of waiting, and the new hire spends their first week asking for access instead of learning the codebase.

None of this is about accounts — those usually work. It's about groups. This post covers how to make group membership on day one automatic, so a new hire who lands in the right directory group ends up in the right place in every tool.

The two halves of onboarding

It helps to separate:

1. Accounts. Does the person exist in Google Workspace, Slack, GitHub, Jira, PagerDuty? This is identity provisioning, usually driven by an HR system or an IdP, or by IT creating accounts from a checklist.
2. Group membership. Is the person in the right Slack user groups and channels, GitHub teams, Jira groups, Zoom groups, and eventually PagerDuty teams? This is where most day-one friction actually lives.

Many companies have solved the first half reasonably well and still do the second half by hand. That's the half this post is about.

Step 1: Pick one place where team membership is decided

Group sync only works if there's a single answer to "which team is this person on?" For most companies that answer belongs in the directory:

• Google Workspace: a Google Group per team (platform@, support@, sales-emea@).
• Microsoft Entra ID: a security group per team.

The person who adds a new hire to that group — IT, People Ops, or the hiring manager — is effectively deciding everything downstream. Make that step part of the hiring checklist, not an afterthought.

Dynamic groups: let attributes decide

Both directories can populate groups automatically from user attributes like department or cost centre, so adding a new hire to the HR system or directory with the right department is enough. Licensing applies (as of 2026):

• Google Workspace dynamic groups are available on Enterprise Standard and Plus, Education Standard and Plus, Frontline Standard and Plus, Enterprise Essentials Plus, and Cloud Identity Premium, per Google's admin help.
• Microsoft Entra dynamic membership groups require a Microsoft Entra ID P1 license for each unique user who is a member of one or more dynamic groups, per Microsoft's documentation.

If you don't have those editions, static groups maintained as part of the hiring checklist work fine. The point is that there's one group per team, in one place.

Step 2: Map each team group to everything it should unlock

Write down, per team, what membership should mean in every tool. A simple table is enough:

Directory group	Slack user group	Slack channels	GitHub team	Jira / Atlassian	Other
platform@	@platform	#team-platform, #platform-alerts	platform	platform group + Platform team	Zoom group
support@	@support	#team-support, #escalations	—	jsm-agents group	—
sales-emea@	@sales-emea	#sales-emea, #deals	—	—	Zoom group
everyone@	—	#announcements	—	—	—

This table is your onboarding spec. If a row is hard to fill in, that's a sign the team boundaries in your tools don't match the org chart — worth fixing regardless of automation.

Leave on-call out of day-one onboarding. New engineers shouldn't be paged in their first week. Add them to PagerDuty or Opsgenie teams deliberately when they start shadowing; see Keep PagerDuty teams in sync with Google Groups for that step.

Step 3: Make the mapping automatic

This is where a group sync tool replaces the checklist. SyncMyGroup keeps destination groups matching a source group across Google Groups, Microsoft Entra ID, Slack user groups and channels, GitHub teams, GitLab, Jira / Atlassian groups and teams, PagerDuty, Opsgenie / JSM Ops, Linear and Zoom.

For each row of your table:

1. Connect the directory (Google Workspace or Entra ID) and each destination tool at app.syncmygroup.com.
2. Create one sync per destination: platform@ → @platform, platform@ → #team-platform, platform@ → GitHub platform, and so on.
3. Preview each one. On existing teams, the preview also shows who is in the destination but not the source — people your onboarding process added by hand and nobody ever removed.
4. Add permanent users where someone should always be present regardless of the roster, such as a team's manager in a leadership channel.
5. Turn on notifications.

From then on, adding a new hire to platform@ is the whole onboarding step for groups. Each destination picks them up, provided their account exists in that tool.

Announce arrivals where the team will see them

SyncMyGroup's Slack bot posts every addition and removal to a channel you choose: run @SyncMyGroups subscribe <team> in the channel (Slack or Microsoft Teams). For onboarding, subscribing #it-ops gives IT a live feed of new hires landing in groups, and a team can subscribe its own channel so "Priya added to @platform" shows up where people will say hello.

Step 4: Handle the timing

The awkward part of onboarding is that accounts don't all exist at the same moment.

• Google account created a week before start date. Adding them to platform@ early means they appear in Slack groups as soon as their Slack account exists. If you'd rather they didn't, add them to the team group on day one, or use an exclusion until their start date.
• Slack account created on day one. A sync can only add someone to a Slack group once they have a Slack account. Make sure your Slack provisioning (SSO just-in-time, SCIM, or invite) happens first thing.
• GitHub account depends on the person. Engineers often bring a personal GitHub account and need to accept an org invitation. Plan for a short delay and make the identity mapping part of IT's checklist; How to sync GitHub teams with Google Groups covers the details.
• Matching is by email. Every tool's account should use the person's work email. Mismatches are the most common reason someone "didn't get added".

Step 5: Treat onboarding and offboarding as the same system

Once team groups drive everything, the same mechanism handles the other two lifecycle events:

• Movers. Someone switches from support to platform: move them from support@ to platform@ and every downstream group follows — including the removals people usually forget.
• Leavers. Remove them from their team groups and they're removed from every synced Slack group, channel, GitHub team and Jira group. Account deactivation is still a separate step. See The offboarding gap.

The mover case is where manual onboarding does the most damage. People collect access from every team they've ever been on, and nobody files a ticket to remove it.

A day-one checklist, after automation

Before day one	Owner
Directory account created with the correct department/team	IT / People Ops
Added to the team group (or dynamic group rule covers them)	IT / hiring manager
Slack, Jira, GitHub accounts provisioned with the work email	IT
Day one
Confirm notifications show the new hire landing in each group	IT
Hiring manager confirms channel and repo access in the first hour	Manager
Week two or later
Add to on-call team when shadowing starts	Team lead

Short enough to actually follow.

What it costs

SyncMyGroup is free up to 5 users with every integration and 24x7 Slack support, and the Starter plan is $2 per user per month with unlimited users (pricing). It's built to avoid the enterprise SCIM tiers that some tools require for group provisioning.

FAQ

Do I need an HR system integration to automate onboarding groups?

No. The key is one directory group per team. Whether your HR system populates it, a dynamic group rule does, or IT adds people by hand as part of the hiring checklist, group sync takes it from there.

What if a new hire doesn't have a Slack account yet when they're added to the Google Group?

A sync can't add a user who doesn't exist in the destination tool. Once their Slack account exists with the same email, they'll be picked up on a later sync. Provision Slack early on day one.

Should new hires be added to on-call groups automatically?

Usually not. Add people to on-call teams deliberately when they start shadowing. Keep on-call group membership as a separate decision from team membership.

Can the same group drive Slack, GitHub and Jira at once?

Yes. Create one sync per destination from the same source group. See the workflow list for supported pairs, such as Google Group → GitHub and Google Group → Jira.

---

Map your first team in a few minutes at app.syncmygroup.com, or book a walkthrough.