Greenhouse manages several silos to host customer data. Every silo manages Greenhouse Recruiting accounts for many customers, with each customer in a given silo sharing network and system resources.
What is a silo?
A silo is an environment where organizations' Greenhouse Recruiting accounts are hosted. All Greenhouse Recruiting accounts in a given silo share backend resources, and experience updates and maintenance simultaneously. While all accounts within a silo share system resources, the actual customer-owned data within those accounts is never shared or accessible by other organizations in the silo.
As the Greenhouse customer base grows, we create additional silos to support new organizations. Adding more silos prevents a single silo from ever hosting an outsized number of accounts, ensuring your organization maintains the same level of performance regardless of how many total customers use Greenhouse Recruiting.
Note: Each silo functions individually and does not overlap with other silos, but all silos function identically. Greenhouse provides the same resources and support to every silo.
When the Greenhouse team first creates your brand new Greenhouse Recruiting account, the account is added to a silo that currently has space to support an additional organization. This assignment is permanent; organizations are never moved from one silo to another.
What silo does my organization use?
To determine which silo your organization uses, navigate to your Greenhouse Recruiting Dashboard page and review the bottom-left corner. Your silo is listed here.
Example
In the above image, the organization's Greenhouse Recruiting account is in Silo: 1.
Identify silo-specific site-wide issues
Most of the time, your organization's silo will not impact anything about your work in Greenhouse Recruiting. However, in the event of a system incident, knowing your silo can help confirm if your organization's account is impacted.
If you suspect you might be impacted by a current issue, navigate to the Greenhouse Status page: https://status.greenhouse.io.
From the Greenhouse Status page, one of three scenarios is most likely:
- Greenhouse is fully functional with no active incidents
- An isolated incident has been identified and is impacting one or more specified silos
- A system-wide incident has been identified and is impacting all silos
To check for silo-specific issues, click the + icon next to a product or feature.
From the subsequent dropdown, review your silo's status.
If you suspect you are experiencing an incident that has not yet been reported / posted to the Greenhouse Status page, please Greenhouse Support.
Silo-specific email addresses
The Greenhouse Recruiting features listed below rely on silo-specific email addresses. In most cases, your organization's silo-specific email address is appended automatically when you trigger one of these features.
If you start one of these processes manually (such as adding a candidate via Maildrop, or setting up interviews via manual scheduling), be sure to select the appropriate email address for your assigned silo. Your requested action will not complete successfully if an incorrect email address is used.
|
Silo |
Assigned email address |
| Silo: 1 | maildrop@rose.greenhouse.io |
| Silo: 2 | maildrop@ivy.greenhouse.io |
| Silo: 3 | maildrop@fern.greenhouse.io |
| Silo: 4 | maildrop@lily.greenhouse.io |
| Silo: 5 | maildrop@iris@greenhouse.io |
| Silo: 6 | maildrop@peat.greenhouse.io |
| Silo: 7 | maildrop@kelp.greenhouse.io |
| Silo: 101 | maildrop@mint.greenhouse.io |
|
Silo |
Assigned email address |
| Silo: 1 | FlyOnTheWall@rose.greenhouse.io |
| Silo: 2 | FlyOnTheWall@ivy.greenhouse.io |
| Silo: 3 | FlyOnTheWall@fern.greenhouse.io |
| Silo: 4 | FlyOnTheWall@lily.greenhouse.io |
| Silo: 5 | FlyOnTheWall@iris.greenhouse.io |
| Silo: 6 | FlyOnTheWall@peat.greenhouse.io |
| Silo: 7 | FlyOnTheWall@kelp.greenhouse.io |
| Silo: 101 | FlyOnTheWall@mint.greenhouse.io |
|
Silo |
Assigned email address |
| Silo: 1 | schedule@rose.greenhouse.io |
| Silo: 2 | schedule@ivy.greenhouse.io |
| Silo: 3 | schedule@fern.greenhouse.io |
| Silo: 4 | schedule@lily.greenhouse.io |
| Silo: 5 | schedule@iris.greenhouse.io |
| Silo: 6 | schedule@peat.greenhouse.io |
| Silo: 7 | schedule@kelp.greenhouse.io |
| Silo: 101 | schedule@mint.greenhouse.io |