An email alias is a separate, independent email address that you connect to Recruiterflow. Aliases are useful for warming up a new domain, splitting outreach by purpose, or sending from a shared team email address, all without paying for another user seat.
What an alias is
An alias is its own email account, with its own inbox, separate from your primary mailbox. You connect it to Recruiterflow directly — the same way you'd connect any mailbox — so you can send from it inside Recruiterflow. It's a sending and receiving address, not a login: connecting an alias doesn't grant Recruiterflow user access.
How to add an alias
Go to Settings → Profile.
Click Add Alias.
Enter the First Name, Last Name, and the alias's Email, then choose the platform it's hosted on — Google Workspace or Office 365.
Click Connect next to the new alias to grant sending permissions, then approve the OAuth prompt from Google or Microsoft.
You'll see a confirmation once the alias is live. It's now selectable as a From address anywhere you send email in Recruiterflow.
Where you can use an alias
Profile emails — one-off emails sent from a candidate or contact record
Campaigns and Sequences
Recipes
Practical example
A recruiter running high-volume outreach to passive candidates wants to keep it separate from their main inbox. They set up a dedicated mailbox — outbound@theirfirm.com — with its own inbox, connect it to Recruiterflow as an alias, and set it as the From address inside a campaign. Outreach goes out through that address, and replies land in its own inbox, separate from the recruiter's primary mailbox.
Things to know
One alias maps to one user. For a shared team address, see Using Shared Aliases in Recruiterflow.
An alias needs to be its own independent email account, with its own inbox, before you connect it — you can't set one up as an extension of your existing mailbox.
Admins can see every alias set up across the workspace.
Aliases can't log into Recruiterflow — connecting one only enables sending and receiving from that address; it doesn't grant user access.
If your domain or DNS provider blocks the OAuth grant, the Connect step will fail. Ask your IT admin to whitelist the Recruiterflow OAuth scope and try again.
Related articles