Onboarding Recruiters to a Shared Inbox: A Practical Playbook

Onboarding Recruiters to a Shared Inbox: A Practical Playbook

To onboard a recruiter to a shared inbox, do four things in order. Pick the access model (delegation or a true shared mailbox). Grant access and test it with the new person. Teach three or four ownership rules, so nobody answers the same candidate twice. Then give them a way to find CVs that does not depend on scrolling. This guide walks through each step for teams that receive applications at an address like jobs@ or careers@, with the checks that save you from the usual first-week mistakes.

TL;DR

• Choose the model first: Gmail delegation gives people access to one account, while a Google Workspace shared inbox or Collaborative Inbox adds role addresses and conversation assignment.
• Test access on day one with the new recruiter. Invitations expire after a week, and access can take up to 24 hours to appear.
• Write down ownership rules: who takes a conversation, how you mark it done, and who handles duplicates and unclear applications.
• Treat the inbox as a store of personal data: limit access, collect only what you need and keep CVs out of personal mailboxes.
• A shared inbox is a good intake channel but a weak database. Plan early for how recruiters will search past CVs.

Table of Contents

• Decide how recruiters will access the inbox
• Set up the mailbox before the new recruiter starts
• Day-one onboarding steps
• Ownership rules that prevent double replies
• Organize applications so new people can find things
• Protect candidate data from the first day
• Our perspective: the inbox is the intake, not the system
• When the shared inbox stops being enough
• A simple tool for the next step
• A 30-day onboarding plan
• FAQ
• Sources

Decide how recruiters will access the inbox

Most onboarding problems come from a vague setup. Someone shares a password, three people log in, and nobody knows who replied. Before you invite a new recruiter, decide which of three models you are using.

Google itself draws this line: delegation gives people or groups access to an account, while a Collaborative Inbox is a Google Group whose members can assign conversations and track them as tasks. If your team is two or three people who talk across a desk, delegation may be enough. If you have five recruiters and several open roles, you will want assignment.

Microsoft 365 teams have an equivalent in shared mailboxes. The onboarding logic below applies there too: grant access, test it, set rules.

Set up the mailbox before the new recruiter starts

Do the admin work the day before, not on the morning the recruiter arrives.

Use a role address, not a person

Applications should arrive at an address that survives staff changes. Google’s guide says an administrator creates the shared inbox in the Admin console, enters a role address such as sales@yourdomain.com, adds users and completes the setup. For recruiting, that means jobs@ or careers@ rather than someone’s own mailbox. When a recruiter leaves, you remove them as a delegate and the address keeps working.

Know the delegation limits

If you go with delegation, a few facts from Gmail’s delegation help page will shape your plan:

• The owner adds a delegate under Accounts and Import in Gmail settings, and the delegate accepts the invitation.
• Delegates can read, send and delete email. They cannot change the account password or access Google Account settings.
• A personal Gmail account can have up to 10 delegates, and a work or school account up to 1,000. Typical simultaneous access is 40 delegates.

Those ceilings are far above what most recruiting teams need. The practical constraint is not the number of people but whether they know what to do once they are in.

Decide what candidates will see

Google notes that sent messages can show the shared address and the delegate who sent them, and users with access can configure sender-information visibility and whether messages are marked read. Decide this on purpose. Many agencies prefer candidates to see the team address with the recruiter’s name in the signature. Whatever you choose, tell the new recruiter, so their first reply looks like everyone else’s.

Day-one onboarding steps

This is the checklist to run through with each new recruiter, ideally in a 30-minute session.

1. Send the invitation early. Google says invitations expire after a week, and access may take up to 24 hours. Send it two days before the start date so nothing is blocked on day one.
2. Watch them accept it. Have the recruiter accept the invitation and open the inbox through the account switcher, while you are present. This is the single most useful test, because it exposes browser profile confusion and missing permissions.
3. Check what they can and cannot do. Confirm they can read, reply and archive. Confirm they cannot change the password. If they need to, that is a request to the owner, not a workaround.
4. Send a test reply. Have them reply to a dummy application so you can see how the sender name and signature appear.
5. Walk through the labels and folders. Show how roles, stages and “needs review” are marked. Keep the list short enough to memorize.
6. Show them how to search. Teach the search operators your team actually uses: sender, attachment, role keyword, label.
7. Explain removal. Owners can remove delegates at any time. Telling new people this up front makes offboarding less awkward later.

