An agency recruiter account is tied to one or more Greenhouse organizations, and given access to different jobs and offices. Each Greenhouse organization is hosted on a database called a silo, which is used to store and protect your data. Greenhouse maintains multiple silos to ensure the stability and security of an organization's data.
If you are working with an organization based in the EMEA market, there is a chance they are hosted by Greenhouse's EU silo. Due to technical constraints, the EU silo is completely separate from its US counterparts. For most Greenhouse users, this is not a problem, since they are only accessing their organization that is hosted on a single silo.
However, since agency recruiters work with many Greenhouse customers, they may need to access organizations in both the US and the EU silos. In this case, the recruiter will need two separate Greenhouse Recruiting accounts to access the US and EU organizations.
See the following sections for more information:
Create an account for an agency recruiter
If you're getting an error when trying to add a recruiter to an agency, they may already have an account on another silo.
To create a new account on your silo, the recruiter will need to provide a new email address for the EU or US account.
Guide for recruiting agencies - creating two email addresses
If you need two separate email addresses to access each silo, follow your IT department's suggestions for how to maintain the two accounts. In some cases, your organization can create two accounts and manually link them to appear in the same inbox. However, the specific setup may differ based on your organization.
If you are using Gmail as your email provider, you can add a plus sign in the middle of your email address to make it appear as a unique address for applications, but Google will continue to send emails to the original email.
Example: If your Gmail address is email@example.com, you can create an account in Greenhouse Recruiting for both firstname.lastname@example.org and email@example.com. Applications will view greenhouse+us and greenhouse+eu as separate emails, but when a message is sent, it will automatically be sent to firstname.lastname@example.org.
Remember that the recruiter only needs one email address for the entire silo - so if they work with another organization that uses Greenhouse in the US or EU, they can use the same email address for both accounts.
Recruiter strategies for managing two Agency Portal logins
When you're using two agency portal logins, you should avoid opening both accounts in the same browser session (this includes opening them in separate tabs). Because of how webpage data is displayed, having two open tabs with different login information could cause errors when saving or trying to reload the page.
Check out the sections below on some alternative solutions on how to manage two agency recruiter accounts.
Use Google Chrome profiles to manage your browsing session
If you are using a Gmail account and Google Chrome to access Greenhouse Recruiting, you can sign in to your Google account in the top right corner of the page.
Google offers a feature called "Chrome Profiles," where you can open a unique browsing session for an account, which avoids the saving issues with multiple tabs. Click here for more info on adding profiles to your Chrome browser.
Using multiple browsers
If you open two separate browsers (such as Firefox and Chrome) and separately sign into Greenhouse Recruiting through those browsers, you can have both applications open on your computer without running into issues with saving. However, we understand this isn't an ideal solution if you're trying to organize multiple windows.
Use Greenhouse Recruiting in an incognito window
Google's incognito windows do not share any data between other open windows. By using different incognito windows, you can have multiple instances of Greenhouse Recruiting running without saving issues.
Note: Incognito windows are not limited to Google Chrome. All browsers have some form of private or incognito browsing, but they are named differently based on the application.