(Internal) Gem demo instance next steps

General idea:

Gem is transitioning from using Greenhouse for recruiting to using Gem ATS for recruiting.

We will keep our recruiting Greenhouse instance around and use it as a demo instance. Specifically, we will connect it to a new demo-gem.com Gem team.

Data

All the real Gem recruiting data from Greenhouse will be in the demo-gem.com Gem team.

Any new data manually added to this Greenhouse instance will sync to the demo-gem.com Gem team.

We’ll still run the demo script that auto-generates fresh demo data; this will populate the demo-gem.com Gem team.

Permissions

Same as in the recruiting Greenhouse today. Also same as today, the permissions will reflect in Gem, specifically in the demo-gem.com Gem team.

Accounts

• You will have two email accounts: your existing name@gem.com and a new name@demo-gem.com
• Use name@gem.com on Greenhouse - this will log you into the recruiting Greenhouse instance.
• Use name@demo-gem.com on Gem - this will log you into the Gem demo team.
• Logging into Gem with name@gem.com will go to our live recruiting Gem team with Gem ATS

How to operationalize it:

SCs/GTM TODO list

• Wait for iulia to confirm all the pre-required engineering steps have been completed
• Log in to the recruiting Greenhouse and add name@demo-gem.com as a secondary email.
• Provision a Gem user for yourself on the demo-gem.com Gem instance
• Complete the “grant email permissions” flow after logging into Gem for the first time (to be able to send sequences).

Steps for deleting/adding an email (officialGH docs):

1. Go to Account Settings

1. Click the pencil icon to the right of Personal Information

1. Add name@demo-gem.com as a secondary email

1. Log in to you name@demo-gem.com email account and check for an email from Greenhouse asking you to verify the account.

• Data
• Permissions
• Accounts
• How to operationalize it:
• SCs/GTM TODO list