If you need ready-made wording for first contacts once the recruiter is live, our recruitment email templates for each hiring stage save a lot of drafting.

Ownership rules that prevent double replies

The top complaint about shared inboxes, in any forum thread you read, is that two people answer the same email or nobody does. Technology helps, but the rules matter more. Teach these.

One conversation, one owner

In a Collaborative Inbox, Google says recruiters can take or be assigned a conversation, search for conversations assigned to them, mark it complete and unassign it to remove the assignment. Make “take it before you reply” the first rule. If you use plain delegation without assignment, replicate this with a label such as “Taken: initials” or a star color per recruiter.

Close the loop with a status

Google says Collaborative Inbox members can mark conversations complete, duplicate or no action needed, and search by assignee or resolution status. Those three statuses cover most recruiting traffic: a handled application, a candidate who applied twice, and a newsletter or spam message. Teach new recruiters to use them rather than leaving threads open.

Check the permissions behind the feature

Assignment fails quietly when permissions are wrong. Google says taking or assigning conversations requires the “Who can moderate metadata” permission, and viewing assignments requires “Who can view conversations”. If a new recruiter cannot see the Assign button, start there. Our guide on four shared inbox permissions recruiters must check goes through the same kind of checks for CVs and connected apps.

Set a response standard

Pick a response window, such as an acknowledgment within one business day, and write it on the first page of your onboarding document. A recruiter who knows what “on time” means does not need to ask.

Organize applications so new people can find things

A new recruiter’s biggest handicap is not knowing what happened before they arrived. Give them structure.

• Labels by role and stage. Use “Role: Warehouse Supervisor” and “Stage: Screening” instead of free-form tags.
• A rule for unsolicited CVs. Decide whether they go to a talent pool label, get a standard reply, or both.
• A rule for duplicates. Candidates often apply to several roles or send the same CV twice. Mark duplicates with a status, and link them to the earlier thread.
• A naming convention for attachments. If a candidate sends “CV.pdf”, you will not find it later. Save a renamed copy in your document storage, or rely on tooling that reads the attachment itself.

Google’s guide for the Collaborative Inbox setup adds that owners or managers must create or enable the features, turn on conversation history, add members and grant permissions for taking, assigning, completing or classifying conversations. Do that once, then document it, so you do not rediscover it each time someone joins.

For a deeper look at keeping files from slipping away, see how to manage resumes in a shared inbox without losing any.

Protect candidate data from the first day

A recruiting inbox holds names, phone numbers, addresses, work histories and sometimes health or family details volunteered in a cover letter. Each new recruiter gains access to all of it, so privacy training belongs in onboarding, not in an annual policy.

The UK Information Commissioner’s Office, whose guidance is a useful benchmark even if you are outside the UK, says recruitment organisations process candidates’ personal information, which may be sensitive. Its employment practices code adds that applicants should know what is collected and why, recruitment information should be used only for recruitment unless another purpose is clearly explained, and staff involved must understand the rules. It also says not to collect more than you need and to keep candidate information secure.

These laws are UK-specific. In the US, requirements vary by state and by the kind of data, so ask your counsel which rules apply to your applicants. The habits, though, travel well. Teach new recruiters to:

• Keep CVs in the shared inbox or your database, never in personal email or on desktops.
• Avoid forwarding candidate emails to personal addresses.
• Ask for only the information the role requires.
• Report a misdirected email immediately, rather than quietly deleting it.
• Never share the inbox login. Everyone uses their own access, so you can remove one person without touching the rest.

If you connect the inbox to other tools via IMAP, read our notes on IMAP recruiting setup for a shared CV inbox before you hand over credentials.

Our perspective: the inbox is the intake, not the system

