This article answers common questions related to technical set-up for Tezi.
What Google Workspace permissions does the Tezi app require?
What Google Workspace permissions does the Tezi app require?
To understand Tezi’s permissions requests, it can be helpful to first understand what Tezi is. Tezi’s product is a fully autonomous AI recruiting partner named Max. Max works directly with hiring managers and recruiting teams to drive end-to-end recruiting for assigned roles, including autonomously reaching out to and responding to candidates, scheduling interviews, and screening candidates.
One way to think about onboarding Max is that it is similar to onboarding a contract recruiter. Max emails candidates on behalf of the company, so it needs an email address on your company domain. It schedules interviews so it needs a calendar to schedule on. It schedules video calls so it needs Google Meet. Other than that, it needs no access to your company's resources or apps.
To enable Max's full functionality, technical set-up for Tezi involves:
Creating an email address for Max on your company's main domain (max.tezi@[yourcompany].com) so that Max can email candidates
Providing max.tezi@[yourcompany].com access to the following Google services:
GMail, so that Max can email candidates
Google Calendar, so that Max can book interviews
Google Meet, so that Max can attach video conferencing to interview invites
Providing the Tezi app the following Google Calendar permissions:
Full access to max.tezi@[yourcompany].com's calendar so Max can schedule and manage interviews. Scope:
https://www.googleapis.com/auth/calendar
Tezi Support will briefly log in as max.tezi@[yourcompany].com (see next FAQ response) to grant the Tezi app’s request to manage the account’s calendar.
View access to users’ calendars so Tezi can consider their availability when scheduling interviews. Scope:
https://www.googleapis.com/auth/calendar.readonly
Max will prompt users to grant calendar access when they are added as interviewers.
Configuring DNS records so that Tezi can use SendGrid to send sourcing emails from Max's subdomain on your company domain (i.e., sourcing emails are sent from an email address that looks like max.tezi@mail.[yourcompany].com, not max.tezi@[yourcompany].com)
In our instructions on how to set up email for Max, we very narrowly limited access for Max’s user account and the Tezi app. We welcome alternative permissions set-ups as long as they support 1-4 above.
Will Tezi's service interactively log in as max.tezi@[yourcompany].com at any time?
Will Tezi's service interactively log in as max.tezi@[yourcompany].com at any time?
The Tezi service will not log in as the service account at any time. Tezi Support will need login access only for 2 things:
To complete technical setup (e.g., grant the Tezi app read/write access to max.tezi@[yourcompany].com’s calendar). This is a one-time task.
To occasionally debug and resolve candidate correspondence and interview scheduling issues. For example, in complicated cases where the AI cannot complete scheduling, Tezi Support may log in to view interviewers’ availability directly and schedule the interview.
To ensure your organization's security, our instructions on how to set up email for Max suggest creating the max.tezi@[yourcompany].com account in a highly restricted OU with only the access Tezi needs to function and support your company’s recruiting needs. If set up according to our instructions, this account will not have access to Google Drive or any third-party software that your organization uses. We also securely store all credentials in a 1Password vault with heavily restricted internal access, and we use 2-step verification.