Here are 3 Google Admin tricks that will save you time when onboarding (and offboarding) team members.
Note that I’m making some assumptions here
- You are likely a Google Apps for Business Super Admin
- You geek out on system architecture and system settings
- Your company probably doesn’t yet have a dedicated IT team
- Your company has an all@ (or everyone@) Google Group
- *Your company has team specific Google Groups
- Your company has a Calendar for company and/or team events
- Your company has a company Drive folder and/or team Drive folders
- Your company has G Suite Basic
*The last two tricks can be used without team specific Google Groups!
Today’s onboarding process
- A new team member is hired and you create an email address
- Add the email address to a team Google Group, say team@
- Add the email address to a general Google Group, say all@
- Navigate to Google Calendar
- Find team events that the email address should be included in
- Add the email address to each individual event
- Navigate to Google Drive
- Find documents that should be shared with the team member
- Individually share each document (or folder) with that individual
That’s a lot of work for 1 new team member. Now imagine 10x’ing or 20x’ing that. Suddenly, onboarding just Google products is a full-time job. Eek.
Tomorrow’s onboarding process
- A new team member is hired and you create an email address
- Add the email address to team@
- (1) The email address is automatically added to all@
- (2) The email address is automatically added to all team and company Calendar events
- (3) The email address is automatically added to all relevant Drive folders (and files)
These simple tricks will help you turn that >9 step process into 2.
Here’s how to do it
(1) Automatically update all@ by nesting your Google Groups
A Group can be added to another Group a member, just like an email address.
For example:
- Create your team groups, say team-a@ and team-b@
- Chose “Team” access level: “Only managers can invite new members, but anyone in your domain can post messages, view the members list, and read the archives.”
- Do NOT check the box “allow anyone on the internet to post messages”
- Add each team member to their correct group
- 1 team member per team group
- Create your company-wide group, say all@
- Add team groups to all@
It looks like this:
(2) Automatically update Calendar events by adding Groups to events as guests
A Google Group can be added to a Calendar event as a guest, just like an email address.
Here’s what your all-hands Calendar event could look like:
Here’s what your team meeting events could look like:
(3) Automatically update Drive folder viewing and editing permissions with Groups
Last, but not least, a Google Group can be added to a Drive folder to set the level of viewing and editing access for that folder, also just like an email address.
The structure could look like this:
- Company Drive Folder : all@ view only access, yourname@ edit access
- Team A Drive Folder : team-a@ view and edit access
- Team B Drive Folder : team-b@ view and edit access
- Everyone in all@ can VIEW what’s in the Company Drive Folder, including what’s in:
- Team A Drive Folder
- Team B Drive Folder
- You can EDIT what’s in the Company Drive Folder, including what’s in:
- Team A Drive Folder
- Team B Drive Folder
- Team members in team-a@ can EDIT what’s in the Team A Drive Folder
- Team members in team-b@ can EDIT what’s in the Team B Drive Folder
Here’s what your company drive folder could look like:
As a bonus, this structure gives all and only the right team members editing access to folders. When a company hits 100 employees, you start to see files and folders go missing because it’s too easy to move things around in Drive without training... and who has time to spend on that?!
Troubleshooting and caveats
Nesting Groups
- Set an alert so you know when someone accidentally removes themself from their group:
- Reports > Groups > Event Name > Select “User removed from a group” > Hit “Set Alert”
- I don’t recommend nesting non-team groups, e.g. inbound support tickets, inbound bills
- They should be kept separate since they are for non-team specific communication
- Plus, it tends to introduce spam into email, which leads individuals to unsubscribe from the group
- When you’re creating a new team group, check to make sure the members update in Calendar
- If they don't, remove and re-add the team group to the parent group in Google Groups and check again
- You’ll still need to share the link to the Company Drive Folder with the new team member, ideally in their onboarding email
More of My Preferred Google Admin Settings
There are so many stories behind each of these. I’ll save you the read time and give you a list
Enforce 2-step verification
- Security > Advanced security settings > Authentication > 2-step verification > Enforcement > Turn on enforcement now or from date
- Apps > G Suite > Settings for Groups for Business > Sharing Settings > Creating Groups > Only domain admins can create groups
- Apps > G Suite > Settings for Drive and Docs > Link sharing > OFF - Only the owner has access until they share the file
- Home > Directory > Users > Manage Organizational Units > Create a new organizational unit
- Separate full-time, contractors, and non-people email addresses
- Apps > G Suite > Settings for Gmail > Advanced Settings > End User Access > Automatic Forwarding > Don’t Check “Allow users to automatically forward incoming email to another address”
- Alls > G Suite > Settings for Drive and Docs > Features and Applications
- I LOVE multiple inboxes ;)
A big shout-out to Jane Stecyk and Kim for editing! I couldn't do it without you. If you have questions or want more information on any of these settings or my reasons for loving them, leave a comment below and I’ll answer. Thanks for reading!
Leia Rollag is OrgOrg's Resources Lead. She recently launched OrgOrg's Annual Compensation and Benchmarking Survey and re-designed the orgorg.co/forum webpage. She is currently a consultant designing consistent compensation practices that rely on market data and previously was the Director of People Operations at IFTTT. She specializes in operationalizing Human Resources and Total Rewards for software technology companies. |