We built RecrutFlo for teams that live in a shared mailbox, so we see the same pattern again and again. Onboarding goes smoothly for the first month. The new recruiter learns the labels, takes threads, replies. Then the volume grows, and the questions change. Did we already hear from this person? Which of the 400 applications last quarter mentioned Spanish and logistics experience? Nobody can answer from the inbox alone, because an inbox is organized by time, not by person.

Our view is that you should not force a team onto a new platform to fix this. Recruiters already work in email, and that is fine. What they lack is a layer that reads the CV attachments arriving in that mailbox, pulls out the contact details, skills, languages and location, and files them as searchable profiles. We keep the recruiter in control: the automation handles repetitive data entry, and people still decide who to call.

So when we advise a team on onboarding, we say: get access and ownership rules right first, because that is what stops double replies. Then decide early how you will search past candidates. If you wait until the inbox holds thousands of messages, the cleanup is painful. New recruiters also benefit more than anyone from a searchable database, because they have no memory of earlier applicants to lean on.

— Marco

When the shared inbox stops being enough

There are signs that onboarding rules alone will not hold:

• Recruiters keep asking “did anyone talk to this person before?”
• The same candidate appears under three role labels.
• Finding a CV means searching sender names and guessing at keywords.
• Someone retypes details from PDFs into a spreadsheet every week.
• A departing recruiter leaves behind knowledge that lives only in their sent folder.

At that point the fix is not more labels. It is a candidate database fed automatically from the inbox. Our write-ups on building a searchable candidate database for agency CV management and searching CVs received by email describe what that looks like in practice. If intake is the bottleneck, automating candidate intake from your hiring inbox is the next step.

A simple tool for the next step

RecrutFlo connects to your existing inbox (Microsoft 365, Outlook and IMAP today, with Gmail coming), spots CV attachments in incoming emails, extracts candidate details from PDF, DOC and DOCX files, and flags duplicates. New recruiters get a searchable database on day one, with no onboarding call or implementation project. You can see how it works before signing up.

You can test the workflow on the Free plan. Paid plans on our pricing page start with Starter at €19 per month, then Professional at €49 per month and Business at €149 per month. If you run out of processing capacity, you can add runs one time: +100 for €9, +500 for €29 or +1,000 for €49.

A 30-day onboarding plan

Use this as a skeleton and adjust it to your hiring volume.

The week-four test is the one most teams skip. If a recruiter cannot find a candidate you know exists, you have a search problem, not a training problem.

FAQ

What is the difference between Gmail delegation and a shared inbox?

Delegation gives selected people access to one account: they can read, send and delete mail but cannot change the password. A Google Workspace shared inbox is created by an administrator around a role address. A Collaborative Inbox adds assignment and status tracking on top, through a Google Group.

How long does it take for a new recruiter to get access?

Plan for up to 24 hours after the invitation is accepted, according to Google’s delegation help. The invitation itself expires after a week, so send it a couple of days before the start date and test it together.

Should new recruiters share one login for the recruiting inbox?

No. Shared logins hide who did what, and they make offboarding messy because you must change credentials for everyone. Give each recruiter their own access to the shared address, so you can remove one person without disrupting the team.

How do we stop two recruiters from replying to the same candidate?

Make taking a conversation the first step before replying. With a Collaborative Inbox, use assignment and statuses. Without it, use a label or color per recruiter and review open threads in a short daily check.

How many people can have delegate access?

Google says a personal Gmail account can have up to 10 delegates and a work or school account up to 1,000, with typical simultaneous access of 40. Most recruiting teams are well under those numbers.

Sources

• Create a shared inbox, Google Workspace Admin Help
• Delegate and collaborate on email, Gmail Help
• Delegate and collaborate on email, Gmail Help (UK)
• Take and assign conversations, Google Groups Help
• Make a group a Collaborative Inbox, Google Workspace Help
• Employment practices and data protection: recruitment and selection, ICO
• Quick guide to the employment practices code, ICO

Recommended

• How to Manage Resumes in a Shared Inbox Without Losing Any
• IMAP Recruiting Setup: Connect a Shared CV Inbox Safely
• 4 Shared Inbox Permissions Recruiters Must Check, From CVs to Apps
• How to Automate Candidate Intake From Your Hiring Inbox