Permission	Use case
Sign in and read user profile	To enable the admin to sign in via oAuth to the Chezie app.
Team.Read.Group Read this team’s metadata	Allows the app to read this team’s metadata, without a signed-in user
TeamMember.Read.Group Read this team’s members	Allows the app to read the members of this team, without a signed-in user
OnlineMeetingParticipant.Read.Chat Read the participants of the meetings associated with this chat	Allows the app to read participant information, including name, role, ID, joined and left times, of meetings associated with this chat, without a signed-in user
TeamsActivity.Send.Chat Send activity feed notifications to users in this chat	Allows the app to send auto-welcome messages to new members
Member.Read.Group Read this group’s members	Allows the app to read the basic profile of this group’s members, without a signed-in user
TeamsActivity.Send.User Send activity feed notification to this user	Allows the app to create new notifications in the teamwork activity feed of this user, without a signed-in user

\n\n## **Chezie Microsoft Teams Integration – Common IT Q&A**\n\n### **Who is the “user” when actions are logged?**\n\n- **Calendar events:** The service account (e.g., [**ergs@company.com**](mailto:ergs@company.com)) is always the user. Events will show that account as the organizer.\n\n- **Teams meetings:** The organizer remains the service account, but the Chezie app identity is what accesses meeting attendance data, since Microsoft Graph requires application permissions for that.\n\n- **Teams channels:** The “user” is the account that authenticated with the Chezie app (for example the service account). Chezie only has access to the channels that this account itself has access to. To avoid tenant-wide approval, the recommended setup is to grant the service account access only to ERG-related channels. As a result, Chezie can listen to or sync activity only for those channels.\n\n### **Why do I see two permission dialogs during setup?**\n\nBecause there are two flows:\n\n- **Delegated permissions** tied to the service account, which allow calendar and channel actions in the scope of that account.\n\n- **Application permissions** for the Chezie app identity, which are required only for Teams meeting attendance and similar background tasks.\n\n### **How does Chezie get access to Teams channels?**\n\nThe Teams channel URL maps each ERG in Chezie to a specific Teams channel. The service account you configure with Chezie must already have access to those channels. Chezie then uses the delegated permissions of that authenticated account to interact with those channels. Because the service account is scoped only to ERG-related channels, Chezie never has visibility into tenant-wide Teams data.\n\n### **What events are logged for Teams channels?**\n\n- Chezie logs ERG membership changes (join or leave) inside Chezie.\n\n- If the service account has the correct channel permissions, these changes are synced with the connected channel.\n\n- Messages and activity are only logged if the relevant Graph permissions are granted, and always limited to channels that the authenticated service account can access.\n\n### **What does “app identity” mean in this context?**\n\nApp identity refers to Chezie acting as the registered application in your Azure directory, not as an admin or employee. It applies only when application-level permissions are needed, such as reading Teams meeting attendance. For channels, Chezie relies on the authenticated service account’s delegated permissions and channel access.\n\n### **Does Chezie need tenant-wide permissions?**\n\nNo. Tenant-wide permissions like Group.ReadWrite.All are not required. By scoping the service account’s access to only ERG-related channels, Chezie can function without tenant-wide approval.","2026-04-16T19:07:11.308Z","2026-04-17T19:14:47.496Z","d5a8c3a4-c3e9-40b3-a832-6dfe29a589b7",[],[],[],"Microsoft/Outlook Calendar","microsoftoutlook-calendar","## **How the Microsoft Calendar integration is used**\n\nThe Chezie MS Calendar integration allows you to:\n\n- Create events and distribute calendar invites to the people invited to them (in-group members, all employees, etc.).\n\n- Update calendar invitations if an event is changed\n\n- Cancel calendar invitations if an event is canceled\n\n- Track user responses to calendar invites (accepted invite, declined invite, tentative)\n\n## **How to connect your Microsoft Calendar account**\n\n### **Service account requirements**\n\nThe application primarily uses:\n\n1. **Calendar** – requires exchange online\n\n2. **Teams (Teams for Business)** – for online meetings\n\nThe service account should, at the minimum, **have a Microsoft 365 Business Basic license.**\n\n### Creating your service account\n\nFrom your Azure Admin portal, please create a new user. We suggest giving the user the following information\n\n- **First name**: \\[Company]\n- **Last name**: ERGs/BRGs/etc. (whatever your company calls your Groups)\n- **Email**: \n\n### Connecting the service account (2026)\n\n1. Log into Chezie via https\\://\\[customername].chezie.io\n\n2. Click _**Settings**_\n\n3. Click _**Integrations**_ under company settings\n\n4. Click _**Add account**_ under Microsoft Calendar integration\n\n ![CleanShot 2026-05-05 at 12.31.19@2x.png](/api/knowledge-base/images/72f2e363-a63b-422e-820c-ce7f8ef8c3f9)\n\n5. Complete the oAuth process.\n\n6. If you see this screen, then the application needs to be approved by an admin to complete the connection. Complete steps 6-13.\n\n![](/api/knowledge-base/images/235e2098-f376-4937-8878-0734caf2b092)\n\n6. You will be prompted to accept permissions requests, select **Accept.**\n\n![](/api/knowledge-base/images/2c433b8c-a968-4128-90a7-983dfed8c255)\n\n7. At this point, your integration should be complete.\n\n8. If you gave your service account admin privileges before starting the process, you can remove those privileges in your Azure portal.\n\n9. Go back to your Azure directory and click _**Enterprise Applications**_ → _**Chezie**_.\n\n Click the button to **Grant Admin Consent for Default Directory**. This enables automatic attendance tracking for MS Teams ERG events.\n\n![](/api/knowledge-base/images/a27c56f0-f8e4-4619-9456-9c379c216829)\n\nWhen you click the Grant admin consent button, you’ll see another screen like this. Sign in with your own admin account (not the service account), to accept the permissions.\n\n![](/api/knowledge-base/images/e0c8e7ab-bfa2-41f0-b2bf-224e320b6f0e)\n\n10. Now, you should see a screen with the following permissions:\n\n![](/api/knowledge-base/images/5dba9990-bc12-4e6b-9ce2-3cb5e5932cb4)\n\n11. Delete all of the highlighted Delegated permissions.\n\n![](/api/knowledge-base/images/9412c75f-b5bf-40d6-bb50-7d2dafe0e56e)\n\n12. Confirm that only the two permissions in the image below are visible for the Chezie application. If your screen looks like this, then you’re done.\n\n![](/api/knowledge-base/images/b0e57126-05bb-4a66-adaa-8c6cf11c00db)\n\n13. Email to confirm that you’ve completed the setup. Thank you!\n\n## **Microsoft Calendar Integration - IT Details**\n\n### User role to install app\n\nOwner and Contributor.\n\n### Scopes\n\nMicrosoft scope reference page [here](https://learn.microsoft.com/en-us/graph/permissions-reference).\n\n**Calendar permissions**\n\n![Screenshot 2026-08-26 at 12.20.17 AM.png](/api/knowledge-base/images/95bb3dfb-1dc2-4c32-8caa-b3bb2fa002f0)\n\n**Online meeting permissions**\n\n![Screenshot 2026-08-26 at 12.21.15 AM.png](/api/knowledge-base/images/972008d6-6b75-47e5-ba2b-6626f6ea9b61)\n\n**Online meeting application permissions**\n\n![Screenshot 2026-08-26 at 12.22.00 AM.png](/api/knowledge-base/images/655fe3e4-bc28-4a37-967f-0d22e6f02238)\n\n## Troubleshooting\n\n### **For Error Mailbox Not Enabled for Rest API:**\n\n**Make sure the tenant has a Microsoft 365 plan**\n\nIf none already have a Microsoft 365 subscription, you must purchase one from Microsoft or a certified reseller. Choose a plan that includes Exchange Online, such as Microsoft 365 Business Basic, Microsoft 365 Business Standard, or Microsoft 365 Enterprise plans.\n\n**Assign License to User**\n\nOnce you have the Microsoft 365 license, you can assign it to the user whose mailbox needs to create the online meeting. Here's how admin:\n\n1. Go to the Microsoft 365 admin center (.[microsoft.com](http://microsoft.com/)) and sign in with your admin credentials.\n\n2. In the admin center, go to the \"Users\" or \"Active users\" section.\n\n3. Find the user for whom you want to enable Exchange Online (the mailbox user).\n\n4. Select the user and then click on \"Edit\" or \"Product licenses\" (the wording may vary depending on the admin center's version).\n\n5. In the license assignment window, check the box for the Microsoft 365 license that includes Exchange Online (e.g., Microsoft 365 Business Basic, Microsoft 365 Business Standard).\n\n6. Save the changes.\n\n**Verify Mailbox Setup**\n\nAfter assigning the license, the mailbox should be automatically set up for Exchange Online. You can verify this by checking the user's mailbox settings in the Microsoft 365 admin center or by accessing the Exchange admin center.\n","2026-04-16T19:06:43.592Z","2026-08-27T13:29:00.131Z","406bf0b2-b938-420a-a5a7-e8d3e71f357e",[],[],[],"Integration data flow","integration-data-flow-chezie-2","Below is a diagram of how the integration data is used. This includes SSO, Directory, Calendar, and Video.\n\n![Chezie for ERGs - Overview.png](https://firebasestorage.googleapis.com/v0/b/trnout-co.appspot.com/o/u-chezie-wg8g5%2Fknowledge-base%2Ff05f0d76-07c2-4946-a127-128f64b0bb20.png?alt=media)\n\n![](https://6445cdb19af5e6e8088a0f92.featurebase-attachments.com/c/article/68139259e7186c84ae7eb007/01968c74-f12e-7380-a16b-d2124f1199f1/b64u-Q2hlemllIGZvciBFUkdzIC0gT3ZlcnZpZXcucG5n.png?X-Amz-Expires=3600&X-Amz-Date=20260416T190000Z&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260416%2Ffra1%2Fs3%2Faws4_request&X-Amz-SignedHeaders=host&X-Amz-Signature=a373e5144d16d28cb8d3ac2babe7f75c38823d00828fec17898f5dbee11d67fa)","2026-04-16T19:06:46.902Z","2026-04-17T19:11:15.834Z","33ba55c8-e84d-41cf-a874-c0c49be52e4d",[],[],[],"How to connect your Calendar Integration","how-to-connect-calendar-2026","1. Log in to your portal - \\[companyname\\].chezie.io\n\n2. Click **Settings**![CleanShot 2026-05-27 at 12.37.20@2x.png](/api/knowledge-base/images/6fd219d6-9072-47eb-966f-875180765494)\n\n3. Click **Integrations**![CleanShot 2026-05-27 at 12.37.26@2x.png](/api/knowledge-base/images/25ba78b7-508e-4b9b-bf07-a958e64bc090)\n\n4. Select Add account under the calendar provider that your company uses\n\n ![CleanShot 2026-05-27 at 12.37.31@2x.png](/api/knowledge-base/images/87d44d0d-f7fa-4750-b42d-7d0ea99b0681)\n\n5. Proceed with the OAuth process.\n\n > ***Note***: The application will appear as [nylas.com.](http://nylas.com) Nylas is the sub-processor we use to handle our calendar integration.\n\n6. When you see the Connected Accounts calendar has gone from 0 to 1 (or increased by 1), the integration is complete.\n\n ![CleanShot 2026-05-27 at 12.40.19@2x.png](/api/knowledge-base/images/110c8a3c-674d-4191-b722-54f39bdb9a2e)\n\n# FAQs\n\n1. **Do we need to do anything to reconnect our calendar integration?**\n\n Yes. The calendar integration will need to be reconnected in the new Chezie environment. This is done by your Chezie admin (not IT), directly from the Integrations page inside the new platform after your first login. No new service account or IT action is required in most cases — you'll just re-authorize using the existing account you set up originally.\n\n2. **Why does it ask for admin approval when we try to reconnect the calendar?**\n\n Because the new Chezie platform is technically a new application, your organization's IT policies may require an admin to approve the OAuth connection before it goes through. This is the same approval your IT team gave when you first connected Chezie. You'll need to reach out to the person who handled that original setup and ask them to approve the new app. This is a one-time step.\n\n---\n\n**Do we need a dedicated service account for the calendar integration? Can it be the same one we used before?**\n\nYes, you can reuse the same service account. You don't need to create a new one. The reconnection process just re-authorizes the existing account in the new environment. If your organization uses a dedicated calendar account for ERG events (e.g., `ergs@yourcompany.com`), that account should be used again during reconnection.\n\n---\n\n**We use Microsoft Calendar/Teams. Are there any special steps for us compared to Google Calendar users?**\n\nThe reconnection process is the same for both Google and Microsoft. One thing to be aware of: if your Microsoft tenant has restrictions on third-party app authorizations, your IT team may need to approve the connection — see the question above about admin approval. Also note that if you use Microsoft Teams for video meetings, you do **not** need to set up a separate video integration — Teams is handled automatically through the Microsoft Calendar connection.\n\n---\n\n**We use Zoom (or Webex) for video. Does that need to be reconnected too?**\n\nZoom and Webex integrations will also need to be reconnected in the new environment. If you have a custom or enterprise-level video integration, please let us know in advance — some of these require additional setup time and we may need to discuss your specific configuration. Google Meet and Microsoft Teams are handled through the calendar integrations and do not need separate reconnection.\n\n---\n\n**What happens to events that were already created in the old platform?**\n\nEvents created before your migration cutoff date will remain visible but will no longer be editable within the Chezie platform after that date. If you need to make changes to a pre-migration event, you can edit it directly in your service account's calendar (Google Calendar or Outlook). We'll give you a specific cutoff date ahead of your migration window so you can plan accordingly — ideally, avoid scheduling new events in the old platform once you've been given a migration date.\n\n---\n\n**After the calendar is reconnected, will attendance tracking still work?**\n\nYes. Once the calendar integration is reconnected in the new environment, attendance will be captured automatically for events created through the platform, the same way it worked before.","2026-05-27T16:38:16.274Z","2026-08-27T13:28:59.009Z","38efed2d-84cc-4e4e-a031-d0e7a24bf70b",[],[],[],"How Chezie works with your other tools (and what those tools control)","how-chezie-works-with-your-other-tools-and-what-those-tools-control","*Chezie connects to your calendar, video, email, and identity/HRIS tools so events, invites, attendance, and member data work automatically.*\n\n---\n\n# For Group/Chapter Admins\n\n## The calendar invite shows the wrong name\n\n**What you'll see:** Invites to your event arrive showing a generic name — like \"Acme ERGs\" or even \"IT SSO Owner\" — instead of your specific group's name.\n\n**Why:** The name attendees see comes from the service account your IT team used to connect the calendar integration, not from a setting inside Chezie. Every Group’s invites send from that same shared account.\n\n**What you can do:**\n\n- The quickest fix in your control: put your group's name in the **event title** (e.g., \"BE Network ERG — Coffee Chat\"), so it's clear in the invite regardless of the sender name.\n- To change the actual sender name, your IT team can rename the service account (e.g., to \"Acme ERGs\"). If invites are showing an IT admin's name, the integration may have been connected with the wrong account — reconnecting with the intended service account fixes it.\n\n**Who owns it:** Your IT team.\n\n## I can't get the attendance report, or attendance is missing\n\n**What you'll see:** No attendance data for an event, or you can't open the Attendance tab.\n\n**Why:** Chezie captures attendance automatically only when the event uses the **connected Zoom or Teams integration**. If the event was set up with a personal meeting link (the video provider was set to \"Other\"), the meeting ran outside the integration, so there's nothing for Chezie to pull — and the attendance data lives in the account that owns that link.\n\n**What you can do:**\n\n- Always create events using the connected integration rather than pasting a personal Zoom/Teams link.\n- If an event already used a personal link, you can still get the data: pull the attendance report from Zoom or Teams directly, then upload it to Chezie. See [How to upload attendance for a past event](https://docs.chezie.co/docs/chezie-2026/events-3/how-to-upload-attendance).\n\n**Who owns it:** Shared — use the integration to keep it automatic; otherwise the meeting host owns the data.\n\n## Where's the meeting recording?\n\n**What you'll see:** You're looking for a recording of an ERG event and expect to find it in Chezie.\n\n**Why:** Chezie schedules and tracks meetings, but it doesn't record them and doesn't store recordings.\n\n**What you can do:**\n\n- Recordings live in your video platform. Contact your **service account admin** for access.\n- If a Host Key was used to start the meeting, Zoom typically sends the recording link directly to whoever hosted.\n\n**Who owns it:** Your video platform (Zoom/Teams/Webex) and its admin.\n\n## Some members didn't get the email, or it went to spam\n\n**What you'll see:** You send a communication, Chezie confirms it sent, but a few people say they never received it — or it landed in spam.\n\n**Why:** Chezie hands every message to your email provider and confirms it was sent successfully. After that, whether a message reaches the inbox is decided by the **recipient's mail system** — spam filters, quarantine rules, and security settings that Chezie can't see or override.\n\n**What you can do:**\n\n- Ask recipients to check spam/junk and to add your sending address to their safe senders.\n- For company-wide delivery issues, your IT team can allowlist Chezie's sending domain.\n- If you can name one or two people who definitely didn't receive it, send those to support — concrete examples let us trace exactly what happened.\n\n**Who owns it:** The recipient's email system / your IT team.\n\n## Why is my big event email taking so long to arrive?\n\n**What you'll see:** For large groups, some members get the email right away and others get it noticeably later.\n\n**Why:** To protect deliverability, Chezie sends large batches gradually (a short gap between each message) rather than all at once. This is intentional — sending thousands of emails simultaneously gets flagged as spam. Delivery isn't instant for everyone, but it does complete.\n\n**Who owns it:** This is expected Chezie behavior, by design.\n\n## Add to Calendar isn't working in Outlook\n\n**What you'll see:** The \"Add to Calendar\" option downloads an `.ics` file, but it doesn't add cleanly to the new version of Outlook.\n\n**Why:** An `.ics` file is a standard calendar file, but how it's opened and added is handled by the recipient's calendar app — and some newer Outlook versions handle it inconsistently.\n\n**What you can do:** Members can open the `.ics` file manually, or rely on the calendar invite that the integration sends directly (which doesn't depend on the `.ics` download). If you're hitting this often, flag it to support.\n\n**Who owns it:** The recipient's calendar application.\n\n---\n\n# For IT Admins\n\n## The service account, and why reconnection sometimes matters\n\n**What you'll see:** Invites suddenly stop sending, attendance stops being captured, or an integration shows as \"disconnected.\"\n\n**Why:** Chezie's calendar and video integrations run on the service account your team connected. That connection can lapse — most commonly because a **Microsoft API token expires (about every 2 years)**, or because someone disconnected/reconnected the integration with the wrong login. When the connection lapses, automated invites and attendance pause until it's re-established.\n\n**What you can do:**\n\n- Reconnect using the **intended service account**, not an individual admin's login. (For Microsoft, approving with an admin account can configure the integration to use that admin's identity instead of the service account.)\n- If the service account uses SSO, make sure whoever reconnects can actually sign in as it.\n\n**Who owns it:** Your IT team.\n\n## Microsoft permission scopes and automatic attendance\n\n**What you'll see:** During setup you may be asked for scopes like `OnlineMeetings.Read.All` and `OnlineMeetings.ReadWrite.All`, and your security team may want to limit them.\n\n**Why:** Those scopes power **automatic** attendance capture (Microsoft's change-notifications for meetings aren't available with narrower delegated permissions today).\n\n**What you can do:** If your security policy requires it, you can revoke those scopes — attendance still works, but it becomes a **manual pull** after each event (an admin goes into Chezie and retrieves attendance per event) rather than automatic. It's a trade-off, not a breakage.\n\n**Who owns it:** Your IT/security team.\n\n## HRIS attributes (department, location, level) aren't showing\n\n**What you'll see:** Member records or report filters are missing HRIS attributes like department or location.\n\n**Why:** Those attributes flow into Chezie only if your identity/HRIS system is configured to send them and the integration user retains access. Common causes: Okta isn't mapped to share those fields, or a Workday custom report was moved, unshared, or lost access for the integration user.\n\n**What you can do:**\n\n- Confirm your IdP/HRIS is configured to pass the attributes you want into Chezie to WorkOS.\n- For Workday specifically: keep the integration user's reports shared with it, ensure its security group still has GET access to Worker/Person data, and re-run the reports after any change.\n\n**Who owns it:** Your IT/HRIS configuration.\n\n## Login problems and wrong-identity sign-ins\n\n**What you'll see:** A member logs in and sees no group memberships, or gets an SSO error.\n\n**Why:** Identity in Chezie comes from your SSO. If someone is signed in under the wrong email/domain (for example, they have accounts on two domains), Chezie shows the records tied to that identity — which may not be the one with their memberships.\n\n**What you can do:** Have the user sign in with the correct account/domain. Persistent SSO errors are resolved in your identity provider, not in Chezie.\n\n**Who owns it:** Your identity provider (SSO). *Related: [SAML SSO](https://claude.ai/cowork/local_ec55bac3-8365-49be-b632-8c330601bdbb#).*\n\n## Changes made directly on the connected calendar\n\n**What you'll see:** An event that's still approved and active in Chezie is missing from attendees' calendars.\n\n**Why:** If someone edits or cancels the event **directly on the service account's calendar** (outside Chezie), that change happens in your calendar system, not in Chezie — so Chezie still shows it as active while the calendar entry is gone.\n\n**What you can do:** Check the event on the service account calendar first. Treat the service account calendar as something only designated people should modify.\n\n**Who owns it:** Your calendar system / whoever has access to the service account.\n\n---\n\n# The short version\n\n| You expected to control in Chezie… | It's actually controlled by… |\n| --- | --- |\n| Invite sender / organizer name | Your service account (IT) |\n| Meeting recordings & host keys | Your video platform + its admin |\n| Automatic attendance | The connected integration (personal links break it) |\n| Whether an email reaches the inbox | The recipient's mail system |\n| HRIS attributes in member data | Your IdP/HRIS configuration |\n| Who a member is logged in as | Your SSO / identity provider |\n\nIf you're not sure which side a given issue sits on, reach out to support — we'll help you figure out whether it's a Chezie setting or something on your connected tools, and point you to the right person on your team.","2026-06-30T19:26:52.743Z","2026-08-27T13:28:57.701Z","a72538c4-4deb-4665-a1ef-27c15b3f2b2b",[],[],[],"Google Calendar","google-calendar","## **How the Google Calendar integration is used**\n\nThe Chezie Google Calendar integration allows you to:\n\n- Create events and distribute calendar invites to the people invited to the event (in-group members, all employees, etc.)\n\n- Update calendar invitiations if an event is changed\n\n- Cancel calendar invitiations if an event is cancelled\n\n- Track user responses to calendar invites (accepted invite, declined invite, tentative, etc.\n\nTo use Google Calendar, you will need to create a generic ERG user account under your company's Google Admin dashboard (i.e. [ERGS@chezie.co](mailto:ERGS@chezie.co)).\n\n## Scopes\n\n`Please note that the scopes below are only granted for the service account you use for the Chezie integration. We do not access profiles for any other Google accounts within your organization. `\n\n| Scope | Description | Additional detail |\n| --- | --- | --- |\n| .../auth/[userinfo.email](http://userinfo.email) | See your primary Google Account email address | |\n| .../auth/userinfo.profile | See your personal info, including any personal info you've made publicly available | |\n| .../auth/[calendar.events](http://calendar.events) | View and edit events on all your calendars | To create, update, and cancel events from our application. Changes made within Chezie will reflect in the calendar event on the user's calendar and update the invites that have been sent to attendees. |\n\n## **How to connect your Google Calendar account**\n\nTo connect your Google Calendar account, follow these instructions: \n\n## **How to Handle Authorization Error: “Error 400: admin_policy_enforced”**\n\nIf a Chezie user tries to link their service accounts, they may receive an error message stating an Authorization issue with the code \"Error 400: admin_policy_enforced\". It's important to note that this error is unrelated to Chezie itself, but rather stems from the restrictions set by a G Suite administrator to limit access to Google Workspace data by third-party applications.\n\nIn order to fix the error, the G-Suite administrator must grant access to Chezie. If you have access to the Google Admin console using your account, you can make these changes yourself. Otherwise, please reach out to the administrator of your organization and request them to follow these steps.\n\nFollow the steps below in order to manage the authorization error and access your Chezie integrations.\n\n1. **If a user attempts to connect a Chezie integration on their GSuite domain and encounters an 'Authorization Error' as shown below**\n\n![](https://fb-usercontent.fra1.cdn.digitaloceanspaces.com/0195005b-dd3a-7bf1-8fb0-a73cec7d4569.png)\n\n2. **The Admin user should log into their Google GSuite/Workspace Admin console, navigate to the Security section in the menu bar > select API Controls > and then click on Manage Third-party App Access**\n\n![](https://fb-usercontent.fra1.cdn.digitaloceanspaces.com/0195005d-bfce-70c9-a56f-52cdf0ee3658.png)\n\n3. **Click on “Add App” and then “OAuth App Name Or Client ID“**\n\n![](https://fb-usercontent.fra1.cdn.digitaloceanspaces.com/0195005e-2cf7-7f6e-905f-f4063176a80e.png)\n\n4. **Type in the search bar “Chezie“**\n\n![](https://fb-usercontent.fra1.cdn.digitaloceanspaces.com/0195005e-f0f3-733d-a9aa-e35125b30563.png)\n\n5. **Choose the option to authorize all apps**\n\n![](https://fb-usercontent.fra1.cdn.digitaloceanspaces.com/0195005f-541e-7303-a6b4-31dc3f806a96.png)\n\n6. **Select the radio button for “all users” under Scope**\n\n![](https://fb-usercontent.fra1.cdn.digitaloceanspaces.com/0195005f-b2e6-7b46-9c06-2c03bd5f2674.png)\n\n7. **Mark app as trusted**\n\n![](https://fb-usercontent.fra1.cdn.digitaloceanspaces.com/01950060-19fd-7b80-97eb-f02302ee6baf.png)\n\n8. **Click on the Finish button under Review**\n\n![](https://fb-usercontent.fra1.cdn.digitaloceanspaces.com/01950060-64ad-79e0-8a38-e377fe86e074.png)\n\nThis should resolve the Authorization issues experienced.\n\nIf you have any additional questions or require further assistance regarding the Error 400 error, please don't hesitate to reach out to our support team.","2026-04-16T19:07:11.042Z","2026-08-27T13:28:56.190Z","565e64d7-427b-4170-9cbf-c54123022a0f",[],[],[],"Email","email-chezie-2","### How the Chezie email functionality works.\n\n## Overview\n\nChezie uses SendGrid as the email-sending platform to handle various types of emails, including notifications, marketing emails, and other communications on **behalf of the users**. Our integration with SendGrid ensures that emails are delivered reliably and securely.\n\n## How It Works\n\n1. **Email Types**:\n\n - Notifications to employees\n\n - Messages to ERG (Employee Resource Group) members and leaders\n\n - Marketing communications\n\n2. **Customization**:\n\n - **Sender Name**: Customizable by user\n\n - **Subject**: Customizable by user\n\n - **Reply-to Address**: Customizable by user\n\n - **Reply-to Name:** Customizable by user\n\n - **Verified Sender Address/Sender email**: `app@chezie.co` (controlled by us)\n\n## DKIM Authentication\n\n**Chezie supports DKIM authentication for all emails sent through our SendGrid integration.**\n\n- **Verification**: Our implementation ensures that all outgoing emails are signed with DKIM, verifying the email's authenticity and integrity.\n\n- The DKIM signature is included in each email's header. The recipient’s email server can verify it using the public key published in our DNS records.\n\n## FAQ\n\n1. **How to verify if an email is DKIM authenticated?**\n\n - Check the email headers for the DKIM signature.\n\n - Use online tools or your email server's capabilities to verify the DKIM signature against the public key in our DNS records.","2026-04-16T19:06:47.129Z","2026-08-20T15:38:43.601Z","b7fcd815-454d-483e-bc2e-a47fe3b7a597",[],[],[],"Does Chezie have an API?","does-chezie-have-an-api","At this time, **Chezie does not have an API**. We are working on it. If you have certain data requests, please reach out to [support@chezie.co](mailto:support@chezie.co), and our team will see what they can do. ","2026-06-30T18:54:26.021Z","2026-08-27T13:28:53.361Z","e259b0b2-6478-46eb-9a26-2b107e7a3c5e",[],[],[],"Directory Sync Integration Overview","directory-sync-integration-overview-chezie-2","### How our Directory Sync integration works.\n\n```plaintext\nWhile working on our HRIS integration, we work with our customers to import their HRIS data directly into our system.\n```\n\n## WorkOS Overview\n\nWe utilize a third-party solution called [WorkOS](https://workos.com/directory-sync) to offer a directory sync integration via SCIM.\n\nFind documentation for commonly used directories below:\n\n- [Azure AD (Entra)](https://workos.com/docs/integrations/entra-id-scim)\n\n- [Google](https://workos.com/docs/integrations/google-directory-sync)\n\n- [Okta](https://workos.com/docs/integrations/okta-scim)\n\n- [Workday](https://workos.com/docs/integrations/workday)\n\n## **How the HRIS data is used**\n\nTo ensure that ERG leads and Admins can schedule company-wide events and track company-wide engagement, we use the HRIS data to create placeholder user accounts for employees. As employees log-in, these placeholder accounts are deleted and replaced with the user's actual account.\n\nHere is an architecture diagram of how the HRIS data is used:\n\n![](/api/knowledge-base/images/6fe50eb3-2d77-465b-aee9-d8a38173f7d0)\n\nAn image of how the HRIS data is used.\n\n## **What HRIS data do you use?**\n\nWe do not intake any personal identifiable information (PII). Here are the fields that we will capture with our HRIS integration/from the exports from your HRIS system:\n\n- First Name\n\n- Job Title\n\n- Last Name\n\n- Email\n\n- Start date\n\n- EmployeeID (optional)\n\n- Selected HRIS attributes (ex: Level, Department, Unit, Location, Office)\n\n```plaintext\nThese are attributes that the Admins will be able to make visible for reporting and sending targets communications/events.\n```\n\n# **HRIS Data Transfer Using SFTP**\n\n```plaintext\nWe also offer SFTP as an option for transferring your HRIS file, in addition to pre-signed URLs (below).\n```\n\n## **Connection Details**\n\n- **Authentication:** Key-based only — we don't support password login.\n- **Host:** [sftp.chezie.io](http://sftp.chezie.io)\n- **Port:** 22\n- **IPs to whitelist:** 3.213.216.51, 3.219.3.70, 3.216.131.83, 3.219.98.225, 35.173.159.53, 35.175.92.86\n- **Staging path:** Your user will be confined to its own home directory — just drop your file there.\n\n## **Setting Up Your Connection**\n\n1. **Send us your public key.** Since we use key-based authentication, share your SSH public key with your Chezie contact and we'll add it to your account.\n2. **We'll provision your account.** We'll create a dedicated SFTP user for your organization and confirm your credentials and home directory path.\n3. **Upload your file.** Drop your HRIS file into your home directory on your agreed-upon cadence.\n\nFor any questions regarding SFTP setup, please contact our support team - .\n\n## **HRIS Data Transfer File Exchange**\n\nTo facilitate secure and cost-effective HRIS data transfers, we use AWS S3 pre-signed URLs. This method provides the same level of security as traditional SFTP while significantly reducing operational costs.\n\n## **File Exchange Method: Signed URLs**\n\n### Security\n\nSigned URLs offer robust security comparable to, if not exceeding, traditional SFTP transfers.\n\n- **Time-Limited Access:** Each signed URL is valid only for a specific period, ensuring access expires after the defined timeframe.\n\n- **No Persistent Credentials:** Unlike SFTP, which requires storing and managing access credentials, signed URLs eliminate the need for persistent authentication, reducing potential security vulnerabilities.\n\n- **Controlled Access:** URLs are generated with specific permissions and can be restricted by IP address or other conditions to enhance security.\n\n- **Encryption:** All data uploaded via signed URLs is encrypted in transit and at rest using AWS's built-in security features.\n\n### **Ease of Use for IT Teams**\n\nFrom an IT operations perspective, the workflow remains the same as with SFTP.\n\n### **Process Overview**\n\n1. **Receive Signed URL:** We generate a secure, pre-signed URL and provide it to your team.\n\n2. **Upload the HRIS File:** Your team uploads the HRIS file using the provided URL. This can be done manually or automated within your existing processes.\n\n3. **Repeat on a Regular Cadence:** The only requirement is to send the file at the agreed-upon frequency, just like with SFTP.\n\n### **Reasoning**\n\nUsing signed URLs significantly reduces costs while maintaining the same security and ease of use.\n\n- **Lower Cost:** No need to maintain expensive SFTP infrastructure.\n\n- **Simplified Access Control:** No need to manage SSH keys or long-term credentials.\n\n- **Improved Security:** Short-lived credentials minimize the risk of unauthorized access.\n\nFor any questions regarding signed URLs or implementation, please contact our support team - .\n","2026-04-16T19:06:45.905Z","2026-08-27T13:28:31.525Z","c76b8272-e8cf-4495-b831-2e39d6fc9851",[],[],[],"Azure (SAML)","azure-saml-chezie-2","### How to use our Azure SAML integration for SSO.\n\n```plaintext\nConnect your company's Microsoft Calendar account to distribute meeting invites to guests and track people's responses to calendar invites\n```\n\n## **How the Azure SAML is used**\n\nAzure SAML SSO is the means by which your employees are authenticated to Chezie. Benefits of using Azure SAML SSO include:\n\n1. **User Convenience**: Simplified login with a single set of credentials.\n\n2. **Enhanced Security**: Strong authentication and reduced password risk.\n\n3. **Centralized Access Control**: Unified management of access policies.\n\n4. **Improved Productivity**: Faster and seamless access to applications.\n\n5. **Compliance**: Helps meet regulatory and security requirements.\n\n6. **Cost Savings**: Reduces support and password-related costs.\n\n7. **Customization**: Allows for branding and user interface customization.\n\n## How to Configure SAML SSO in Microsoft Azure\n\nTo configure SAML SSO in Microsoft Azure, follow these steps:\n\n1. **Create and Register an Application**: Register an application in Azure AD that will represent your SAML SSO integration. This application will be used to configure the SAML settings and permissions.\n\n![azure screenshot 1.png](/api/knowledge-base/images/f982bce5-d0d3-44b4-98a0-a777997f3303)\n\n2. **Establish a SAML SSO method:** Within the newly created app and under Single sign-on, select SAML.\n\n![](https://fb-usercontent.fra1.cdn.digitaloceanspaces.com/019500ee-2aa5-724f-8ebe-59f724bf91a1.png)\n\n3. **Configure SAML Settings and Mapping**: In the application's settings, locate the SAML settings section. Provide the necessary information such as the Identifier (Entity ID), Reply URL, and Sign-On URL. These values will be provided by Chezie. This step involves mapping the user attributes from Azure AD to the corresponding SAML attributes required by Chezie.\n\n```plaintext\nRequired attributes are first name, last name, email Please map these values as first_name, last_name, and email, respectively.\n```\n\n![](https://fb-usercontent.fra1.cdn.digitaloceanspaces.com/019500ee-addd-75d9-8bd0-4392a6ab2ca3.png)\n\n4. **Download and Share Metadata**: Download the SAML XML metadata file from Azure AD. This file contains the necessary information about your SAML SSO integration. Share this metadata file with Chezie.\n\n![](https://fb-usercontent.fra1.cdn.digitaloceanspaces.com/019500ef-167e-7f87-b76c-288a5544ed29.png)\n\n5. **Test and Verify**: Test the SAML SSO configuration by initiating a login request from Chezie. Ensure that users can authenticate successfully and that the required user attributes are passed correctly.\n\n6. **Enable SSO**: Once the SAML SSO configuration is tested and verified, enable SSO for the desired users or groups. This step ensures that users are redirected to the SAML SSO login page when accessing the Chezie team via email.\n\nBy following these steps, you can successfully configure SAML SSO in Microsoft Azure for your integration with Chezie. Remember to consult the documentation and support resources provided by both Azure and Chezie for more detailed instructions and troubleshooting guidance.","2026-04-16T19:06:46.745Z","2026-04-28T19:55:24.101Z","85f59074-63c3-4815-a812-2dfef094b0d8",[],[],[],"Goals","goals-3","2026-08-26T18:27:15.537Z","194a675c-2cda-4dfe-84f1-0f1ab0bedf53",[640,641,642],[],{"_57":661,"_103":662,"_112":-5,"_113":663,"_115":637,"_116":62,"_117":664,"_119":665,"_22":666,"_24":25,"_122":667,"_124":-5,"_125":668,"_127":669},{"_57":652,"_103":653,"_112":-5,"_113":654,"_115":637,"_116":62,"_117":655,"_119":656,"_22":657,"_24":25,"_122":658,"_124":-5,"_125":659,"_127":660},{"_57":643,"_103":644,"_112":-5,"_113":645,"_115":637,"_116":62,"_117":646,"_119":647,"_22":648,"_24":25,"_122":649,"_124":-5,"_125":650,"_127":651},"How to edit a goal","how-to-edit-a-goal-chezie-2","### Instructions on how to edit a goal.\n\n1. From the Home Page, click ‘Goals’.\n\n ![1.png](/api/knowledge-base/images/28c66ded-102f-41f6-9030-84cc8f2e78bd)\n\n\n2) Select the owner of the goal you want to edit.\n\n ![2.png](/api/knowledge-base/images/6ea7b18d-71f2-4dbf-9a90-3dd81d5fe330)\n\n\n3. Click the menu beside the goal you want to edit and click Goal Settings.\n\n ![3.png](/api/knowledge-base/images/2604e5ee-c86a-4bcd-b9c6-bd4339c7da9b)\n\n\n4) Make the changes and click Save.\n\n ![4.png](/api/knowledge-base/images/48624c1c-64a8-463a-a209-3440db0daaea)","2026-04-16T19:06:39.644Z","2026-08-26T18:43:16.718Z","09b2420c-60ce-4d1d-8144-068a37b738d2",[],[],[],"How to delete a goal","how-to-delete-a-goal-chezie-2","### Guidance on how to delete a goal.\n\n1. Go to Goals\n\n ![1.png](/api/knowledge-base/images/c9695d9f-022b-4785-8302-60e8714c5151)\n\n\n2) Select the owner of the goal you want to delete.\n\n ![2.png](/api/knowledge-base/images/f9f72e1b-ee39-4c4a-9202-71fb62a8d717)\n\n\n3. Click the three dots then click ‘Delete’.\n\n ![3.png](/api/knowledge-base/images/8ba804ac-df9a-437b-b03c-a3c887204b7e)\n4. Confirm deletion.\n\n ![4.png](/api/knowledge-base/images/0e9af71d-5c19-42de-8841-35aa585169d2)","2026-04-16T19:06:39.873Z","2026-08-26T18:33:13.588Z","e023a00a-3cdc-44dc-817c-6c5662f24a55",[],[],[],"How to create a goal","how-to-create-a-goal-chezie-2","### Step-by-step guide on how to create a goal in Chezie.\n\n## **What’s the purpose of goals?**\n\nGoals are designed to help you track the impact of your employee resource group activity. By creating a goal and adding activity to said goal (such as expenses, communications, or events), ERG owners have a way to more clearly state the intention and overall impact of the work they are doing.\n\n1. From the Home Page, click 'Goals'.\n\n ![1.png](/api/knowledge-base/images/330926f0-cd75-42d1-b5ec-c17370c5480a)\n\n\n2) Choose the group you are creating the goal for.\n\n ![2.png](/api/knowledge-base/images/0d5cea0b-7155-40e8-a0db-66f26899348f)\n\n\n3. Click Add Goal.\n\n ![3.png](/api/knowledge-base/images/0d7fafca-44bc-49b5-a555-073c9ce80246)\n\n\n4) Fill in the details of your goal. Click Create once done.\n\n ![5.png](/api/knowledge-base/images/9c1ba79e-4afc-4df6-b4fa-eb8623d6668f)","2026-04-16T19:06:38.397Z","2026-08-26T18:44:47.704Z","75ec6f10-888d-43dd-9634-7b3a659a79f6",[],[],[],"Getting Started","getting-started","sparkles","2026-06-30T16:00:49.868Z","2026-06-30T16:01:00.778Z","3d3bbf1d-a2d7-4d40-b453-365a374fc905",5,[679,680,681,682,683],[],{"_57":718,"_103":719,"_112":-5,"_113":720,"_115":675,"_116":62,"_117":721,"_119":722,"_22":723,"_24":25,"_122":724,"_124":-5,"_125":725,"_127":726},{"_57":710,"_103":711,"_112":-5,"_113":712,"_115":675,"_116":62,"_117":713,"_119":713,"_22":714,"_24":25,"_122":715,"_124":-5,"_125":716,"_127":717},{"_57":701,"_103":702,"_112":-5,"_113":703,"_115":675,"_116":62,"_117":704,"_119":705,"_22":706,"_24":25,"_122":707,"_124":-5,"_125":708,"_127":709},{"_57":692,"_103":693,"_112":-5,"_113":694,"_115":675,"_116":62,"_117":695,"_119":696,"_22":697,"_24":25,"_122":698,"_124":-5,"_125":699,"_127":700},{"_57":684,"_103":685,"_112":-5,"_113":686,"_115":675,"_116":62,"_117":687,"_119":687,"_22":688,"_24":25,"_122":689,"_124":-5,"_125":690,"_127":691},"What is Chezie?","what-is-chezie","Chezie is an all-in-one community management platform built for employee communities — ERGs, volunteer groups, interest groups, local chapters, and more. Whether you're an employee looking to get involved, a group leader running day-to-day operations, or an admin overseeing an entire program, Chezie gives everyone the tools they need in one place.\n\nThere are three types of users on Chezie, each with their own dedicated experience and permissions:\n\n1. **Community Members**\n\n Chezie makes it easy to explore and join the communities that matter to you. Browse groups by type, check out their landing pages, see upcoming events, and join in just a few clicks. Once you're in, you'll get a welcome email, access to the group's messaging space, and you'll be automatically added to the distribution list — so you're always in the loop on calendar invites and updates.\n2. **Group and Chapter Admins**\n\n Chezie gives you everything you need to run your community from one easy-to-use platform. Manage your members, plan and promote events, track your budget, send communications, and view reports on your group's impact — all without juggling multiple tools. You'll have full visibility and control over your group, and your group only.\n3. **Team Admins**\n\n Chezie gives you a bird's-eye view of your entire program — and the ability to zoom in when you need to. Monitor activity across all your groups, track membership, communications, events, and budget from the top down, or drill into individual groups for a closer look. You can also set up approval workflows to keep your program compliant, and pull reports that show the real ROI of your communities.\n\n---\n\nNo matter your role, Chezie is designed to make community feel effortless — for the people joining, the leaders running them, and the teams supporting it all.","2026-06-30T16:02:13.831Z","bae93a04-3b21-4350-b036-3dc95d4755cf",[],[],[],"Upgrade guide","upgrade-guide","The Chezie 2026 platform is a rebuilt version of the product — faster, more flexible, and designed to scale with your organization. Most of what you knew still works the same way, but a few things have moved, a few work differently, and there are some genuinely new capabilities worth knowing about.\n\nThis guide walks through everything so your first session on the new platform isn't a scavenger hunt.\n\n---\n\n# What's new?\n\n## Teams: multiple communities in one platform\n\n**Teams** is a new feature that lets organizations run separate sub-instances (for example, ERGs, a volunteer program, and a mentorship program) all within a single Chezie platform. Each team has its own groups, events, and branding, but shares the same admin layer and HRIS connection.\n\n![image.png](/api/knowledge-base/images/1b72041e-884a-4f4f-bdb6-6eba00e16142)\n\n## Filter your member list by HRIS attributes\n\nYou can now filter your group's member list using data from your HRIS integration — things like department, location, or job level. Useful for understanding representation within a group or targeting communications to a specific segment.\n\n![image.png](/api/knowledge-base/images/a1810de8-542c-48e3-8d26-c01a3619449a)\n\n## Connect your own Zoom account\n\nGroup admins can now connect a personal Zoom account instead of relying on the default service account. This gives you more control over meeting links and host settings for your events.\n\n> **Note:** This is only available for Zoom, not Google Meet or Microsoft Teams, and requires your IT team to have enabled the Chezie app in your company's Zoom workspace.\n\n![image.png](/api/knowledge-base/images/2b099f1a-317f-4537-9e70-c6a551b90bed)\n\n## More control over who gets invited to events\n\nThe **Invites** tab when creating an event now gives you three options: invite your full group, paste in specific email addresses, or send only to your group's admins. This makes it easier to run internal planning meetings or targeted events without a workaround.\n\n![image.png](/api/knowledge-base/images/a2aae9cc-4029-4661-a52f-34f4368492e1)\n\n## Feedback tab for NPS responses\n\nPost-event NPS submissions are now surfaced in a dedicated **Feedback** tab, making it easier to review member sentiment without digging through reports.\n\n![image.png](/api/knowledge-base/images/45bc60eb-1298-4337-a827-0333d1224429)\n\n## Easier sorting on lists\n\nWe've improved the sorting experience. Simply click the arrows next to the column that you want to sort by, and the list will sort automatically.\n\n![CleanShot 2026-07-08 at 12.20.20@2x.png](/api/knowledge-base/images/e923b50a-e45c-484d-a65c-9f2fbd0f4887)\n\n# Where did things move?\n\n## Member view is now called *Discover*\n\nThe tab your members use to browse groups and explore the platform has been renamed from **Member view** to **Discover**. Same functionality, new name — it better reflects what members are actually doing there.\n\n![image.png](/api/knowledge-base/images/62ea7a2e-5492-44f1-9e0f-c25ca81ce1fa)\n\n## Some actions now require selecting a group first\n\nIn the old platform, you could kick off certain actions (adding a member, creating an expense, sending a communication) from a top-level view. In Chezie 2026, you need to select a group first before taking those actions. This keeps data organized by group and prevents things from being created in the wrong context.\n\n![image.png](/api/knowledge-base/images/c2d62282-c637-4039-ba51-96415b64381c)\n\n## Join requests moved to the Members tab\n\nIf your group is private, join requests used to live at the bottom of the Settings page — easy to miss. They're now front and center in the **Members** tab, so reviewing and approving requests is part of your normal members workflow.\n\n![image.png](/api/knowledge-base/images/7789a7fa-d2f6-4b18-925b-a2e17e270704)\n\n---\n\n# What works differently?\n\n## Chapter admins now inherit access to the parent group\n\nPreviously, a Lead for a chapter group only had admin access to that chapter. In Chezie 2026, if a group has chapters, admins automatically have access to both the parent group and its chapters. This means fewer permission gaps and less back-and-forth when managing chapter-based ERGs.\n\n![image.png](/api/knowledge-base/images/aea92634-fa7d-4528-b63d-d3f8b375f18b)\n\n## Expenses must be cancelled before they can be deleted\n\nThis is the most common workflow change that trips people up. In the new platform, you can't delete an active expense directly — you need to cancel it first, then delete it. This prevents accidental removal of expenses still under review or tied to an event.\n\n![image.png](/api/knowledge-base/images/b8d70bd8-2afb-49b2-9270-bc43bb379e6b)","2026-06-30T19:28:02.987Z","2026-07-08T16:21:34.478Z","532560d5-6e7b-4297-b2c9-95cfb5071586",[],[],[],"Ideas from other Chezie customers","ideas-from-other-chezie-customers-chezie-2","# Ideas from other Chezie customers\n\nThe below section includes some creative ideas to boost ERG engagement and direct employees to Chezie from the people who have done it before → Chezie customers.\n\n## Make joining easy\n\n> ✒️ Case study: Chegg, Greenhouse\n\nLearning about and joining an ERG should be easy and intuitive (that’s part of the reason we made Chezie.)\n\nHere are four places to consider adding your join links:\n\n1. **Employee onboarding presentation**\n\n The prime time to get people to join your ERGs is within their first 30 days at the company. Work with your employee onboarding team to make sure that information about your ERGs is included in your onboarding materials. This can be as simple as a slide that lists all of the ERGs and QR codes or links to their individual join links.\n\n2. **Company intranet**\n\n While Chezie houses all of your ERG information, your employees probably turn to your intranet first for questions. If you don’t already, you should create a page on your intranet that houses some basic information about your ERGs and directs employees to join them by logging into Chezie.\n\n Some things to include on this page:\n\n 1. Why your ERGs exist\n\n 2. A list of your ERGs and their respective mission statements\n\n 3. Join links for each ERG\n\n **Note**: you don’t want too much information on this page because it will turn into another thing you have to manage. Simply use this as a redirect to let people know that your ERGs are hosted in Chezie.\n\n3. **DEI Slack Channel (pinned post)**\n\n Use the [pinned post](https://slack.com/help/articles/205239997-Pin-messages-and-bookmark-links) feature in Slack to stick a message about your ERGs to the top of a relevant Slack channel.\n\n Many companies have general DEI channels that employees are auto-added to. This is a great spot for your pinned post. Here’s how to do it:\n\n 1. From your desktop, hover over the message you'd like to pin.\n\n 2. Click the **three dots icon**.\n\n 3. Select **Pin to channel**, or **Pin** **to this conversation** in a DM.\n\n Example:\n\n![](/api/knowledge-base/images/c38994c7-d7c5-4e71-abfb-6521fc12c840)\n\n4. **In-office flyers with QR codes**\n\n If your company has a solid in-person presence, consider placing flyers for your ERGs where employees can see them. Again, don’t overcomplicate this. Place them in places like the restrooms, the kitchen and the coffeeroom, and by the entrance.\n\n Include QR codes that people can scan with their phones so they can quickly join an ERG from mobile!\n\n## Create FOMO (fear of missing out)\n\nOne of the best ways to boost membership is to make employees who aren’t members feel as if they are missing out on something by not being an ERG member.\n\nLike everything, there are levels to this.\n\n**Level 1** - Gate-keep event invites and informative/engagement emails.\n\nYou can gate-keep event invitations and email messages to only people who have joined the ERG. When employees start asking why they didn’t know about the event, you direct them to join the ERG via Chezie so they receive future invites.\n\nTo boost this, send summaries and/or feedback from the event in your Slack channels.\n\n**Level 2** - Recognize members of your ERGs publicly.\n\nPeople appreciate being recognized, especially publicly. If you’re able to recognize members of your ERGs in your company’s public forums - such as an all-hands or #general Slack channel - people who aren’t members will see that recognition and understand that by joining, they can be recognized, too.\n\n## Market at the Group level, not the program level\n\nYour ERGs are a product. Your job is to sell them to your customers (employees).\n\nThe thing is, people don’t buy products; they buy solutions. The problems that your employees are facing vary based on the employee, but the majority of your employees identify with one of the following:\n\n- Struggling to network with other employees\n\n- Seeking professional development opportunities\n\n- Gaining exposure to leadership\n\n- Finding volunteer opportunities\n\n- Learning about other cultures\n\nIf an employee is facing one of these problems, there’s an **ERG that can be the solution**.\n\nRead that again. There is an ERG (singular, not plural) that can be the solution. People aren’t signing up to participate in your company’s ERG program; they’re signing up to network or access resources as a member of one ERG. Don’t market the entire ERG program. Instead, market your ERGs individually and let members find the ERG (i.e. the solution) that best solves their problems.\n\n### How Lattice marketed their ERGs individually\n\n**About Lattice**\n\n[Lattice](https://lattice.com/) is an HR software platform that helps companies with an all-in-one solution for performance management, engagement, and an HRIS, sent a company-wide email\n\n**How Lattice increased its ERG membership by 13% in 24 hours with one email**\n\nMaurice Tuiasosopo Bell, Sr. Director of DEIB at Lattice, wanted to start 2024 off with a reminder to employees to join the company’s ERGs. His plan was to send a company-wide email to all employees to encourage them to join.\n\nThis isn’t new. Most companies sent blasts to employees to make them aware of the ERGs. Where Maurice zagged was that rather than telling employees all of the perks of joining Lattice’s ERG program, Maurice opted to include details about each individual ERG in the email so each employee knew that there was a group for them. He shared each ERG’s mission statement and embedded each ERG’s one-click join link into the email so employees could simply click the link and join the group they were most interested in.\n\nHere’s a template that’s based on the email that Maurice sent 👇🏾\n\n_\\._\n\n_**Subject:**_\n\n_DEI Announcement & Join an ERG!_\n\n_**Body:**_\n\n_Hi everyone!_\n\n_I want to use this opportunity to encourage you to join any of our Employee Resource Groups (ERGs). These are employee-led communities that aim to foster inclusion and belonging for employees from underrepresented and traditionally marginalized backgrounds, with a focus on building community, development opportunities, and cultural celebration. Click on the links below to join any of our ERGs:_\n\n- _**API**_ _\\ advocates and fosters a sense of inclusion dedicated to supporting the diverse and multicultural Asian & Pacific Islander employees through community, empowerment, and education._\n\n- _**Families at Lattice**_ _help parents and caregivers feel they can bring their whole selves to work as the providers of care for others — whether for a child, a family member, or community member._\n\n- _**ForEach**_ _makes a difference by supporting the development of community, personal growth, and continued learning for members of Lattice Engineering with underrepresented genders._\n\n- _**Latinx/é**_ _develops a supportive and uplifting network of employees to promote the cultural diversity of the Latinx/é community and aid in the professional development of its members in line with Lattice’s mission of ‘Better Together’._\n\n- _**Obsidian**_ _celebrates, amplifies, and supports the professional and personal journeys of the Black community at Lattice. Through community building, storytelling, and collaboration, we strive to create a more inclusive workplace._\n\n- _**PRIDE**_ _promotes an affirmation of the unique intersectionality of identities that make up the LGBTQIA+ individuals at Lattice. Through education, professional development, workplace collaboration, mentorship, and community outreach we strive to foster an inclusive environment for our LGBTQIA+ Latticians, allies, and surrounding communities._\n\n- _**Thrive**_ _drives inclusive accountability for Latticians to have equal access and opportunity to succeed in the workplace through community engagement, educational awareness, and establishing business best practices rooted in accessibility for all._\n\n- _**Women at Lattice**_ _advances the professional development and empowerment of women at Lattice through education, mentorship, and cross-functional connection, with the ultimate goal of building a more inclusive workplace._\n\n- _**Yachad**_ _fosters a vibrant and safe community for Jewish people at Lattice by educating individuals curious about the history and values of Judaism and hosting events around Jewish holidays, traditions, and culture_\n","2026-04-16T19:06:50.160Z","2026-08-26T15:59:32.098Z","3c7d05e9-1bc0-4be2-9e3a-e3b5ddbf98c6",[],[],[],"Glossary of key terms","glossary-of-key-terms","## Glossary of Terms\n\nGetting familiar with these key terms will help you navigate Chezie with confidence.\n\n**Teams**\\\nA Team represents a program type at your organization — like ERGs, Local Communities, or Interest Groups. Teams help organize groups into categories, making it easy for employees to browse and discover communities that match their interests.\n\n**Groups**\\\nA Group is an individual employee community that lives within a Team. Think of it as the core unit of Chezie — it's where members connect, events happen, and activity is tracked.\n\n**Chapters**\\\nA Chapter is a sub-group within a Group, typically organized by region, programming focus, or professional interest. For example, a company-wide ERG might have a Chapter specifically for its EMEA members.\n\n**Cycles**\\\nA Cycle is a defined period of time used to track budget, goals, and key metrics for a group. Cycles are typically aligned with your organization's fiscal year and help group leaders and admins measure progress over time.\n\n**Goals**\\\nGoals are the objectives a group sets out to achieve within a Cycle. In Chezie, Goals are connected to events, communications, and budget items — making it easy to see how day-to-day activity ties back to the bigger picture.\n\n---\n\n## Roles\n\n**Member**\\\nAn employee who has opted in to join a particular Group. Members can explore events, receive communications, and engage with their community through Chezie.\n\n**Group Admin**\\\nA Group Admin is a leader or co-leader of a specific Group. They have the tools to manage members, plan events, handle communications, and track their group's budget and goals.\n\n**Team Admin**\\\nA Team Admin oversees an entire Team (or program) at the organization level. They have visibility across all Groups within their Team and are responsible for managing the overall health and compliance of the program.","2026-06-30T20:55:13.768Z","9dec6a2b-0e79-4f3f-bc9b-b26c6974a9a1",[],[],[],"Announcing Chezie","announcing-chezie-chezie-2","You don’t need to reinvent the wheel. We’ve created easy-to-use templates to announce Chezie to your employees. For an initial launch or for a re-launch, we suggest touching people in multiple channels - primarily email and Slack/Teams.\n\n## To employees\n\n### **Email Announcement - 2 weeks from launch**\n\n**SUBJECT:**\n\nAnnouncing our new <INSERT COMPANY NAME> ERG Portal!\n\n**BODY:**\n\n![](/api/knowledge-base/images/2a0f9f62-d4cf-4d72-bdc5-34b21e6f7e89)\n\nWe have exciting news!\n\nThe Diversity, Equity, and Inclusion team is partnering with Chezie to launch our new ERG Portal. Our ERGs exist to provide community for our employees and build a sense of belonging.\n\nOur new ERG platform will allow you to self-subscribe to your ERG (or ERGs 😉) of choice and sign up for upcoming events.\n\nThe new ERG Portal will go live on <insert confirmed launch date>. We are extremely excited about this partnership and hope that it will help you find your community here at <INSERT COMPANY NAME>.\n\nSincerely,\n\nThe DEI Team\n\n### **ERG Channel Slack/Teams Announcement - 2 weeks before launch**\n\n@here 📢\n\nWe have some exciting news. In 2 weeks, we’ll be launching our new ERG portal, **Chezie**. Chezie will allow you to self-subscribe to your ERG (or ERGs 😉) of choice and sign up fro any upcoming events.\n\nChezie goes live on <insert launch date>! Stay tuned for more updates.\n\nLet us know if you have any questions! 🎉 🎊\n\n### **Email Announcement - Launch Day**\n\n![](/api/knowledge-base/images/6604c917-21de-4edf-ae3c-dd356525b8e4)\n\n**SUBJECT:**\n\nWE ARE LIVE! Our new ERG Management Platform\n\n**BODY:**\n\n**Today’s the day!**\n\nToday is the day! The <INSERT COMPANY NAME> team has officially launched our new Employee Resource Group (ERG) platform to serve as a one-stop-shop. To make it easy, simply click on the name of the Group below that you’re interested in joining, and you’ll be taken directly to the join form for that group.\n\nOur ERGs\n\n1. **ERG 1** - \\*\\*\\*\\*<insert link> - <insert Group’s mission statement>.\n\n2. **ERG 2** - \\*\\*\\*\\*<insert link> - <insert Group’s mission statement>.\n\n3. **ERG 3** - \\*\\*\\*\\*<insert link> - <insert Group’s mission statement>.\n\n4. **ERG 4** - \\*\\*\\*\\*<insert link> - <insert Group’s mission statement>.\n\n5. **ERG 5** - <insert link> - <insert Group’s mission statement>.\n\nFeel free to reach out to our DEI if you have any questions. Be on the lookout for more exciting features coming soon!\n\nBest,\n\n<INSERT COMPANY NAME> DEI Team\n\n### **ERG Channel Slack/Teams Announcement - Launch Day**\n\n@here 📢\n\nToday is the day! The DEI Team has officially launched our new <INSERT COMPANY NAME> ERG Portal to serve as a one-stop-shop, interactive experience for our ERGs. To join, pick the Group(s) that you’re interested in joining from the links below!\n\n1. **ERG 1** - \\*\\*\\*\\*<insert link> - <insert Group’s mission statement>.\n\n2. **ERG 2** - \\*\\*\\*\\*<insert link> - <insert Group’s mission statement>.\n\n3. **ERG 3** - \\*\\*\\*\\*<insert link> - <insert Group’s mission statement>.\n\n4. **ERG 4** - \\*\\*\\*\\*<insert link> - <insert Group’s mission statement>.\n\n5. **ERG 5** - <insert link> - <insert Group’s mission statement>.\n\nTo browse all of our ERGs at once, you can launch the platform by going here: [**https://\\[companyname\\].chezie.io**](https://chezie.app/login/**companyname**)\n\nLet us know if you have any questions! 🎉 🎊\n\n## To ERG leaders\n\n![](/api/knowledge-base/images/5a5dbbd0-c1ea-4223-9adb-ec815390ac0a)\n\nHi ERG Leaders!\n\nAs some of you know, we are soon launching our ERG portal in partnership with [Chezie](https://www.notion.so/0dc6d2f766b8436c9e6138b80c1e9ee2?pvs=21).\n\nWith Chezie, everyone at\n\n1. **Membership** - No more manual work updating distro lists or adding people to Slack/Teams.\n\n Your members have an easy-to-use portal for learning more about and joining your ERG. Upon joining, they are automatically added to your Slack/Teams channel and sent a welcome email.\n\n2. **Events** - Resources for brainstorming event ideas, scheduling events, and tracking RSVPs and attendance.\n\n With Chezie, you’ll have access to a library of event ideas from the Chezie team and from other companies. You’ll also have a set process for scheduling events and getting approval from us as a DEI team, internal comms, and anyone else that’s involved in the process. Lastly, all of the RSVPs and attendance for the events are tracked so you can see which members are most engaged.\n\n3. **Budget** - Ditch the spreadsheets!\n\n Chezie has a built-in budget tracking system so you can enter expenses and see how much budget you have left for the year. You’ll also be able to see your spending by category (i.e. swag, speakers, food, etc.) and upload receipts.\n\nLastly, you’ll also have access to a set of reusable templates and Chezie’s ERG leader community where you can network with Leads from other companies.\n\nWe are set to launch on <insert confirmed launch date>. If you have any questions, reach out to <insert name> at <insert email>.","2026-04-16T19:06:49.244Z","2026-08-26T15:57:20.492Z","59de4523-53e6-4b30-a8f9-a4b8f97f28cb",[],[],[],"For Members","for-members","2026-06-30T16:04:02.518Z","2026-06-30T21:23:23.100Z","8e549e7a-be7e-4378-83f7-544fb51473dc",2,[759,760],[735],{"_65":736,"_103":737,"_59":-5,"_146":-5,"_150":731,"_116":62,"_117":738,"_119":738,"_22":739,"_24":25,"_148":732,"_12":740,"_188":741},"Joining a group","joining-a-group","2026-06-30T16:04:11.195Z","0af46db1-3782-40ce-896b-21fdebdf8e15",[742,743],[],{"_57":736,"_103":-5,"_112":-5,"_113":752,"_115":739,"_116":62,"_117":753,"_119":754,"_22":755,"_24":25,"_122":756,"_124":-5,"_125":757,"_127":758},{"_57":744,"_103":-5,"_112":-5,"_113":745,"_115":739,"_116":62,"_117":746,"_119":747,"_22":748,"_24":25,"_122":749,"_124":-5,"_125":750,"_127":751},"Joining a private group","1\\. Click on a Team\n\n![1.png](/api/knowledge-base/images/1886bc5c-de4d-4c48-aaca-9ba89a3db6c0)\n\n2\\. Click on Group Name\n\n![2.png](/api/knowledge-base/images/f8e57f93-61d7-4deb-af39-cecad6a5829a)\n\n3\\. Click on Request to join\n\n![3.png](/api/knowledge-base/images/f85c97ae-e574-4081-aa13-a5a3ac5cd97d)\n\n4\\. Once you request to join, a Group Admin must approve your request. Once approved, you'll receive a welcome email in your inbox.","2026-06-30T16:04:23.270Z","2026-07-01T19:19:42.163Z","25ad1bc2-329f-4a68-8a26-07e10cebd371",[],[],[],"1. Click on Team\n\n![91.png](/api/knowledge-base/images/da137fa6-0be6-4c2a-a9d3-1aa345c8bc28)\n\n2\\. Click on Group Name\n\n![92.png](/api/knowledge-base/images/fad43bf5-066c-44d0-93f8-5dbaee2380d7)\n\n3\\. Click on Join\n\n![93.png](/api/knowledge-base/images/2f6a6130-ee17-443e-87ec-fa58eff95363)\n\n4\\. Click on Join Slack Channel (or other linked messaging app)\n\n![94.png](/api/knowledge-base/images/5215291d-040c-4799-be70-edb699ef712d)\n\n5\\. Once joining is complete, you will receive a welcome email in your inbox.","2026-06-30T21:00:21.231Z","2026-07-01T19:17:34.132Z","3a411b9e-198a-43ba-a873-22abd780121f",[],[],[],{"_57":769,"_103":770,"_112":-5,"_113":771,"_115":731,"_116":62,"_117":772,"_119":773,"_22":774,"_24":25,"_122":775,"_124":-5,"_125":776,"_127":777},{"_57":761,"_103":-5,"_112":-5,"_113":762,"_115":731,"_116":62,"_117":763,"_119":764,"_22":765,"_24":25,"_122":766,"_124":-5,"_125":767,"_127":768},"Updating your profile","1. Click the menu group in the bottom of the navbar.\n\n ![CleanShot 2026-06-29 at 16.23.53@2x.png](/api/knowledge-base/images/88c735c0-5bb0-4a04-8f7d-252c77011e08)\n2. Click the Settings icon\n\n ![CleanShot 2026-06-29 at 16.24.11@2x.png](/api/knowledge-base/images/fdd91ba3-d95f-4553-875e-dd2b890ab2e6)\n3. Update your name, pronouns, and/or profile picture. Click ***Update details*** to save your changes.\n\n ![CleanShot 2026-06-29 at 16.24.41@2x.png](/api/knowledge-base/images/c316f02a-7560-4a31-b596-65c8fb90279d)","2026-07-01T13:15:52.441Z","2026-07-01T13:16:52.908Z","743a9f90-65f4-4713-86c2-357e6c9f5d1f",[],[],[],"How to leave a Group","how-to-leave-a-group","To leave a Group from Discover:\n\n1. Go to **Discover**.\n2. Open the Group you want to leave.\n\n ![Click on Asian & Pacific Islander Alliance](/api/knowledge-base/images/dc50ecc5-2837-4573-b9e9-5459cd330450)\n3. Click the three-dot menu next to the Group’s name.\n4. Click **Leave group**.\n\n ![](/api/knowledge-base/images/b693ae2a-42c1-487e-8d9d-1a6252a698ea)","2026-09-03T15:39:29.301Z","2026-09-03T15:45:50.285Z","0d176e76-cbb0-4461-a64f-d2ac5b0403a0",[],[],[],"FAQs","faqs-3","zoom-in","2026-08-26T16:33:31.779Z","63a1dd87-b116-45c2-a9f5-abbd32813e72",11,[786,787,788,789,790,791,792,793,794,795,796],[],{"_57":887,"_103":888,"_112":-5,"_113":889,"_115":782,"_116":62,"_117":890,"_119":891,"_22":892,"_24":25,"_122":893,"_124":-5,"_125":894,"_127":895},{"_57":878,"_103":879,"_112":-5,"_113":880,"_115":782,"_116":62,"_117":881,"_119":882,"_22":883,"_24":25,"_122":884,"_124":-5,"_125":885,"_127":886},{"_57":869,"_103":870,"_112":-5,"_113":871,"_115":782,"_116":62,"_117":872,"_119":873,"_22":874,"_24":25,"_122":875,"_124":-5,"_125":876,"_127":877},{"_57":860,"_103":861,"_112":-5,"_113":862,"_115":782,"_116":62,"_117":863,"_119":864,"_22":865,"_24":25,"_122":866,"_124":-5,"_125":867,"_127":868},{"_57":851,"_103":852,"_112":-5,"_113":853,"_115":782,"_116":62,"_117":854,"_119":855,"_22":856,"_24":25,"_122":857,"_124":-5,"_125":858,"_127":859},{"_57":842,"_103":843,"_112":-5,"_113":844,"_115":782,"_116":62,"_117":845,"_119":846,"_22":847,"_24":25,"_122":848,"_124":-5,"_125":849,"_127":850},{"_57":833,"_103":834,"_112":-5,"_113":835,"_115":782,"_116":62,"_117":836,"_119":837,"_22":838,"_24":25,"_122":839,"_124":-5,"_125":840,"_127":841},{"_57":824,"_103":825,"_112":-5,"_113":826,"_115":782,"_116":62,"_117":827,"_119":828,"_22":829,"_24":25,"_122":830,"_124":-5,"_125":831,"_127":832},{"_57":815,"_103":816,"_112":-5,"_113":817,"_115":782,"_116":62,"_117":818,"_119":819,"_22":820,"_24":25,"_122":821,"_124":-5,"_125":822,"_127":823},{"_57":806,"_103":807,"_112":-5,"_113":808,"_115":782,"_116":62,"_117":809,"_119":810,"_22":811,"_24":25,"_122":812,"_124":-5,"_125":813,"_127":814},{"_57":797,"_103":798,"_112":-5,"_113":799,"_115":782,"_116":62,"_117":800,"_119":801,"_22":802,"_24":25,"_122":803,"_124":-5,"_125":804,"_127":805},"Why are applications permissions required for Microsoft Outlook and Calendar setup?","why-are-applications-permissions-required-for-microsoft-outlook-and-calendar-setup","You have the option to only give Chezie delegated access. The only downside to this is that without the application-wide access, your Admins would have to manually go in to Chezie and click a button to refresh attendance data for events that are scheduled.","2026-04-16T20:14:02.213Z","2026-08-26T18:14:12.137Z","93f7e46b-f1d9-411f-99cc-c2ced8b9e88c",[],[],[],"Who receives the Welcome Email when a new member joins?","who-receives-the-welcome-email-when-a-new-member-joins","The Welcome Email is sent exclusively to the **new member**. If they choose to reply to that email, their message will be directed to the address listed in the **Group Email** field defined in your group settings.","2026-04-16T20:22:27.356Z","2026-08-26T18:13:46.763Z","ebc24aa8-cf91-4661-9b43-ed8f7da63d54",[],[],[],"What is the character limit for event titles?","what-is-the-character-limit-for-event-titles","The character limit for event titles is 250 characters.","2026-04-16T19:59:21.091Z","2026-08-26T16:50:13.977Z","44d6b3ae-48f4-4845-8b1b-76be9d819975",[],[],[],"What are the suggested dimensions for the logos and banners","faqs-chezie-2","- Banners - 1600 x 450 px\n- Logos - 500 x 500 px","2026-04-16T19:06:37.289Z","2026-08-26T16:34:12.598Z","6f0e1cdd-c3e3-4297-95dc-3883ba4af693",[],[],[],"Is there an ERG Co-Chair and/or Pillar Lead application in Chezie?","is-there-an-erg-co-chair-andor-pillar-lead-application-in-chezie","There is not an in-app application for ERG leads.","2026-04-16T19:56:56.997Z","2026-08-26T16:45:55.240Z","8bdb930b-a5f1-4b94-bb89-6d722ed1080f",[],[],[],"Is routing for multiple approvals supported?","routing-for-multiple-approvals","Unfortunately not yet, though this is something on our roadmap.","2026-04-16T19:58:28.101Z","2026-08-26T16:46:45.213Z","8077206a-3bfe-4ebd-a275-f0addbdb2264",[],[],[],"If application permissions are absolutely necessary, are Application Access Policies supported to scope access only to the service account (e.g., ergs@company.com)?","if-application-permissions-are-absolutely-necessary-are-application-access-policies-supported-to-sco","Yes, there is scope to only manage the service account’s calendar. Chezie will not have access to or control the calendars of other users.","2026-04-16T20:21:08.552Z","2026-08-26T16:44:55.712Z","77ce1940-ee8b-427a-a901-2ab879974e86",[],[],[],"How does the service account interact with the Chezie application once the integration is complete? Is it acting on behalf of users, or is it solely used to manage events within its own calendar?","how-does-the-service-account-interact-with-the-chezie-application-once-the-integration-is-complete-i","The service account only manages events within its own calendar.","2026-04-16T20:20:37.120Z","2026-08-26T16:43:35.490Z","1645f2d3-2235-4776-8783-f1908ccb6d15",[],[],[],"Can I embed images directly in an email blast?","can-i-embed-images-directly-in-an-email-blast","Embedding images directly in an email blast (rather than sending them as attached files) is not currently supported.","2026-09-03T15:23:42.725Z","2026-09-03T15:46:16.369Z","51a818e1-4407-42d6-b035-502b62810155",[],[],[],"Can delegated permissions be used instead, assuming the service account is the one initiating and managing events? This would help avoid tenant-wide access and reduce security exposure.","can-delegated-permissions-be-used-instead-assuming-the-service-account-is-the-one-initiating-and-man","Yes.","2026-04-16T20:15:24.328Z","2026-08-26T16:43:13.067Z","5fe9e098-284f-4a47-85bb-2ff2b10f5ec7",[],[],[],"Are new members automatically added to upcoming events?","are-new-members-automatically-added-to-upcoming-events","No, new members can view upcoming events in Discover. Moving forward, they will be included in the invite list for new events.","2026-04-16T20:12:09.105Z","2026-08-26T16:41:20.540Z","87d3e88a-738a-420b-9548-95492af7920c",[],[],[],"Expenses","expenses-3","dollar-sign","2026-06-30T21:18:53.277Z","1d99e77d-e140-4ed3-9b71-5dcbf9f3e01d",7,[904,905,906,907,908,909,910],[],{"_57":963,"_103":964,"_112":-5,"_113":965,"_115":900,"_116":62,"_117":966,"_119":967,"_22":968,"_24":25,"_122":969,"_124":-5,"_125":970,"_127":971},{"_57":954,"_103":955,"_112":-5,"_113":956,"_115":900,"_116":62,"_117":957,"_119":958,"_22":959,"_24":25,"_122":960,"_124":-5,"_125":961,"_127":962},{"_57":946,"_103":-5,"_112":-5,"_113":947,"_115":900,"_116":62,"_117":948,"_119":949,"_22":950,"_24":25,"_122":951,"_124":-5,"_125":952,"_127":953},{"_57":937,"_103":938,"_112":-5,"_113":939,"_115":900,"_116":62,"_117":940,"_119":941,"_22":942,"_24":25,"_122":943,"_124":-5,"_125":944,"_127":945},{"_57":928,"_103":929,"_112":-5,"_113":930,"_115":900,"_116":62,"_117":931,"_119":932,"_22":933,"_24":25,"_122":934,"_124":-5,"_125":935,"_127":936},{"_57":919,"_103":920,"_112":-5,"_113":921,"_115":900,"_116":62,"_117":922,"_119":923,"_22":924,"_24":25,"_122":925,"_124":-5,"_125":926,"_127":927},{"_57":911,"_103":-5,"_112":-5,"_113":912,"_115":900,"_116":62,"_117":913,"_119":914,"_22":915,"_24":25,"_122":916,"_124":-5,"_125":917,"_127":918},"Splitting an expense with other Group(s)","1\\. Click on **Budget**\n\n![5.png](/api/knowledge-base/images/c1038695-415d-4622-855d-d46e83ea659b)\n\n2\\. Click on **Add Transaction**\n\n![6.png](/api/knowledge-base/images/d7e84098-5435-45fa-b1d1-9b1a61285fcd)\n\n3\\. Type Expense name\n\n![7.png](/api/knowledge-base/images/83dd9415-0c45-41e8-8e9c-c4b9d7313c51)\n\n4\\. Enter Purchase date\n\n![8.png](/api/knowledge-base/images/5b1c95fd-7a62-46aa-8733-818df6fa5687)\n\n5\\. Choose Cycle\n\n![9.png](/api/knowledge-base/images/6a66597b-6e08-4e6b-af76-c1c9c2ed4f23)\n\n6\\. Select Goal\n\n![10.png](/api/knowledge-base/images/3720b92a-0f24-4116-8f46-f6da231c0639)\n\n7\\. Enter Planned and Actual Amounts\n\n![10.png](/api/knowledge-base/images/a15f7686-4f69-44fa-9de4-6ea97e8f854d)\n\n8\\. Click on Split this expense\n\n![11.png](/api/knowledge-base/images/2fadfa36-cc32-49d0-b6fc-ca23185f6ae7)\n\n9\\. Select Group(s)\n\n![12.png](/api/knowledge-base/images/980dedc4-10a8-46e2-af02-a6a2de24ce81)\n\n---\n\n```plaintext\nℹ️ You can choose to split an expense evenly or do a custom split.\n```\n\n---\n\n10\\. Select Category Category\n\n![13.png](/api/knowledge-base/images/693e6f3a-d567-4589-a296-2a650fc071cc)\n\n11\\. Type Expense description\n\n![15.png](/api/knowledge-base/images/af05ac01-00fc-4786-84da-f996e70f9d31)\n\n12\\. Upload a receipt (if applicable)\n\n![16.png](/api/knowledge-base/images/3e214083-5071-421c-b77e-93d43de3e0b3)\n\n13\\. Click on Create Expense\n\n![17.png](/api/knowledge-base/images/18d2152d-adf1-4429-9e8c-91f225c6a431)","2026-07-02T16:47:14.295Z","2026-07-02T16:56:41.100Z","288e5ea3-3b27-4d0b-a975-f233bceb61af",[],[],[],"How to request approval for an expense","how-to-request-approval-for-an-expense-chezie-2","### How to request approval for an expense in Chezie\n\n1. Go to **Budget** and click the expense you want to request approval for.\n\n ![1.png](/api/knowledge-base/images/3977410c-1895-4085-9f76-bdd555681310)\n\n2. Click **Submit for approval**.\n\n ![2.png](/api/knowledge-base/images/94fabf16-13f3-478e-af6b-e53cef37bc5d)\n\n3. Confirm the submission.\n\n ![3.png](/api/knowledge-base/images/566138c8-f6f8-4168-84ab-af6a3818fc9c)\n\n## If an expense is not visible to your team\n\nAn expense in **Draft** status is visible only to the user who created it. Submit the expense for approval so the relevant team can see it and review it.\n\nAfter the expense is reviewed and approved, it is included in the total budget calculation.","2026-04-16T19:07:09.827Z","2026-09-03T15:11:20.888Z","a09c84f9-0854-4f70-9733-6705a1d470d8",[],[],[],"How to edit an expense","how-to-edit-an-expense-chezie-2","### How to edit an expense in Chezie.\n\n1. In Budget, select the record you want to edit.\n\n ![1.png](/api/knowledge-base/images/6cc704a4-51f3-4b37-86ad-183ebf960499)\n\n\n3) Click Edit expense\n\n ![2.png](/api/knowledge-base/images/f80a6e8a-75e4-459d-890d-4aa7617008c9)\n4) Make the necessary updates. In this case, we'll update the actual amount.\n\n ![3.png](/api/knowledge-base/images/07d5a683-f63b-40ac-8c6b-1703d2dbab53)\n\n\n4. Click on Save changes when done.\n\n ![4.png](/api/knowledge-base/images/f536d905-bced-4ee7-b803-3613dcdceb84)","2026-04-16T19:07:09.364Z","2026-08-26T16:25:09.218Z","4b0355e9-e746-4e7c-880c-905f29d6e201",[],[],[],"How to cancel, delete, or restore an expense","how-to-delete-an-expense-chezie-2","### \n\n1. Click on Budget.\n\n ![1.png](/api/knowledge-base/images/284d30bc-020c-4cfd-80e3-5fbad46806e5)\n\n\n2) Search for the record you want to edit. Click on the three dots and select Cancel expense.\n\n ![2.png](/api/knowledge-base/images/c5d27d62-4c1a-422c-9095-bd461d5d0bad)\n\n\n3. Confirm cancellation.\n\n ![3.png](/api/knowledge-base/images/00978ea1-1397-44e9-85fc-9bcb2f074ac9)\n\n\n4) To delete a cancelled expense, click the three dots and select Delete. To restore it, select Restore expense. Restored expenses will need to be approved by an admin again.\n\n ![4.png](/api/knowledge-base/images/edf5fdeb-81bf-41fc-84a5-cc9a0246e704)","2026-04-16T19:07:09.621Z","2026-08-26T16:15:13.327Z","f07aaed2-9cb2-48bd-9331-bc7567c7def3",[],[],[],"How to approve a submitted expense","```plaintext\nAdmins with the Approve expenses permission can approve expense requests submitted by Group Leads. When a Lead submits an expense for approval, Admins with the Approve expenses permission will receive a notification.\n```\n\n1. Click on **Budget** from the admin view.\n\n ![52.png](/api/knowledge-base/images/7e3e4936-b991-4128-9e57-e776e7de0323)\n\n2. Find the expense with **Pending approval** status.\n\n3. Click on the expense to open it.\n\n ![53.png](/api/knowledge-base/images/b5f750a1-7c00-4883-b2b2-a4bdf32219af)\n\n4. Review the expense details (amount, category, description, attachments).\n\n5. Click **Approve** to approve the expense.\n\n ![55.png](/api/knowledge-base/images/9fdb40bc-94be-4ddb-b92a-3aac57b69d3f)\n\nThe expense status will update and the Lead who submitted it will be notified.\n\n## Who can approve expenses\n\nOnly Admins with the **Approve expenses** permission enabled can approve submitted expenses. This is configured under Admin permissions in your organization's settings.","2026-07-01T14:48:41.089Z","2026-07-01T14:50:40.848Z","0ec1177b-7333-4119-895b-8384b0dbbfc7",[],[],[],"Expense statuses explained","expense-statuses-explained","Every expense moves through a status that shows where it stands in the review process, from first being entered to being approved (or cancelled).\n\n### The five expense statuses\n\n| Status | What it means | |\n| --- | --- | --- |\n| **Draft** | The transaction has been created, but the planned and/or actual amount hasn't been finalized yet. Draft expenses can still be edited, and are only visible to the Admin who created them. | |\n| **Pending** | The transaction has been submitted for review and is waiting on Admin approval. | |\n| **Update requested** | An Admin has reviewed the transaction and is asking for changes or additional documentation. The Group Admin who submitted it is notified and can resubmit once the edits are made. | |\n| **Approved** | The transaction has been approved. | |\n| **Cancelled** | The transaction has been cancelled. | |\n\n### If your organization doesn't require approvals\n\nTeams that don't require expense approval skip Pending, and Update requested entirely — every expense is created and can be moved to **Approved** status immediately.\n\n### How a transaction typically moves through these statuses\n\n1. A Group Admin creates the transaction — it starts in **Draft**.\n2. Once submitted for review, it moves to **Pending**.\n3. A reviewing Admin either:\n - Approves it → **Approved**, or\n - Requests changes → **Update requested**, which returns to the submitter for edits and resubmission (back to **Pending**).\n4. At any point before final approval, the transaction can be moved to **Cancelled**.","2026-09-15T13:56:21.888Z","2026-09-15T13:57:12.902Z","ee5193fc-3fbf-4aea-a1e7-1330d8d5208c",[],[],[],"Creating an Expense","creating-an-expense","1\\. In the left-side pane under **Groups**, select the group for which you want to add the transaction. The **Add Transaction** button is inactive until a group is selected.\n\n2\\. Go to **Budget**.\n\n![79.png](/api/knowledge-base/images/f34ba561-3d12-493a-85c1-717df1a65977)\n\n3\\. Click on **Add Transaction**.\n\n![80.png](/api/knowledge-base/images/0a059689-d3f2-4137-af80-13fbc6b877b8)\n\n4\\. Type Expense name.\n\n![81.png](/api/knowledge-base/images/8f59fa7b-64c5-4d10-91e1-71759b5f8057)\n\n5\\. Enter Purchase date.\n\n![82.png](/api/knowledge-base/images/97f7c232-b482-430f-8e96-2670e8533f38)\n\n6\\. Click on Cycle.\n\n![83.png](/api/knowledge-base/images/9bb4631a-4201-4f89-8296-9d66a370b2f1)\n\n7\\. Select the Goal.\n\n![84.png](/api/knowledge-base/images/72424972-7884-4430-93f0-73091f4cf91f)\n\n8\\. Enter expense amount.\n\n![85.png](/api/knowledge-base/images/e5153c53-4ec0-4707-a106-2b91d877be1c)\n\n9\\. Select whether event is associated with an event (Yes/No).\n\n![86.png](/api/knowledge-base/images/82993884-ec39-4c04-851c-a75f19bfedb6)\n\n---\n\n```plaintext\nℹ️ If an expense item is associated with an event, click Yes, and then select from the Event dropdown which event it corresponds with.\n```\n\n---\n\n10\\. Click on Category.\n\n![87.png](/api/knowledge-base/images/a02809bf-f501-4291-ba79-53a6420769fa)\n\n11\\. Type Expense description.\n\n![88.png](/api/knowledge-base/images/16cb7863-a723-4003-a54d-543351f37cf0)\n\n12\\. Upload a copy of the receipt.\n\n![89.png](/api/knowledge-base/images/b5a57e00-7bd9-4038-9018-1b2da3e48210)\n\n13\\. Click on **Create Expense**.\n\n![90.png](/api/knowledge-base/images/a4adb8a6-c983-4527-bdf6-b1fa884a6692)","2026-07-01T14:05:42.079Z","2026-09-18T18:57:50.894Z","b2a35c35-b346-475e-a7f0-05e286f62584",[],[],[],"Events","events-3","2026-06-30T18:52:18.005Z","2026-06-30T21:23:14.027Z","174b4930-1165-4bfd-ba5a-f7e80791a71f",19,[980,981,982,983,984,985,986,987,988,989,990,991,992,993,994,995,996,997,998],[],{"_57":1159,"_103":-5,"_112":-5,"_113":1160,"_115":976,"_116":62,"_117":1161,"_119":1162,"_22":1163,"_24":25,"_122":1164,"_124":-5,"_125":1165,"_127":1166},{"_57":1150,"_103":1151,"_112":-5,"_113":1152,"_115":976,"_116":62,"_117":1153,"_119":1154,"_22":1155,"_24":25,"_122":1156,"_124":-5,"_125":1157,"_127":1158},{"_57":1141,"_103":1142,"_112":-5,"_113":1143,"_115":976,"_116":62,"_117":1144,"_119":1145,"_22":1146,"_24":25,"_122":1147,"_124":-5,"_125":1148,"_127":1149},{"_57":1133,"_103":-5,"_112":-5,"_113":1134,"_115":976,"_116":62,"_117":1135,"_119":1136,"_22":1137,"_24":25,"_122":1138,"_124":-5,"_125":1139,"_127":1140},{"_57":1124,"_103":1125,"_112":-5,"_113":1126,"_115":976,"_116":62,"_117":1127,"_119":1128,"_22":1129,"_24":25,"_122":1130,"_124":-5,"_125":1131,"_127":1132},{"_57":1115,"_103":1116,"_112":-5,"_113":1117,"_115":976,"_116":62,"_117":1118,"_119":1119,"_22":1120,"_24":25,"_122":1121,"_124":-5,"_125":1122,"_127":1123},{"_57":1106,"_103":1107,"_112":-5,"_113":1108,"_115":976,"_116":62,"_117":1109,"_119":1110,"_22":1111,"_24":25,"_122":1112,"_124":-5,"_125":1113,"_127":1114},{"_57":1097,"_103":1098,"_112":-5,"_113":1099,"_115":976,"_116":62,"_117":1100,"_119":1101,"_22":1102,"_24":25,"_122":1103,"_124":-5,"_125":1104,"_127":1105},{"_57":1088,"_103":1089,"_112":-5,"_113":1090,"_115":976,"_116":62,"_117":1091,"_119":1092,"_22":1093,"_24":25,"_122":1094,"_124":-5,"_125":1095,"_127":1096},{"_57":1079,"_103":1080,"_112":-5,"_113":1081,"_115":976,"_116":62,"_117":1082,"_119":1083,"_22":1084,"_24":25,"_122":1085,"_124":-5,"_125":1086,"_127":1087},{"_57":1070,"_103":1071,"_112":-5,"_113":1072,"_115":976,"_116":62,"_117":1073,"_119":1074,"_22":1075,"_24":25,"_122":1076,"_124":-5,"_125":1077,"_127":1078},{"_57":1061,"_103":1062,"_112":-5,"_113":1063,"_115":976,"_116":62,"_117":1064,"_119":1065,"_22":1066,"_24":25,"_122":1067,"_124":-5,"_125":1068,"_127":1069},{"_57":1052,"_103":1053,"_112":-5,"_113":1054,"_115":976,"_116":62,"_117":1055,"_119":1056,"_22":1057,"_24":25,"_122":1058,"_124":-5,"_125":1059,"_127":1060},{"_57":1043,"_103":1044,"_112":-5,"_113":1045,"_115":976,"_116":62,"_117":1046,"_119":1047,"_22":1048,"_24":25,"_122":1049,"_124":-5,"_125":1050,"_127":1051},{"_57":1034,"_103":1035,"_112":-5,"_113":1036,"_115":976,"_116":62,"_117":1037,"_119":1038,"_22":1039,"_24":25,"_122":1040,"_124":-5,"_125":1041,"_127":1042},{"_57":1026,"_103":-5,"_112":-5,"_113":1027,"_115":976,"_116":62,"_117":1028,"_119":1029,"_22":1030,"_24":25,"_122":1031,"_124":-5,"_125":1032,"_127":1033},{"_57":1017,"_103":1018,"_112":-5,"_113":1019,"_115":976,"_116":62,"_117":1020,"_119":1021,"_22":1022,"_24":25,"_122":1023,"_124":-5,"_125":1024,"_127":1025},{"_57":1008,"_103":1009,"_112":-5,"_113":1010,"_115":976,"_116":62,"_117":1011,"_119":1012,"_22":1013,"_24":25,"_122":1014,"_124":-5,"_125":1015,"_127":1016},{"_57":999,"_103":1000,"_112":-5,"_113":1001,"_115":976,"_116":62,"_117":1002,"_119":1003,"_22":1004,"_24":25,"_122":1005,"_124":-5,"_125":1006,"_127":1007},"Troubleshooting: calendar invites not sending or updating","troubleshooting-calendar-invites","*Calendar invites are sent automatically when an event is approved. If invites aren't arriving or aren't updating correctly, here's how to troubleshoot.*\n\n---\n\n## Invites never sent after event approval\n\n**Check 1: Is your calendar integration connected?**\n\nCalendar invites only send if a calendar integration is active. Go to **Settings → Integrations** and confirm the calendar account is connected. If it shows as disconnected or missing, reconnect it (or ask your IT admin to reconnect it for you) and re-approve the event to trigger a fresh invite send.\n\nMore details here: \n\n**Check 2: Was the event actually approved?**\n\nInvites are sent at the moment of approval, not when the event is created or submitted. Confirm the event status is **Approved** (not Draft, Pending, or Update Requested).\n\n## Google Calendar and Zoom access has been revoked\n\n**What you'll see:** Event invitations are not sent, an error appears when inviting members, and the event does not populate the calendar as a pending event. Zoom conferencing may also fail.\n\n**Why:** The linked Google account used to schedule events and the linked Zoom account used for conferencing have lost access to the Chezie app. This can happen after the account password is changed or when someone explicitly revokes the app's access. The exact reason may not be visible.\n\n**What to do:** Ask whoever originally set up the Google and Zoom accounts to re-authenticate both services. Both integrations must be re-authenticated to restore event scheduling, calendar invitations, and Zoom conferencing.\n\n---\n\n## Invites not updated after editing an event\n\nWhen you edit an approved event, Chezie gives you the option to notify attendees or not.\n\n**If attendees weren't notified after an edit:**\n\n1. Open the event.\n2. Make any small change (even a minor description tweak).\n3. Click **Update**.\n4. On the update confirmation screen, make sure the **\"Notify attendees\"** option is **selected**.\n5. Save the update.\n\n> ```plaintext\n> 💡 If you save without notifying, the event details are updated in Chezie but the calendar invites for existing attendees are not updated. You'll need to re-save with notifications on to push the update.\n> ```\n\n---\n\n## Announcement email vs. calendar invite\n\nChezie sends two types of communications when an event is approved:\n\n- **Announcement email** — a one-time email informing members about the event\n- **Calendar invite** — a calendar event sent to invitees so it appears in their calendar\n\nThese are separate. Getting one doesn't guarantee the other. If members say they didn't receive a calendar invite but got the announcement, check your calendar integration status.\n\n---\n\n## Still not working?\n\nIf invites are still not sending after confirming the above, contact [support@chezie.co](mailto:support@chezie.co) via the in-app chat or via email with the event name and a description of what's happening. This may indicate a bug with the calendar integration.","2026-06-30T19:04:56.182Z","2026-09-03T15:27:46.658Z","367b5291-1418-4907-808f-f4a433886e9c",[],[],[],"The event scheduling process, explained","the-event-scheduling-process-explained-chezie-2","### An explanation of how scheduling and managing events in Chezie works.\n\n```plaintext\nThe event scheduling process helps ensure that Groups go through the same review process every time they want to schedule an event.\n```\n\n![](/api/knowledge-base/images/3a0d54fe-b5df-478c-b67f-6b1031ee8108)\n\n## The event scheduling process\n\nThe process is as follows:\n\n1. Either an Admin or Lead [schedules an event](https://docs.chezie.co/docs/chezie-2026/events-3/cb506682-de51-4370-928e-512a1498a37d)\n\n2. The event is created in **draft** status, meaning that the invites have not yet been sent\n\n3. One of the Leads [requests approval](https://docs.chezie.co/docs/chezie-2026/events-3/how-to-request-approval-for-an-event-chezie-2) for the event\n\n4. Admins receive an email notification about the new event, and then either **Approve** the event or **request changes**.\n\n5. If approved, the calendar invites may be sent to invitees. If changes are requested, Leads get notified and can request approval.","2026-04-16T19:06:50.502Z","2026-08-26T15:30:51.149Z","f95515b8-8624-41b8-b861-4107252a94ff",[],[],[],"The Different Event Statuses","event-statuses","*Events in Chezie move through a defined set of statuses from creation through to completion or cancellation. Here's what each one means.*\n\n---\n\n## Event statuses\n\n- **Draft** — The event has been created but not yet submitted for approval. It can still be edited. This is a good time for Group Admins from co-host groups to provide input (description, name, etc.) and add any expenses tied to the event.\n- **Pending approval** — The Group Admin(s) for the Host or Co-host Groups have submitted the event for review. Only Admins can approve an event. Calendar invites have not been sent yet.\n- **Update requested** — An Admin has reviewed the event but requested changes. Calendar invites have not been sent. Group Admins will be notified and can resubmit once edits are made.\n- **Approved** — An Admin has approved the event. When an event is approved, calendar invites are sent to all invitees and the video meeting link (Zoom, MS Teams, or Google Meet) is automatically created.\n- **Canceled — The event has been cance**led by either the Group Admins or an Admin. Once an event is canceled, it cannot be edited.","2026-06-30T18:53:15.097Z","2026-07-01T13:27:41.316Z","ae575836-909e-46eb-9cae-cfa802558e57",[],[],[],"QR codes","Chezie generates QR codes for three purposes per event: check-in attendance, sharing the event, and post-event surveys. Here's how to access each one.\n\n---\n\n1. On the homepage, click on **Events**.\n\n ![39.png](/api/knowledge-base/images/95fc0a97-f303-4d4d-a68b-847ce3678bb2)\n\n2. Choose the event and click on **View**.\n\n ![40.png](/api/knowledge-base/images/cbdc76a5-07bf-43b6-82a7-230130a78b10)\n\n3. To download a **check-in QR code** (for tracking in-person attendance), click on **Event Actions > Attendance**.\n\n ![47.png](/api/knowledge-base/images/748cb539-14f8-407c-8482-3528959df8aa)\n\n4. Click on **Get check-in QR code**.\n\n ![42.png](/api/knowledge-base/images/ee22a2f5-cd0e-480e-bc0e-924611146a20)\n\n5. To download a **QR code to share the event**, click on **Share event**.\n\n ![49.png](/api/knowledge-base/images/40fbfb53-efb9-4563-b616-f6265b0752e9)\n\n6. Click on **Download QR code**.\n\n ![44.png](/api/knowledge-base/images/854f774b-7061-487e-8342-c0b6562c8736)\n\n7. To get a **survey QR code**, click on **Survey link**.\n\n ![51.png](/api/knowledge-base/images/25de681f-d4e8-43fd-b589-90718bd33f44)\n\n8. Click on **Get survey QR code**.\n\n ![46.png](/api/knowledge-base/images/61ba2549-98bf-4697-beb1-fef03ef8962a)","2026-06-30T20:33:05.787Z","2026-06-30T20:35:20.727Z","e4a08351-8862-403a-a79c-fbaf662b9f2b",[],[],[],"How to use your company’s Host Key in a Zoom meeting","how-to-use-your-companys-host-key-in-a-zoom-meeting-chezie-2","## **What is a Zoom Host Key?**\n\nA **Zoom host key** is a 6-digit code that allows a participant to claim host control in a Zoom meeting. \n\nUsing the host key gives group leaders access to advanced Zoom features like:\n\n- Managing participants\n\n- Controlling screen sharing\n\n- Starting and ending the meeting\n\n- Managing breakout roomsERG leaders can now use the host key for any meetings they create, allowing them to take host control, enable breakout rooms, create webinars, and more—while still benefiting from automatic attendance tracking.\n\nTo use the host key:\n\n1. **Join the meeting:** Begin by joining the Zoom meeting you need to control.\n\n2. **Access Participants panel:** In the meeting controls at the bottom of the screen, click the “Participants” icon.\n\n3. **Claim Host:** At the bottom of the Participants panel, you’ll see “Claim Host”. Click on this option.\n\n4. **Enter Host Key:** A window will pop up asking for your host key. Enter the 6-digit code.\n\n5. **Claim Host:** Click “Claim Host” to verify the key and gain host privileges.\n\n## **How to view and customize your host key**\n\nYou can edit and enter your preferred 6-digit host key. This host key is applied to meetings you schedule.\n\n1. Sign in to the [**Zoom web portal**](https://zoom.us/profile).\n2. In the navigation panel, click [**Profile**](https://zoom.us/profile).\n3. Scroll down to the **Meeting** section.\n4. Select the eye icon next to your **Host Key** to view your current 6-digit pin.\n5. Click **Edit**.\n6. Input the new host key desired and click **Save**.\n\n> The Zoom Host Key remains static across all events. This will not change unless updated within the service account’s Zoom settings.\n\n## **How to Access the Recording**\n\nTo get access to the recording, the leads would need to:\n\n1. Join the zoom meeting\n\n2. Enter the host key\n\n3. Take host control\n\n4. Click the **Record** button and choose to record to your computer\n\nAfter the call, the lead will have access to the recording.","2026-04-16T19:06:27.951Z","2026-08-26T15:52:28.158Z","1cf198ad-b1e5-49da-9cf5-5a387dea071f",[],[],[],"How to upload attendance for a past event","how-to-upload-attendance","# Chezie (2026 Upgrade)\n\n1. Gather your attendance reports (from Zoom, Google Meet, MS Teams, or in-person tracking). Click [here](https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0073594) for instructions on how to gather your report from Zoom.\n2. Make sure the list has at least each attendee's email address. \n3. Email us at [support@chezie.co](mailto:support@chezie.co) with:\n 1. Event name\n 2. Attendance list csv\n4. Look out for an email notification to let you know that the upload has been finished.\n\n# Chezie (Legacy)\n\n### Effortlessly upload and manage attendance records for your past events.\n\n1. Gather your attendance reports (from Zoom, Google Meet, MS Teams, or in-person tracking). Click [here](https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0073594) for instructions on how to gather your report from Zoom.\n\n2. Go to the Events tab in Admin view.\n\n![](https://fb-usercontent.fra1.cdn.digitaloceanspaces.com/0194fbbd-4012-7c70-aa00-7f86ded4f412.png)\n\n3. Click the three dots next to the event you want to upload attendance for.\n\n![](https://fb-usercontent.fra1.cdn.digitaloceanspaces.com/0194fbbd-edb4-734f-9e0a-ed0af0091737.png)\n\n4. Click on Upload attendance.\n\n![](https://fb-usercontent.fra1.cdn.digitaloceanspaces.com/0194fbbe-ac2e-7aed-bf93-5a237998cb11.png)\n\n5. Drop the files that you wish to upload into the popup.\n\n![](https://fb-usercontent.fra1.cdn.digitaloceanspaces.com/0194fbbf-0db6-7f65-ad96-958dd4b7fa3f.png)\n\n6. Click on Upload attendance.\n\n![](https://fb-usercontent.fra1.cdn.digitaloceanspaces.com/0194fbbf-6da7-7c8b-8dda-8a06069aeb7e.png)\n\n7. Once your attendance is uploaded, you'll get a notification that the report is ready.","2026-04-16T19:06:52.318Z","2026-06-30T19:23:41.127Z","e5f0ae17-ceb8-4ba8-bc81-19b3e8b3e655",[],[],[],"How to update an event","how-to-update-an-event-chezie-2","### How to update an existing calendar invite with the option to deliver the notifications quietly\n\n1. Go to Events.\n\n\n2) Click the event that you want to update.\n\n ![1.png](/api/knowledge-base/images/0794b8c0-5245-4ea5-a22a-b0b0ad44147f)\n\n\n3. Click on Edit event.\n\n ![2.png](/api/knowledge-base/images/f76ab3ce-292b-4f0e-9000-5142eacf2ac9)\n\n\n4) Make whatever changes you like. In this case, we'll change the end time.\n\n ![5.png](/api/knowledge-base/images/b4638b06-e859-4b39-b8f4-2a788b9e9149)\n5) Once all updates are made, click Update.\n\n ![3.png](/api/knowledge-base/images/20d698f6-7649-464f-b535-f54371f4f652)\n6) If you don't want the people on your guest list to be notified, click Don't Send. Otherwise, click Send.\n\n ![4.png](/api/knowledge-base/images/4d16ea62-301a-421d-b81a-23f7797562c0)","2026-04-16T19:06:25.646Z","2026-08-26T15:20:21.352Z","433ff336-2309-476f-a1e7-1684f1da169b",[],[],[],"How to request approval for an event","how-to-request-approval-for-an-event-chezie-2","### Learn how to navigate the event approval request process with our user-friendly guide.\n\n```plaintext\nWhen you’re ready to send the invites for your event, you can notify your Admins that the event should be approved.\n\nNote: Admins with the Approve events permission don’t need to request approval for events.\n```\n\n1. Go to Events and find the event you want to request approval for.\n\n ![1.png](/api/knowledge-base/images/274f8e94-dd61-4868-ad97-249dee26373f)\n\n2. Open the event and click Submit for Approval.\n\n ![2.png](/api/knowledge-base/images/f4b1f544-3e1c-44a0-aaee-9c94f50be345)\n\n3. You do not need to select an individual admin. Add your message (if any) and click Send. All admins with approval permissions will automatically receive a notification to approve the event.\n\n ![3.png](/api/knowledge-base/images/6e15ce57-e734-4b77-94fe-ced877f7ed18)","2026-04-16T19:06:52.000Z","2026-09-03T15:08:29.304Z","915686b9-1619-4966-9a96-6c1525e34c63",[],[],[],"How to get your meeting room links when scheduling new events","how-to-get-your-meeting-room-links-when-scheduling-new-events-chezie-2","### Access and share meeting room links seamlessly when scheduling new events.\n\n```plaintext\nThese are simple instructions for copying your meeting links for Zoom and Google Meet.\n```\n\n## **How to get your Zoom meeting link**\n\n1. Sign in to the Zoom web portal.\n\n2. Next to **Personal Meeting ID**, click the eye icon to view your full link.\n\n3. Click the eye icon to reveal your full link\n\n![](/api/knowledge-base/images/ad7111bf-91e1-4acf-9694-47fbe95342be)\n\n![](/api/knowledge-base/images/798eb5a7-6358-4047-aea7-36e3e7a84f5c)\n\n4. Copy the link\n\n5. Paste your link into the event form\n\n## **How to get your Google Meet meeting link**\n\n1. Sign in to your Google account.\n\n2. Go to \n\n3. Click **New Meeting**\n\n![](/api/knowledge-base/images/3a87a0ea-00b0-4599-9113-73acb8f404eb)\n\n4. Click **Create a meeting for later**\n\n![](/api/knowledge-base/images/f5db5fa9-585a-4536-b739-6a79f5ce0f61)\n\n5. **Copy your meeting** link and paste it into the event form. We suggest pasting the dial in instructions into the meeting description so people can access it!\n\n![](/api/knowledge-base/images/1b4d2292-b7af-4447-a1dc-4a057afd5b97)\n","2026-04-16T19:06:52.465Z","2026-08-25T20:46:43.023Z","edffc4d0-20b4-47f5-960a-7aee5621e96c",[],[],[],"How to get an attendance report","how-to-get-an-attendance-report-chezie-2","### Easily access and generate detailed attendance reports for your events.\n\n## Zoom\n\n1. Sign in to the Zoom web portal.\n\n2. In the navigation menu, click **Analytics &** **Reports**.\n\n3. Click the **Usage Reports** tab.\n\n4. Click **Usage**.\n\n5. At the top, use the following functionalities to sort the data by meeting:\n\n - Search by time range: Select a time range (within a month) using the **From** and **To** fields, then click **Search**.\n\n - Search by meeting ID: Enter the meeting ID in the search box, then click **Search**.\n\n6. Export CSV files:\n\n - Export the entire list of meetings on the **Usage** page:\n\n 1. At the top of the **Usage** page, click **Export as CSV File**.A CSV will download, including all the listed meetings in the **Usage** page.\n\n - Export a specific meeting's list of participants:\n\n 1. Locate your meeting, then click the participant count (number) under the **Participants Source** column. A pop-up window with the list and details of internal and external meeting participants will appear. This will show you a list of meeting participants, including join and leave times. **Note**: This includes all participants except [**Waiting Room**](https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0063329) users.\n\n 2. (Optional) In the top-left corner of the window, select the following checkboxes:\n\n - **Export with meeting data**: The Zoom meeting data will be included in the exported attendee list.\n\n - **Show unique users**: The unique users will be included in the exported attendee list. **Note**: If the participant is a **Guest**, and no emails were uploaded to Zoom in any form (for example, by entering emails to register to join the meeting, or the host provided the participants' email to Zoom), the guest email is hidden.\n\n 3. Click **Export**. A CSV file will download.\n\n## Microsoft Teams\n\n### After the meeting\n\nYou'll find the attendance report in a few different places.\n\n### **In the meeting invite**\n\nIn Teams, go to **Calendar**, open the meeting, and select the **Attendance** tab. You can view the data directly in Teams.\n\n![](/api/knowledge-base/images/9cebc741-8bbd-4f78-a4b8-d8255463da84)\n\nFor recurring meetings, select the report you want to view from the dropdown list.\n\n![](/api/knowledge-base/images/075accfd-5a34-4be2-bcd3-68511e148b8d)\n\nTo download the attendance CSV file for the meeting, click **Download**.\n\n![](/api/knowledge-base/images/e1a3f6e0-4be5-4278-9781-8eb03eca12c1)\n\n### **In the meeting chat**\n\nA tile labeled **Attendance report** will pop into the chat about five minutes after your meeting ends. Select it to download the CSV file.\n\n![](/api/knowledge-base/images/ff47e701-f09e-4f35-929e-6c17ad3e90d4)\n\n## **In the meeting chat**\n\nA tile labeled **Attendance report** will pop into the chat about five minutes after your meeting ends. Select it to download the CSV file.\n\n![](/api/knowledge-base/images/27f6e854-57c8-45b5-9dd4-668b6e61e1e4)\n\n## Scheduled channel meetings\n\nTo view the attendance reports for meetings created in channels, click **More actions** > **View meeting details,** and navigate to the **Attendance** tab.\n\n![](/api/knowledge-base/images/e6bad847-c0cc-4901-a003-4dd863558c5b)\n\n![](/api/knowledge-base/images/ef74a2c2-488c-49d9-8ef6-0571121b13a9)\n\n## In-person Events\n\nTo record attendance for an in-person event, you can upload a list of attendee email addresses directly into Chezie.\n\n### File Format:\n\nBefore uploading, make sure you have:\n\n- **CSV (.csv)** file\n\n- One column containing **attendee email addresses only**\n\n **Notes:**\n\n - A header is optional but allowed\n\n - No additional columns, formatting, notes, or merged cells\n\n### How to Upload the Attendance File:\n\n1. Log in to Chezie and go to **Events**.\n\n2. Open the event you hosted.\n\n3. Click on **Event Actions**\n\n ![2.png](/api/knowledge-base/images/f10f954e-89c1-46a0-84b7-4ba041d9a1e7)\n\n4. Click **Upload attendance**.\n\n ![3.png](/api/knowledge-base/images/68896e26-471a-482c-ab72-d6d062a24586)\n\n5. Select your CSV file and **Submit**.\n\n ![4.png](/api/knowledge-base/images/041e5837-da7b-447c-b3e8-4b6159c66bcb)\n\n6. Wait while Chezie processes the attendee list.\n\n## Need Support?\n\nIf you encounter an error or need help matching attendees:\n\n- Email us at [**support@chezie.co**](mailto:support@chezie.co)","2026-04-16T19:06:51.837Z","2026-08-31T18:58:56.692Z","8a7d1964-7988-48bf-a24d-07b8277d2e08",[],[],[],"How to duplicate events","how-to-duplicate-events-chezie-2","### Streamline your event planning by duplicating existing events.\n\n```plaintext\nRather than creating the same event over and over, you can simply duplicate an event and use it again.\n```\n\n1. From Events, find the event you want to duplicate.\n\n2. Click the three dots and select 'Make a copy'.\n\n ![1.png](/api/knowledge-base/images/cea56ac3-b9f6-4211-86ee-c56ac4a639e7)\n\n3. That’s it!","2026-04-16T19:06:52.588Z","2026-08-25T20:34:59.201Z","719ae679-4e83-49d7-8b1a-450f7c3b8db5",[],[],[],"How to disable the event approval requirement","how-to-disable-the-event-approval-requirement-chezie-2","### How to disable the event approval requirement so Leads can approve their own events.\n\nGive your Group Leads more control over their programming by disabling the event approval requirements. When this is disabled, Leads can approve their own events.\n\nKeep in mind that you can limit which Leads can actually approve events by controlling which Leads have that [permission](https://docs.chezie.co/docs/chezie-2026/security/5543fb2b-7582-4774-a901-6f640700f7fe).\n\n1. Click Settings\n\n ![1.png](/api/knowledge-base/images/6a4eb102-08c8-4591-8714-a04c2524393e)\n\n\n2) Choose your team\n\n ![2.png](/api/knowledge-base/images/a1978b41-e5f6-43d3-b8e8-8c5bfd543f4a)\n\n\n3. Scroll down to Admin Controls. Toggle 'Events need to be approved first' to turn it on/off.\n\n ![3.png](/api/knowledge-base/images/ceb7478c-3ffe-4623-897a-f4dffe69b9fc)","2026-04-16T19:06:26.048Z","2026-08-25T20:25:21.456Z","c2a6714b-95dc-4a05-b9c0-995fd1a0b188",[],[],[],"How to copy an event’s landing page URL","how-to-copy-an-events-landing-page-url-chezie-2","### Quickly copy and share event landing page URLs for enhanced event promotion.\n\nEasily copy the URL for an event so you can share it with your members. Here’s how:\n\n1. From Events, select the event you want to share.\n\n ![1.png](/api/knowledge-base/images/51ce8588-1974-406b-a6b5-0614e91a87bf)\n2. Click on Event Actions\n\n ![2.png](/api/knowledge-base/images/5019bd7a-93a1-4c57-b333-1b9d373cdd3b)\n3. Click on Copy link\n\n ![3.png](/api/knowledge-base/images/b27a82d7-970f-44fa-aab2-26b16412e26d)","2026-04-16T19:06:52.727Z","2026-08-25T20:18:25.942Z","49b4ae73-bcbd-41ef-8e28-34a22a79f0e0",[],[],[],"How time zones work in Chezie","how-time-zones-work-in-chezie-chezie-2","### An explanation of how time zones work in Chezie.\n\n# Things to know about time zones in Chezie\n\n- Time zones in Chezie automatically adjust based on your current time zone.\n\n- Time zones also automatically adjust based on a recipient’s location.\n\n**For example:**\n\n1. If you are in New York City, Chezie auto-detects that you’re EST.\n\n2. If you schedule an event in Chezie at 12pm, it is being scheduled for 12pm EST.\n\n3. If someone in Los Angeles (PST) receives your event invite, their invite will be for 9am PST. If someone in London (GMT) receives your invite, their invite will be for 5pm GMT.\n\nPlease email us at [support@chezie.co](mailto:support@chezie.co) if you have any additional questions.","2026-04-16T19:06:25.883Z","2026-06-30T19:07:34.525Z","6b964486-393b-4c37-aec0-449ce8d4b31f",[],[],[],"Event NPS, explained","event-nps-explained-chezie-2","### Learn how NPS works and what each score means.\n\nNet Promoter Score, or NPS, measures your member's experiences with your Group events. This metric gives you a way to track the success of your events and get a better idea of what type of content your members want.\n\n![](/api/knowledge-base/images/47811fda-a89c-461c-90fe-22d94eb4bb0b)\n\n## **The NPS Calculation**\n\nCalculate your NPS using the answer to a key question, using a 0-10 scale:\n\n> _How likely are you to recommend this event to a friend or colleague?_\n\nRespondents are grouped as follows:\n\n- **Promoters** (score 9-10) are loyal enthusiasts who will keep joining your events and referring your Group's events to others, which powers growth.\n\n- **Passives** (score 7-8) are satisfied but unenthusiastic members who will neither promote nor talk badly about your events.\n\n- **Detractors** (score 0-6) are unhappy members who can damage your Group's reputation and impede growth through negative word-of-mouth.\n\n## **Formula**\n\n**NPS =** (% Promoters) - (% Detractors)\n\n## NPS Reporting Levels\n\n1. **All Groups** - shows you the cumulative NPS score for all survey responses across all Groups for the selected Cycle\n\n ![1.png](/api/knowledge-base/images/4a3aa2b3-3ff5-4370-bd64-4fe35bf7f259)\n\n2. **Single Group** view - shows you the cumulative NPS score for all survey responses for events that the selected group has hosted\n\n ![2.png](/api/knowledge-base/images/cd4fc49e-7fb6-4473-bd84-2ebd00eec7b3)\n\n3. **Single Event** view - shows you the NPS score for all survey responses for the selected event\n\n ![3.png](/api/knowledge-base/images/e62e17af-2955-41a2-8919-af3c60572c12)\n","2026-04-16T19:06:52.990Z","2026-08-25T20:10:33.402Z","f838b376-e2df-4210-9ab7-5b81b4082840",[],[],[],"Disabling Event Approvals","1. Go to **Settings**.\n\n ![1.png](/api/knowledge-base/images/36b58404-d0ea-4612-90b1-f46f3c1659dd)\n2. Select Team.\n\n ![2.png](/api/knowledge-base/images/017b1823-e404-4d5c-bfc0-5ed59a227b6e)\n3. Under **General** Team Settings, scroll down to **Admin Controls**.\n\n ![3.png](/api/knowledge-base/images/d4594871-9394-4618-a148-c8b50b7c4504)\n4. Toggle the button on/off.\n\n ![4.png](/api/knowledge-base/images/8cb3ef23-e810-47d1-890c-de5651148903)","2026-07-02T16:40:13.684Z","2026-08-04T16:31:35.711Z","723e8880-58d8-435f-aec1-a9768d7e8669",[],[],[],"Creating & Scheduling an Event","creating-scheduling-an-event","1\\. From **Events**, click on **New Event.**\n\n![57.png](/api/knowledge-base/images/1b6b518b-8642-40a0-8e0f-3abdca19fe57)\n\n2\\. Type Event title\n\n![58.png](/api/knowledge-base/images/02a98dc7-d0c2-4da7-a029-7499bcdb2eec)\n\n3\\. Choose Event date and time\n\n![59.png](/api/knowledge-base/images/2aff1dd3-24a7-437e-98ad-03b0925604b4)\n\n4\\. Select Cycle\n\n![60.png](/api/knowledge-base/images/38b403da-c248-4596-9a00-be944a2ffa67)\n\n5\\. Select Attached Goal\n\n![61.png](/api/knowledge-base/images/68fed9a6-a936-4b70-aaef-9f98f494607c)\n\n6\\. Select which Admin(s) are planning this Event.\n\n![62.png](/api/knowledge-base/images/4347aeb0-8ee5-403a-b9e9-ad043809100f)\n\n7\\. Select Location (Virtual or In-Person)\n\n![63.png](/api/knowledge-base/images/40563dbc-1397-49f2-a74e-46199ca57629)\n\n---\n\n```plaintext\nℹ️ For Virtual Events, ensure that the video system has been integrated. If so, select from the dropdown which system you will use, and Chezie will generate a meeting link.\n```\n\n---\n\n8\\. Type Event Description\n\n![64.png](/api/knowledge-base/images/91d308a2-f7e8-4a41-8b3b-d43a88330746)\n\n9\\. Click on Organizer\n\n![65.png](/api/knowledge-base/images/760f98d6-b897-4705-9ade-a0610c011e53)\n\n10\\. Click on Calendar\n\n![66.png](/api/knowledge-base/images/5f21850b-9ebc-4379-b784-a75a06f0c322)\n\n11\\. Click on Add Invitees\n\n![67.png](/api/knowledge-base/images/968e36e8-6168-46fb-8dfb-1e965fbc229c)\n\n12\\. Select Invitees (Select All for complete member list)\n\n![68.png](/api/knowledge-base/images/e9c3950f-7f98-49d1-90ea-4c94ab86d459)\n\n13\\. Click on Add Invitees\n\n![69.png](/api/knowledge-base/images/957f8703-c194-4aa1-8747-df91462d7e6c)\n\n14\\. Click on **Save as Draft.**\n\n![70.png](/api/knowledge-base/images/a5456835-6170-40e0-a0b8-9f446d581e5b)\n\n15\\. Click on **Submit for Approval.**\n\n![71.png](/api/knowledge-base/images/4293e48e-b424-4285-b903-1d5d90b65ef3)\n\n16\\. Click on Approvers and type in text field.\n\n![72.png](/api/knowledge-base/images/1768826a-f32e-4116-b6af-3d90f0e34327)\n\n17\\. Click on Send.\n\n![73.png](/api/knowledge-base/images/ee25e38b-e1d8-4fcd-b457-05869c2053ba)\n\n## FAQs\n\n## Adding a past event\n\nIf the event form prevents you from selecting a date or time that has already passed:\n\n1. Create each event and enter its event details.\n2. Set the event time in Chezie.\n3. Leave the event in **Draft** mode; do not submit it for approval.\n4. Send a list of the event names and their corresponding past dates and times to support@chezie.co.\n5. Support will update the dates on the backend while the events remain in Draft.\n\n**Q: How do I send an event to all groups under my team?**\n\nA: If you have multiple ERGs on your team and want to invite all of their members to one event, you don't need to add people one by one. When creating the event, add each of the relevant ERGs as co-hosts on the event. Then, on the invite screen, click \"Add Invitees\" and choose \"Select All\" — this will invite every member across all the co-hosting ERGs at once.","2026-07-01T13:19:42.774Z","2026-09-18T18:55:47.182Z","cb506682-de51-4370-928e-512a1498a37d",[],[],[],"Creating events with a Waitlist","waitlist-events","> Set a cap on RSVPs for any event and let Chezie handle the overflow. Once an event reaches capacity, new sign-ups are automatically placed on a waitlist — and if a spot opens up, everyone on the list is notified so the first person to claim it gets it.\n\n![image.png](/api/knowledge-base/images/bb7b87de-f4b9-4464-b190-c4aad45fb9aa)\n\n## Setting up a waitlisted event\n\n***Important:*** *Enabling a waitlist turns off automatic invites for that event.* \n\n1. Create your event as usual — name, date, location, description, and meeting type.\n\n2. Open **Advanced Options**.\n\n3. Check **Enable waitlist** and enter the number of spots available.\n\n ![image.png](/api/knowledge-base/images/1e4ef3ea-8b09-46a5-b6ce-a7d6d83062ad)\n\n4. Click **Save as Draft** to create the event.\n\n ![image.png](/api/knowledge-base/images/3d697692-1512-4358-912c-74918d061e4e)\n\n5. From there, approve the event.\n\n 1. If you’re a Team admin, click the Approve & Finalize button to approve the event directly.\n\n ![image.png](/api/knowledge-base/images/d4742fe2-cb49-476e-8151-57ea6277e366)\n\n 2. If you’re a Group Admin, request approval.\n\n6. Once the event is approved, you will be prompted to send the invite email.\n\n ![image.png](/api/knowledge-base/images/8343bb50-0713-4fb6-9be5-50be0bea4b45)\n\n7. In the **Communications** tab, draft your invite email. Be sure to **copy the event link** in the format bar, and paste that link into the email so invitees can register.\n\n ![image.png](/api/knowledge-base/images/a1d4becd-780a-4d4c-847d-c724d01eaa70)\n\n8. Send the email to whoever you’d like to invite.\n\n## What members experience\n\n1. **If a spot is available:**\\\n The member RSVPs and is automatically confirmed. Chezie sends the calendar invite for them — there's no \"Add to Calendar\" step to complete. The event is added directly to their calendar through their organization's connected account.\n\n2. **If the event is full:**\\\n The member sees an \"Event Full\" badge and can join the waitlist instead. They'll get a confirmation email letting them know they're on the list. No calendar invite goes out at this point, since they don't have a confirmed spot yet.\n\n ![image.png](/api/knowledge-base/images/fc350095-0a5d-4e31-8954-614fd812846b)\n\n3. **If a confirmed attendee drops out:**\\\n Chezie doesn't automatically promote the next person in line. Instead, **everyone currently on the waitlist gets an email** letting them know a spot has opened. It's first-come, first-served — whoever returns to Chezie and claims the spot first gets it. Once claimed, that member receives their calendar invite automatically, the same as any other confirmed attendee.\n\n## Leaving a waitlist or dropping from an event\n\nMembers can leave the waitlist at any time from the event page from the original email they received.\n\nTo cancel a **confirmed** spot, a member needs to use **Drop from Event** on the event page in Chezie — not just delete the event from their personal calendar. Deleting the calendar entry only removes it from their own view; it doesn't release the spot or update their status in Chezie.\n\n> 📣 **Organizers:** this is worth calling out explicitly when you invite people — members who assume deleting the calendar invite cancels their RSVP will unintentionally hold a spot open. We'd recommend a line in your invite communication like: *\"If you can no longer attend, please cancel from the event page in Chezie — removing it from your calendar alone won't release your spot.\"*\n\n## Managing a waitlisted event as an organizer or admin\n\n![image.png](/api/knowledge-base/images/76d2ef4b-e598-443a-b57d-cd20d085d860)\n\nFrom the event's **Invites** tab, you can see live counts for total spots, confirmed attendees, waitlisted members, and spots remaining.\n\n## FAQ\n\n1. **Do I need to connect my calendar to RSVP?**\\\n No. Chezie adds you to the event directly — there's nothing to connect or confirm on your end.\n2. **I joined a waitlist. Will I be notified in order?**\\\n No. There's no visible queue position, and promotion isn't based on when you joined. When a spot opens, everyone on the waitlist is notified at the same time.\n3. **I deleted the event from my calendar. Am I still going?**\\\n Yes — deleting a calendar entry doesn't cancel your registration in Chezie. Use **Drop from Event** on the event page to actually cancel.\n4. **Can I increase the RSVP cap after the event is published?**\\\n Yes – after creating a waitlisted event, the capacity can be changed however, increasing the capacity does not auto-promote members on the waitlist. Decreasing the cap also doesn’t remove anyone, already registered from the event if the cap is changed to something lower, than the current number of registrees.\n5. **What happens to my waitlist spot if the event gets canceled?**\\\n Waitlisted members are ***not*** notified about an event cancellation. You would need to email them from Chezie.","2026-08-04T16:32:28.192Z","2026-08-04T16:34:42.716Z","f2257cf1-df1c-43b7-8ebb-64db7e78b439",[],[],[],"Attendance & RSVPs","1\\. Click on **Events**.\n\n![74.png](/api/knowledge-base/images/30a2f694-187d-4d8d-9f9f-0180328da403)\n\n2\\. Click on **Past events**.\n\n![75.png](/api/knowledge-base/images/d874bcbd-34fb-46ea-8df8-02b225b637af)\n\n3\\. Select Event you want to view.\n\n![76.png](/api/knowledge-base/images/fc1fd84d-c07d-414f-b63c-2b4f8e338bbb)\n\n4\\. Click on **Attendees**.\n\n![77.png](/api/knowledge-base/images/36a61f5b-eb2b-4b80-bff6-2a9749c1f7a1)\n\n5\\. Click on **Feedback**.\n\n![78.png](/api/knowledge-base/images/a7ab6289-84a6-4132-96b3-aef29b9a3d21)","2026-07-01T13:24:54.478Z","2026-07-01T19:09:34.674Z","5d339021-63dd-4f83-8371-b2737d06a2b1",[],[],[],"Cycles","cycles","repeat","2026-08-26T21:02:09.059Z","c7e6e371-58c1-458d-afdc-597d773f2df8",[1174,1175,1176],[],{"_57":1195,"_103":1196,"_112":-5,"_113":1197,"_115":1171,"_116":62,"_117":1198,"_119":1199,"_22":1200,"_24":25,"_122":1201,"_124":-5,"_125":1202,"_127":1203},{"_57":1186,"_103":1187,"_112":-5,"_113":1188,"_115":1171,"_116":62,"_117":1189,"_119":1190,"_22":1191,"_24":25,"_122":1192,"_124":-5,"_125":1193,"_127":1194},{"_57":1177,"_103":1178,"_112":-5,"_113":1179,"_115":1171,"_116":62,"_117":1180,"_119":1181,"_22":1182,"_24":25,"_122":1183,"_124":-5,"_125":1184,"_127":1185},"How to edit or reactivate a cycle","how-to-edit-a-cycle-chezie-2","### How to edit or reactivate an existing cycle in Chezie\n\n1. Go to **Settings**.\n\n ![1.png](/api/knowledge-base/images/502c05c4-6fe1-432f-807e-2c7d0f6174b6)\n\n2. Select the team of the cycle you are editing or reactivating.\n\n ![2.png](/api/knowledge-base/images/254230f7-d5fa-4c91-89d8-2c096c78e190)\n\n3. Find the cycle you want to manage. Click the options/action icon beside the cycle.\n\n ![1.png](/api/knowledge-base/images/21364bb6-6202-4510-91cf-5c92b70492b5)\n\n4. To edit the cycle, select **Edit cycle**, make the updates, and click **Save changes**.\n\n ![2.png](/api/knowledge-base/images/cd36e015-1e68-45f9-8cf8-6001ae0054a0)\n\n5. To reactivate a previous cycle, use the options under Cycle status and select 'Active'.\n\n ![](/api/knowledge-base/images/269e001c-3249-49b4-9461-c1d8d07e5f55)\n\n6. The options to set the selected cycle as default, archive, or delete it are also controlled here. Only archived cycles can be deleted.\n\n ![3.png](/api/knowledge-base/images/8cb7e06c-e349-4e1c-b666-2974aebc5671)","2026-04-16T19:06:54.157Z","2026-09-03T15:37:29.211Z","0b11d8e7-34a1-4e14-a19d-d428986a5811",[],[],[],"How to create a new cycle","how-to-create-a-new-cycle-chezie-2","### Learn how to create a new Cycle in Chezie\n\n1. Go to Settings\n\n ![1.png](/api/knowledge-base/images/c7239e05-42f0-4450-9e73-a4e199f92cac)\n\n\n2) Select the team you are creating the cycle for.\n\n ![2.png](/api/knowledge-base/images/8c68980a-d2cf-495f-b194-ceab045b5d22)\n\n\n3. Scroll to Budget Cycles and select Create Cycle\n\n ![3.png](/api/knowledge-base/images/124d7d03-bce4-41d6-ae74-9190f0fd0ea4)\n\n\n4) Fill in the details of this cycle. If you would like to set this as the default cycle, you can do so by ticking the small box in the lower left corner.\n\n ![4.png](/api/knowledge-base/images/1f7daf87-42d6-4519-8532-58be18e7f38a)\n\n5. Click on Create Cycle once done.\n\n ![5.png](/api/knowledge-base/images/b4f518fe-97c8-4315-af62-65e3e06a3268)","2026-04-16T19:06:42.295Z","2026-08-26T21:02:27.151Z","af8193bb-1809-4345-ac37-7e81a7dc2d6e",[],[],[],"Cycles, explained","cycles-explained-chezie-2","### An explanation of how Cycles work in Chezie.\n\nAs DEI Managers and ERG leaders, it's important to be able to track spending and programming over various budgeting periods.\n\nWe're excited to introduce **Annual Cycles** - a way for you to associate programming to a specific period of time.\n\nExpenses and events are now automatically tied to a your current cycle (aka the 'default' cycle), and you have the ability to select an upcoming or past cycle for an expense or event as well.\n\n## **How it works**\n\nFor instructions on how to create a new cycle, read this [page](https://docs.chezie.co/docs/chezie-2026/expenses-3/how-to-create-a-new-cycle-chezie-2).\n\nCycles can be created for any duration of time. Simply select a start, end date, and an amount.\n\n![3.png](/api/knowledge-base/images/b38a72c5-e2ed-4b8c-afc4-9ba9ecb47ecb)\n\nNext, enter the amount of money that each selected Group has to spend in this cycle. Lastly, determine if this cycle is to be used as the default moving forward.\n\n![4.png](/api/knowledge-base/images/00555d5c-2da2-49a0-8ff8-f9fdc28ab0ca)","2026-04-16T19:06:42.181Z","2026-08-26T21:02:40.907Z","f25553bd-fdb5-4585-b92f-e1cd80bfc383",[],[],[],"Communications","communications-3","phone","2026-06-30T21:18:25.115Z","9bec4577-efeb-4240-bdb9-6dbde9adae4f",[1211,1212,1213],[],{"_57":1230,"_103":-5,"_112":-5,"_113":1231,"_115":1208,"_116":62,"_117":1232,"_119":1233,"_22":1234,"_24":25,"_122":1235,"_124":-5,"_125":1236,"_127":1237},{"_57":1222,"_103":-5,"_112":-5,"_113":1223,"_115":1208,"_116":62,"_117":1224,"_119":1225,"_22":1226,"_24":25,"_122":1227,"_124":-5,"_125":1228,"_127":1229},{"_57":1214,"_103":-5,"_112":-5,"_113":1215,"_115":1208,"_116":62,"_117":1216,"_119":1217,"_22":1218,"_24":25,"_122":1219,"_124":-5,"_125":1220,"_127":1221},"Sending an email from Chezie","# [Schedule and Send Chezie Comms](https://app.tango.us/app/workflow/693bf22d-5453-4b53-b89c-80eed30803fe?utm_source=magicCopy&utm_medium=magicCopy&utm_campaign=workflow%20export%20links)\n\n1\\. Click on Communications\n\n![1.png](/api/knowledge-base/images/b4a60f28-215a-4a76-b952-1606153ae80d)\n\n2\\. Click on Create comms\n\n![2.png](/api/knowledge-base/images/7636cbb2-66b7-4ccf-b47f-06b519c6e968)\n\n3\\. Type Subject line and message in text field\n\n![3.png](/api/knowledge-base/images/5ddb7b41-0bf8-4969-9a66-b7e80469f721)\n\n4\\. Select Cycle\n\n![4.png](/api/knowledge-base/images/313be9eb-2c83-4904-9ce0-a178a391208c)\n\n5\\. Select Related goal\n\n![5.png](/api/knowledge-base/images/42c27a54-d574-469e-935a-020e9b189988)\n\n6\\. Click on Schedule - Either Send Now or Schedule for Later\n\n![6.png](/api/knowledge-base/images/bab7f468-6bf3-4625-b8d9-741ace02cc89)\n\n---\n\n```plaintext\nℹ️ If you want to send the email immediately, the button will say \"Send.\" If you are scheduling it for later, the button will say \"Schedule.\"\n```\n\n---\n\n### 7. Click on Send\n\n![7.png](/api/knowledge-base/images/08cf61cd-56cb-4c9e-bdf4-58dc1ff61303)","2026-07-01T20:31:09.689Z","2026-07-01T20:35:21.773Z","976d030a-6b47-41c2-a373-3fb7e05b9889",[],[],[],"Editing a scheduled email","1\\. Click on **Communications**\n\n![1.png](/api/knowledge-base/images/4b55f18f-6a9e-4048-ab40-11db66be1925)\n\n2\\. Click on **Scheduled**\n\n![8.png](/api/knowledge-base/images/cf419248-078e-40ff-9554-4ca42d0a2588)\n\n3\\. Click on **Menu** and **Edit**\n\n![9.png](/api/knowledge-base/images/7e587d0e-ec32-418d-94d9-c4cfa91ba3e2)\n\n4\\. Edit Email\n\n![10.png](/api/knowledge-base/images/7b30157e-0b24-430f-b740-db0cf9c3e161)\n\n5\\. Click on **Schedule**\n\n![11.png](/api/knowledge-base/images/2c28a290-0fd5-4950-ac61-d1fbcfc3e67f)","2026-07-01T20:36:06.729Z","2026-07-01T20:39:31.406Z","bbafc788-4e62-4536-b455-605e3ecc7908",[],[],[],"Customizing your welcome email","1\\. Click on **Settings**\n\n![1.png](/api/knowledge-base/images/4dad5867-ea39-4123-b51c-d2a4bde86197)\n\n2\\. Click on Team\n\n![2.png](/api/knowledge-base/images/ba539f09-2511-4b31-9aa3-c630d3cfbbe7)\n\n3\\. Click on Group\n\n![3.png](/api/knowledge-base/images/19d0a5de-f51f-464e-ba6f-2ef874cfa301)\n\n4\\. Click on **Communications**\n\n![4.png](/api/knowledge-base/images/060f98f4-fab9-4328-ae64-3eacfef6f51d)\n\n5\\. Click on **Create Message**\n\n![5.png](/api/knowledge-base/images/e66828ff-d8b6-42be-894e-565efda8c402)\n\n6\\. Write in copy for email\n\n![6.png](/api/knowledge-base/images/be0123b3-2c2d-4b16-97b5-2b909d3e2c49)\n\n7\\. Click on **Save changes**\n\n![7.png](/api/knowledge-base/images/a4c439bb-355f-417e-9786-ec8adf4450c9)","2026-07-01T20:41:07.245Z","2026-07-01T20:44:32.892Z","8cf8ee89-72e2-4244-8beb-3e3cfaff0970",[],[],[],"Account & Security","security","Chezie is SOC2 and pending GDPR compliance. Browse the pages below for more information about our security policies.","lock","2026-04-16T19:04:35.318Z","2026-06-30T21:20:29.215Z","6cd1d618-1836-4f3a-8b34-d6d1913e8027",[1247,1248,1249,1250,1251],[],{"_57":1288,"_103":-5,"_112":-5,"_113":1289,"_115":1244,"_116":62,"_117":1290,"_119":1291,"_22":1292,"_24":25,"_122":1293,"_124":-5,"_125":1294,"_127":1295},{"_57":1279,"_103":1280,"_112":-5,"_113":1281,"_115":1244,"_116":62,"_117":1282,"_119":1283,"_22":1284,"_24":25,"_122":1285,"_124":-5,"_125":1286,"_127":1287},{"_57":1270,"_103":1271,"_112":-5,"_113":1272,"_115":1244,"_116":62,"_117":1273,"_119":1274,"_22":1275,"_24":25,"_122":1276,"_124":-5,"_125":1277,"_127":1278},{"_57":1261,"_103":1262,"_112":-5,"_113":1263,"_115":1244,"_116":62,"_117":1264,"_119":1265,"_22":1266,"_24":25,"_122":1267,"_124":-5,"_125":1268,"_127":1269},{"_57":1252,"_103":1253,"_112":-5,"_113":1254,"_115":1244,"_116":62,"_117":1255,"_119":1256,"_22":1257,"_24":25,"_122":1258,"_124":-5,"_125":1259,"_127":1260},"Privacy Policy","privacy-policy-chezie-2","**Effective Date:** *12/14/2022*\\\n**Last Updated:** *4/1/2025*\n\nDyversifi Inc. (“Chezie,” “we,” “our,” or “us”) is committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you visit our platform or use our services. It also outlines your rights and choices regarding your personal data, in accordance with applicable privacy laws including the General Data Protection Regulation (GDPR).\n\n## **1. Information We Collect**\n\nWe collect personal data that you voluntarily provide when using our services, including:\n\n- Contact details (name, email, organization)\n\n- Authentication credentials\n\n- ERG membership and participation data\n\n- User preferences and communications\n\n- Usage data (via log files and analytics)\n\nWe do not knowingly collect personal data from children under 16.\n\n## **2. How We Use Your Information**\n\nWe use your data to:\n\n- Provide, maintain, and improve our services\n\n- Authenticate and manage user access\n\n- Enable ERG operations, communication, and reporting\n\n- Ensure security and prevent fraud\n\n- Comply with legal obligations\n\n## **3. Legal Bases for Processing**\n\nUnder the GDPR, we process your personal data based on the following legal grounds:\n\n- Consent – where you have provided consent\n\n- Contractual necessity – to perform a contract with you\n\n- Legitimate interests – for analytics, platform improvement, and customer support\n\n- Legal obligation – to comply with applicable laws\n\n## **4. Data Sharing and Transfers**\n\nWe do not sell your personal data. We may share it with:\n\n- Authorized personnel and subcontractors under NDA\n\n- Third-party processors (e.g., for hosting and analytics), listed in our [Third-Party Sub-Processor List](https://drive.google.com/file/d/1tI7XaTtLIxDHUV9YYaa7qagLrDfVlAvU/view?usp=sharing)\n\n- Regulatory authorities if legally required\n\nData may be transferred to the United States and is protected by appropriate safeguards including data processing agreements and SOC 2 compliance.\n\n## **5. Data Retention**\n\nWe retain your data as long as necessary to provide services and fulfill legal obligations. Upon contract termination, Customer Data is available for retrieval for 90 days before permanent deletion.\n\n## **6. Your Rights**\n\nYou have rights under the GDPR, including to:\n\n- Access and obtain a copy of your data\n\n- Rectify incorrect or incomplete data\n\n- Request deletion (“right to be forgotten”)\n\n- Restrict or object to processing\n\n- Port your data to another service\n\n- Withdraw consent at any time\n\nTo exercise your rights, contact us at [**support@chezie.co**](mailto:support@chezie.co).\n\n## **7. Security Measures**\n\nWe use industry-standard security controls, including:\n\n- Encryption of data in transit and at rest\n\n- Role-based access controls\n\n- Regular audits and vulnerability scanning\n\n- Hosting with SOC 2-compliant providers (DigitalOcean)\n\nFor more details, see our [Security Handbook](https://www.notion.so/chezie/Chezie-Security-Handbook-PUBLIC-b9d2a04efe7945c68b139b6a2b9abfcc?pvs=4).\n\n## **8. Cookies and Tracking**\n\nWe use cookies to:\n\n- Enable essential platform functionality\n\n- Understand user behavior and improve service\n\nYou can manage cookie preferences in your browser settings.\n\n## **9. Changes to This Policy**\n\nWe may update this Privacy Policy from time to time. Any changes will be posted on this page with an updated “Last Updated” date.\n\n## **10. Contact Us**\n\nFor questions or concerns about this Privacy Policy or our data practices, contact:\n\n**Dyversifi Inc. (Chezie)**\\\n1445 Woodmont Ln NW, Suite 1861, Atlanta, GA 30318\\\nEmail: [**support@chezie.co**](mailto:support@chezie.co)","2026-04-16T19:06:36.471Z","2026-04-17T21:08:23.525Z","e102a387-0a25-4c0b-9308-e4e492b1a229",[],[],[],"Notifications Inventory","notifications-inventory","*Here is a list of all notifications that come from Chezie.*\n\n---\n\n## Member Added to New Group\n\n- **Subject:** You have been added to \\[Group Name\\]!\n- **Description:** Sent when someone is added to a group, includes link to finish joining\n- **Body:** Hi! You have been added to \\[Group\\] by \\[Name\\]! You should finish joining in Chezie! Click the link below to log in and finish joining this Group. Finish joining: \\[link\\]\n- **Sender:** [app@chezie.co](mailto:app@chezie.co)\n- **Customizable:** No\n\n---\n\n## Join Request\n\n- **Subject:** Request to join \\[Group Name\\]\n- **Description:** Alerts group admins when someone requests to join their group\n- **Body:** \\[Name\\] has requested to join \\[Group Name\\]! Go to your group's settings page to review the request (scroll to the bottom of the page to see them). \\[link to group\\]\n- **Sender:** [app@chezie.co](mailto:app@chezie.co)\n- **Customizable:** No\n\n---\n\n## Join Request Acceptance\n\n- **Subject:** Your request to join \\[Group Name\\] has been accepted!\n\n- **Description:** Welcome message sent to new members when their join request is approved, includes onboarding\n\n- **Body:**\\\n Hi there,\n\n Welcome to \\[Group Name\\]! We're so excited to have you join our community \\[Group Description\\] at \\[Company Name\\].\n\n Here's how you can get started:\n\n - Join our \\[link to Group Channel\\] to connect with the community and stay updated\n - Keep an eye out for upcoming events like workshops, networking opportunities, and volunteer activities\n - Explore our Resources Library for tools and materials to support personal and professional growth\n\n If you have any questions, feel free to contact the \\[Group Name\\] Leadership Team at \\[Group/Lead Email\\].\n\n We're excited to have you with us and look forward to making a lasting impact together!\n\n Best, \\[Group Name\\] Leadership Team\n\n- **Sender:** [app@chezie.co](mailto:app@chezie.co)\n\n- **Customizable:** No\n\n---\n\n## Welcome Messages\n\n- **Subject:** Welcome to \\[Group Name\\]!\n- **Description:** General welcome message sent to new group members with group-specific information and resources\n- **Body:** Welcome to \\[Group Name\\]! \\[Welcome Message\\]\n- **Sender:** [app@chezie.co](mailto:app@chezie.co)\n- **Customizable:** Yes\n\n---\n\n## Event Status Change\n\n- **Subject:** \\[Group Name\\] - \\[Event Name\\] - Change Requested\n- **Description:** Notifies when changes are requested for a pending event\n- **Body:** \\[Details of event updates\\]\n- **Sender:** [app@chezie.co](mailto:app@chezie.co)\n- **Customizable:** No\n\n---\n\n## Attendance Upload\n\n- **Subject:** Attendance uploaded - \\[Event Name\\]\n- **Description:** Sent to admins when event attendance data has been uploaded, includes download link\n- **Body:** Attendance has been uploaded for \\[Event Name\\]. Uploaded by: \\[Name\\]. Download the required data here: \\[link to event page\\]\n- **Sender:** [app@chezie.co](mailto:app@chezie.co)\n- **Customizable:** No\n\n---\n\n## Event Approval Request\n\n- **Subject:** New Event - \\[Event Name\\]\n- **Description:** Sent to admins when an ERG requests event approval\n- **Body:** Hi! \\[Group Name\\] is requesting your approval on the following event: \\[Event Title\\]. Click the link below to review and approve the event. \\[link to event page\\]\n- **Sender:** [app@chezie.co](mailto:app@chezie.co)\n- **Customizable:** No\n\n---\n\n## Event Approval\n\n- **Subject:** Your event has been approved! - \\[Event Name\\]\n- **Description:** Notifies organizers when an event is approved, confirms calendar invites will be sent\n- **Body:** Hi! Your event \\[Event Title\\] has been approved by \\[Name\\]. We're sending calendar invitations out to the invitees. See you there!\n- **Sender:** [app@chezie.co](mailto:app@chezie.co)\n- **Customizable:** No\n\n---\n\n## Calendar Invitations\n\n- **Subject:** Invitation: \\[Event Name\\] @ \\[Date/Time\\]\n\n- **Description:** Sent when events are approved; includes details, location, RSVP options\n\n- **Body:** \\[Event description as entered in Chezie\\]\n\n- **Sender:** Company Service Account","2026-06-30T19:00:59.161Z","2026-06-30T21:22:11.860Z","a5116eb1-603b-4f33-af7c-941253732180",[],[],[],"Chezie Security Handbook","chezie-security-handbook-chezie-2","### A comprehensive document of all of our security practices.\n\n## Documentation\n\n 1. **Access Control Policy**\n\n [Access Control Policy Doc](https://drive.google.com/file/d/1sY2mqTZrkec778cr8OVfBynfE-fe3g3Q/view?usp=sharing)\n\n 2. **Asset Management Policy**\n\n [Asset Management Policy Doc](https://drive.google.com/file/d/1nDPG_U4yafkZ2Kzce9cD1DwQ7y4LjzNH/view?usp=sharing)\n\n 3. **Incident Response Plan**\n\n [Incident Response Plan](https://drive.google.com/file/d/123k8r3qHH6ijVsm9ZkipxAeJlVI1TDOV/view?usp=sharing)\n\n 4. **Data Classification Matrix**\n\n [Data Classification Matrix Doc](https://docs.google.com/spreadsheets/d/1ClG76W4NFwAihnppf91sIdE4axWxvsETBbLeEyxyQjU/edit?usp=sharing)\n\n 5. **Business Continuity and Disaster Recovery**\n\n [Business Continuity and Disaster Recovery Doc](https://drive.google.com/file/d/1EtAk63xOHpQhwCOw6f4DYeWGWnvd-Gr7/view?usp=drive_link)\n\n 6. **Data Flow Diagram**\n\n [Data Flow Diagram Doc](https://drive.google.com/file/d/1mZSnGDXnBwIsgJGcMHD3YFlHTCaY_WaB/view?usp=sharing)\n\n 7. **Third-Party Integration Sequence Diagram**\n\n [Third-Party Integration Sequence Diagram Doc](https://drive.google.com/file/d/1aGsRmZa3FH4FvSXsDeSh5LdJ6jWZ5sp7/view?usp=share_link)\n\n 8. **Data Management Policy**\n\n [Data Management Policy Doc](https://drive.google.com/file/d/1AARV44-47Q9m_rPEontm017eIub2xZsh/view?usp=sharing)\n\n 9. **Third-Party Management Policy**\n\n [Third-Party Management Policy Doc](https://drive.google.com/file/d/1CBjIh8UI97Vd1QfQYeHL5YTtx0gweMHI/view?usp=sharing)\n\n10. **GDPR Compliance Policy**\n\n [GDPR Compliance Policy Doc](https://drive.google.com/file/d/1ITbIHDIKhUt8JB3IvkV5JE-_1hrPnNsS/view?usp=sharing)\n\n11. **Human Resource Security Policy**\n\n [Human Resource Security Policy Doc](https://drive.google.com/file/d/123lmPkb7H_sl8pSX7hCvFlCMO4QOF8WS/view?usp=sharing)\n\n12. **Risk Management Policy**\n\n [Risk Management Policy Doc](https://drive.google.com/file/d/1Mo-4oo43LCYgG3txIgQ8WXKgbbRYRn8t/view?usp=sharing)\n\n13. **Information Security Policy**\n\n [Information Security Policy Doc](https://drive.google.com/file/d/1tI7XaTtLIxDHUV9YYaa7qagLrDfVlAvU/view?usp=sharing)\n\n14. **SOC2**\n\n [Dyversifi SOC 2 Type 2 Report](https://drive.google.com/file/d/1VqbOMV60hjqbpJfCEiEjWsV-TvIABqAP/view?usp=sharing)\n\n15. **Change Control**\n\n [Change Control Policy](https://drive.google.com/file/d/1at6_xl8NQvhYA4qfu7raYqRNzQNzpEi1/view?usp=share_link)\n\n16. **Privacy and Data Protection**\n\n [**Privacy and Data Protection**](https://docs.google.com/document/d/1QAVQvPcDeAGPxKvl0nWPECTlM4Ws5x_x/edit?usp=drive_link&ouid=103217826087718612853&rtpof=true&sd=true)\n\n## Business Information\n\n 1. **Company Name**\n\n Dyversifi Inc.\n\n 2. **Name of product, service**\n\n Chezie for ERGs.\n\n 3. **Do products, services, or systems require network connectivity between parties?**\n\n Yes.\n\n 4. **Do the products, services, or systems require remote access between parties?**\n\n No.\n\n 5. **Products, services, or systems that require system-to-system integration?**\n\n Yes. Integrations to your\n\n - Video meeting software (i.e. Zoom, MS Teams, or Google Meet)\n\n - Chat software (i.e. Slack or MS Teams)\n\n - Calendar (i.e. Google or Outlook Calendar)\n\n 6. **Are technology or software applications provided?**\n\n Yes.\n\n 7. **List the names of the applications provided that are in scope.**\n\n Chezie.\n\n 8. **Technology or software is being provided?**\n\n Commercial Off-The-Shelf.\n\n 9. **Hosting Model included as part of this service.**\n\n DigitalOcean\n\n10. **Type of Cloud Computing service(s) provided.**\n\n Software as a Service.\n\n11. **Company website URL**\n\n [https://www.chezie.co](https://www.chezie.co/)\n\n## Enterprise Risk Management\n\n1. **Is there a formalized risk governance plan approved by management that defines the Enterprise Risk Management program requirements?**\n\n Yes there is a formalized risk governance plan.\n\n2. **Does the risk governance plan include risk management policies, procedures, and internal controls?**\n\n Chezie’s Risk Governance Plan is guided by procedures and our risk management policy. [Please see Risk Management Policy](https://docs.google.com/document/d/16yFrnYdBQY9S9RYxv-I8U0ZdQ7MqMJwX8VeA3OuZwcs/edit#bookmark=id.ej4zdbb5xdsa)\n\n3. **Is there a documented third-party risk management program in place for the selection, oversight and risk assessment of third parties (e.g., subcontractors, suppliers, service providers, dependent service providers, sub-processors) in scope for the services?**\n\n Currently, we do not have a third-party risk management program, but we have plans to implement one in the near future.\n\n4. **Are annual internal risk assessments performed?**\n\n Yes. All annual risk assessments are performed in-house.\n\n5. **Does your organization maintain an internal risk register for tracking and remediating risks?**\n\n As part of our risk governance plan, we maintain an internal risk register.\n\n6. **How often is the risk register reviewed internally?**\n\n We review our risk register annually.\n\n## Information Security Policy\n\n1. **Is there a set of information security policies that have been approved by management, published, and communicated to constituents?**\n\n Yes, please see [Information Security Policy.](https://docs.google.com/document/d/16yFrnYdBQY9S9RYxv-I8U0ZdQ7MqMJwX8VeA3OuZwcs/edit#bookmark=id.reemlkmxewst)\n\n2. **Do the information security policies and procedures establish requirements for the protection of information that is processed, stored or transmitted on external systems?**\n\n The information security policies and procedures establish requirements for the protection of information. We follow industry-standard best practices to ensure all information we handle is done so with security in mind.\n\n3. **Have all information security policies and standards been reviewed in the last 12 months?**\n\n All information security policies have been reviewed in the last 12 months.\n\n## Asset and Information Management\n\n1. **Asset Management Program**\n\n Please refer to our asset [management policy.](https://drive.google.com/file/d/1nDPG_U4yafkZ2Kzce9cD1DwQ7y4LjzNH/view?usp=sharing)\n\n2. **Where is client data stored geographically**\n\n DigitalOcean West Region, DigitalOcean East Region (backup).\n\n3. **Do you logically and physically segregate production and non-production environments? How do you ensure Production Data is not to be replicated or used in your test environments?**\n\n There is a logical and physical disassociation between local environments and remote environments. Our data models are built before a line of code is written so we're able to develop locally with dummy data that matches (in shape) to the data that lives in our servers.\n\n## Personnel Security\n\n1. **Is there an acceptable use policy for information and associated assets that has been approved by management, communicated to appropriate constituents, and assigned an owner to maintain and periodically review the policy?**\n\n Please refer to our [Information Security Policy](https://drive.google.com/file/d/1tI7XaTtLIxDHUV9YYaa7qagLrDfVlAvU/view?usp=sharing). This policy is regularly reviewed and updated.\n\n2. **Are all employees and contractors required to acknowledge/sign your organization's acceptable use policy upon hire?**\n\n Yes.\n\n3. **Is required annual information security awareness training completed by all organization personnel?**\n\n Yes, we require all employees and stakeholders to complete information security awareness training.\n\n## Physical and Environmental Security\n\n1. **Is there a physical security policy approved by management, communicated to constituents, and has an owner been assigned to maintain and review?**\n\n Data is housed with DigitalOcean, they are an industry leader in physical data storage. DigitalOcean writes and implements best practices.\n\n2. **Can your organization's constituents physically access scoped data for this engagement?**\n\n No, all of the data lives in the cloud (DigitalOcean)\n\n3. **Is authentication required for physical access to scoped data?**\n\n Physical access is not possible.\n\n## Change Management\n\n1. **Is there an operational Change Management/Change Control policy and process that has been documented, approved by management, communicated to appropriate personnel and assigned an owner to maintain and review the policy?**\n\n Yes, please refer to our [Change Control Policy.](https://docs.google.com/document/d/16yFrnYdBQY9S9RYxv-I8U0ZdQ7MqMJwX8VeA3OuZwcs/edit#bookmark=id.vhcfy5iqohbj)\n\n## Access Control\n\n1. **How does Chezie access a client’s data?**\n\n All data collected by Chezie is explicitly provided by the user through the use of online forms or with user permission through third-party integrations.\n\n2. **Does Chezie get access to a client’s system to provide a service?**\n\n Chezie will not access a client’s system to provide service. If a client gives Chezie access to any system it will only be to gather data relevant to Chezie’s data model. Chezie does not blindly scrape proprietary/sensitive data.\n\n3. **Will data Chezie collects be transferred to other region(s)?**\n\n In compliance with Chezie’s backup policy, currently, any data moved to another region will be restricted to safeguard data from a centralized disaster or critical event.\n\n4. **Are Chezie’s employees and contractors able to access scoped data?**\n\n Chezie’s employees are instructed not to access scoped data unless explicitly asked to by relevant stakeholders or for blind testing purposes and to explore anomalies.\n\n5. **Are unique IDs required for authentication to applications, operating systems, databases and network devices.**\n\n Yes, unique IDs are required for authentication purposes.\n\n6. **Does Chezie’s password policy require keeping passwords confidential?**\n\n Yes.\n\n7. **Is Multi-factor Authentication required in order to access scoped data?**\n\n Yes.\n\n8. I**s there a process for reviewing access?**\n\n We limit IAM permissions and access to a select group of people and limit permissions to the lowest possible level. We regularly review access permissions.\n\n9. **Are Access privileges revoked when an employee is terminated?**\n\n Yes. We make the adjustment within 24 hours of the employee’s termination.\n\n## Application Security and SDLC\n\n1. **Are applications used to transmit, process or store scoped data?**\n\n Yes, applications are used to transmit and process data.\n\n2. **Do you follow a Secure SDLC methodology, please describe. Please include a description of your SDLC methodology. You may provide the table of contents for your Secure SDLC procedure.**\n\n We currently adhere to SLDC, we plan on integrating the security aspect of this by associating annual pen testing before deployment of our V2 dashboard coming out in early 2023.\n\n Our Process:\n\n - Design\n\n - Development\n\n - Testing\n\n - Deployment and Maintenance\n\n## Cybersecurity Incident Management\n\n1. **Is there an established Cybersecurity Incident Management Program that has been approved by management, communicated to appropriate constituents and an owner to maintain and review the program?**\n\n Yes.\n\n2. **Is there a formal Incident Response Plan that includes an escalation procedure?**\n\n Yes, [please refer to Incident Response Plan](https://drive.google.com/file/d/1Uxf92Cu0B_TAL7XDMFn9qxYI6ZAsRihl/view?usp=share_link)\n\n3. **Are events on Scoped Systems or systems containing Scoped Data regularly reviewed and monitored to uncover potential incidents?**\n\n Through regular maintenance of our firewall and restricted network access, we limit IAM permissions and access to a select group of people. We monitor data coming into our servers regularly, identify unusual traffic, and log and patch any bugs.\n\n4. **Is there a staffed form of communication (e.g., e-mail, web form, phone, etc.) available to customers/clients 24/7/365 to report security incidents?**\n\n Yes. All issues can be communicated in-app or to [support@chezie.co.](mailto:support@chezie.co)\n\n## Contingency Planning - BCP & DR\n\n1. **Are formal business continuity procedures developed and documented?**\n\n [Please refer to our business continuity and disaster planning](https://drive.google.com/file/d/1EtAk63xOHpQhwCOw6f4DYeWGWnvd-Gr7/view?usp=drive_link).\n\n2. **Is there a formal, documented Information Technology Disaster Recovery exercise and testing program in place?**\n\n Yes.\n\n3. **Are there any dependencies on critical third-party service providers?**\n\n Yes, DigitalOcean has daily snapshots of our DB. These DB images are accessible and stored securely on the cloud.\n\n4. **Has the organization established processes for third-party service providers to provide immediate notification in the event of a disruption that impacts delivery of the products and/or services they provide?**\n\n Immediately. We have a response point person that will notify in the event of a breach. We will contact affected partners through email, Slack, text, phone (through as many mediums we have at our disposal).\n\n5. **Is there a policy or process for the backup of production data?**\n\n Yes. 3-2-1 Backup strategy. 3 copies of data, two backups. Two different DigitalOcean DB services, 1 copy of data in a different region.\n\n6. **Is scoped data backed up and stored offsite?**\n\n Yes.\n\n7. **What is the location (entity name and location) of any backup site(s)?**\n\n DigitalOcean - NYC1 - New York City, United States\n\n8. **Is there a formal process focused on identifying and addressing risks of disruptive events to business operations?**\n\n Yes.\n\n9. **Is there a data retention policy or process with a retention schedule?**\n\n Generally, we keep data for as long as it is relevant. A company can request data deletion at any point.\n\n\\*\\****Subject to change***\n\n## Endpoint Device Security\n\n1. **Are End User Devices (Desktops, Laptops, Tablets, Smartphones) used for transmitting, processing, or storing scoped data?**\n\n All transmission, processing, and storing of scoped data is done on DigitalOcean.\n\n2. **Are there documented end-user device security configuration standards?**\n\n Every device must be secured with anti-virus protection, and employees are not allowed to use unsecured networks with devices that access company data. We require employees to always keep their OS's up to date and download the latest security patches. Employees are not allowed to download illegal or pirated content with devices used to access company data.\n\n3. **Are there documented end-user device security configuration standards?**\n\n [Refer to 2.](https://docs.google.com/document/d/16yFrnYdBQY9S9RYxv-I8U0ZdQ7MqMJwX8VeA3OuZwcs/edit#bookmark=id.6edh2d4i5jl)\n\n4. **Is there a mobile device management program in place that has been approved by management and communicated to appropriate constituents?**\n\n [Refer to 2](https://docs.google.com/document/d/16yFrnYdBQY9S9RYxv-I8U0ZdQ7MqMJwX8VeA3OuZwcs/edit#bookmark=id.6edh2d4i5jl)\n\n5. **Are non-company-managed computing devices used to connect to the company network and store scoped data?**\n\n No, none of the above.\n\n## Server Security\n\n 1. **Are End User Devices (Desktops, Laptops, Tablets, Smartphones) used for transmitting, processing or storing Scoped Data?**\n\n Yes, servers are used for transmitting and processing Scoped Data.\n\n 2. **Are server security standards reviewed and/or updated at least annually to account for any changes in environment, available security features and/or leading best practices?**\n\n Yes, we regularly review our server security standards and apply any patches or updates as available and necessary.\n\n 3. **Are all unnecessary/unused services uninstalled or disabled on all servers?**\n\n Yes, all unnecessary/unused ports, services, and whitelists are disabled on our servers.\n\n 4. **Are vendor default passwords removed, disabled, or changed prior to placing any device or system into production?**\n\n Yes, Chezie does not keep default passwords.\n\n 5. **Are all systems and applications patched regularly?**\n\n Chezie patches systems as patches become available.\n\n 6. **Are there any Operating System versions in use within the Scoped Services that no longer have patches released? If yes, please describe in the Additional Information section.**\n\n Currently, Chezie does not use unserviced/unmaintained OS versions.\n\n 7. **Is there an anti-malware policy or program that has been approved by management, and communicated to appropriate constituents and an owner to maintain and review the policy?**\n\n Every device must be secured with an anti-virus, employees are not allowed to use unsecured networks with devices that access company data, we require employees to always keep their OS's up to date and download the latest security patches. Employees are not allowed to download illegal or pirated content with devices used to access company data. Coupled with some other of our device policies and education surrounding the engagement of dubious profiles in social media, dubious text messages, and dubious emails and URL links.\n\n 8. **What measures do you take to ensure your APIs are secure?**\n\n Accessed through a short-lived JWT associated with a refresh token. We limit the depth and rates that users can hit our API.\n\n 9. **Please describe the detection and protection technologies in place to identify anomalies in the corporate and production environment.**\n\n We currently use CloudWatch anomaly detection to look for a detect for anomalies.\n\n10. **Certificate Management**\n\n Chezie uses AWS certificate manager, which automates the process of renewing our SSL/TLS certificates and keys. (AWS is used for domain management and related operations).\n\n11. **Encryption Standards**\n\n Chezie uses DigitalOcean’s MongoDB services which are encrypted at rest. In transit data travels through SSL.\n\n## Network Security\n\n1. **Is there a policy that defines network security requirements that is approved by management, communicated to Constituents, and has an owner to maintain and review?**\n\n Yes. All networks must be secured with a strong password and updated with the latest security updates.\n\n2. **Are there security and hardening standards for network devices, including Firewalls, Switches, Routers and Wireless Access Points (baseline configuration, patching, passwords, Access control)?**\n\n [Refer to 1](https://docs.google.com/document/d/16yFrnYdBQY9S9RYxv-I8U0ZdQ7MqMJwX8VeA3OuZwcs/edit#bookmark=id.aenua382zzf3)\n\n3. **Is there a policy that defines the requirements for remote access from external networks to networks containing Scoped Systems and Data that has been approved by management and communicated to constituents?**\n\n Yes.\n\n4. **Are encrypted communications required for all remote network connections from external networks to networks containing Scoped Systems and Data?**\n\n Yes.\n\n5. **Are Network Intrusion Detection/Prevention capabilities employed e.g., appliance, software, etc.?**\n\n Yes, we employ firewall(s) as a preventative mechanism.\n\n6. **Is there a DMZ environment within the network that transmits, processes or stores Scoped systems and data e.g., web servers, DNS, directory services, remote access, etc.?**\n\n No DMZ environment is currently in place.\n\n7. **Is there a wireless policy or program that has been approved by management, communicated to appropriate constituents and an owner to maintain and review the policy?**\n\n [Refer to policy SS.7.](https://docs.google.com/document/d/16yFrnYdBQY9S9RYxv-I8U0ZdQ7MqMJwX8VeA3OuZwcs/edit#bookmark=id.6edh2d4i5jl)\n\n8. **Encrypted connections**\n\n All of our traffic goes over SSL/TLS.\n\n## Threat and Vulnerability Management\n\n1. **Is there a documented vulnerability management policy or program that has been approved by management, communicated to appropriate constituents and an owner assigned to maintain and review the policy?**\n\n Chezie’s VMP can be summarized as:\n\n - Assess our Assets\n\n - For vulnerabilities\n\n - Prioritize vulnerabilities\n\n - Assign Value\n\n - Gauge threat exposure\n\n - Add threat context\n\n - Act\n\n - Reassess\n\n - Improve\n\n In this vein, we attempt to identify threats before we have incidents,\n\n improve processes, and follow best practices.\n\n2. **Has your organization implemented scanning tools to identify any software vulnerabilities on systems in the organization?**\n\n We use Nmap to target our infrastructure resources (server(s), db, buckets \\[spaces\\]) and automatically scan for vulnerabilities.\n\n3. **How often is vulnerability scanning performed for systems that process or store Scoped Data?**\n\n Scanning is performed daily.\n\n4. **Does the organization maintain policies, standards and procedures for identifying and managing supply chain risks (i.e. ensuring software and hardware components used as part of delivering a service or product do not present a risk)?**\n\n Yes.\n\n5. **Does your organization perform annual penetration testing?**\n\n Find a copy of our latest penetration report below. Please note that we are working on the DNS records that would bring our grade to an “A.”\n\n [2025 Chezie Penetration Test](https://drive.google.com/file/d/1JH1EjgeCoT6fKvB2K-r5RLILdMBShwXw/view?usp=sharing)\n\n **Patch Strategy**\n\n For non-production, we simply keep all of our devices and OS's up to date with the latest versions and use them in only secure networks. For production we scan our DigitalOcean Droplets for applicable OS patches, identify patches, group instances at a suitable time and report patching compliance across the server environment.\n\n6. **Ransomware Prevention**\n\n We utilize the following:\n\n - Data backups\n\n - Regular system maintenance and up keep firewalls ,\n\n - Endpoint security\n\n - on access to our production server\n\n - Team training on suspicious activities that have led to opening access to strangers, no useless network/port access\n\n7. **Baseline Practices**\n\n In addition to the aforementioned, we disable unused networks and services, regularly audit and modify network rules and access privileges, and reconfigure our network firewall as needed.\n\n## Compliance and Operational Risk\n\n1. **Are there policies and procedures to ensure compliance with applicable legislative, regulatory and contractual requirements?**\n\n Yes, we have a suite of policies that adhere to all applicable compliance regulations.\n\n2. **Is there an internal audit, risk management, or compliance department, or similar management oversight function with responsibility for tracking the resolution of outstanding regulatory or compliance issues?**\n\n Chezie contracts a third-party auditor to look over all of our regulatory policies and practices to ensure all of our policies and standards meet compliance where we operate.\n\n3. **Is there a compliance program or set of policies and procedures in place to restrict activities or transactions for sanctioned countries (e.g., country blocking)?**\n\n We do not work with sanctioned countries.\n\n4. **Are documented policies and procedures maintained to enforce applicable legal, regulatory or contractual cybersecurity compliance obligations?**\n\n See responses COR1 (Compliance and Operational Risk) and COR2\n\n## Third Party Sub-Processors\n\n| **Name** | **Services Rendered** | **Data Processed** | **Corporate Domicile** | **Default Hosting Region** | **More Information** |\n| --- | --- | --- | --- | --- | --- |\n| **Bubble** | Development platform | User data, application data | Bubble Group, Inc. – United States (New York) | US cloud infrastructure (AWS US regions by default; other regions via enterprise arrangements) | |\n| **DigitalOcean** | Cloud hosting and infrastructure services | Server data, user data | DigitalOcean Holdings, Inc. – United States (New York) | Region-based; multiple US regions (data stored in selected region) | |\n| **SendGrid (Twilio SendGrid)** | Email delivery service | Email content, recipient data (email address) | Twilio SendGrid, Inc. – United States (Denver, Colorado) | Primarily US-based infrastructure on major cloud providers | |\n| **Pathfix** | API integration platform | API data | Pathfix, Inc. – United States | US-based SaaS infrastructure (defaults to US regions) | |\n| **WorkOS** | HRIS directory sync | Employee profile data (non-sensitive PII) | WorkOS, Inc. – United States (San Francisco, California) | US cloud infrastructure by default (EU options on some plans) | |\n| **Supabase** | Backend-as-a-service (database, auth, storage) | Application data, user data | Supabase, Inc. – United States | Region-based (supports US regions; configurable per project) | |\n\n## Third-Party Integrations\n\n1. **What are they?**\n\n Third-party application integrations are those that we use to make a Chezie user’s life easier. We create applications on platforms like Slack and Microsoft Teams and Chezie user’s leverage them to enhance their user experience.\n\n2. **What do you use them for?**\n\n The primary use for our third-party integrations are to:\n\n - Sync membership between teams channels and Chezie - [WorkOS](https://workos.com/security).\n\n - Push notifications for new events and group updates.\n\n - Track engagement within a Slack/Teams channel (if possible).\n\n - Allow users to push notifications to a Slack/Teams channel (if possible).\n\n Our use cases for our integrations will expand. There will be no blind scraping of user data but targeted ephemeral and in some instances stored data to reference associations between user’s, ERGs, events, and teams. The principal goal behind our third-party integrations is to boost user engagement by making Chezie functions accessible outside of the Chezie site.\n\n3. **How do you gain access to our data?**\n\n If you use Chezie’s third-party integration the installer of integration will give Chezie permission to access cursory user data that is then used to make the user’s experience with Chezie a lot more seamless. The data Chezie’s integration will access is limited, targeted and gained through secure APIs.\n\n This process is referred to as *OAuth 2.0 authorization code grant flow* and it is the industry standard for accessing APIs.\n\n## Slack Integration\n\nProvided are details on Chezie’s Slack Integration:\n\n**User role to install app**\n\nAccount admin(s)\n\n```plaintext\nPermissions\n\nOn behalf of users, Chezie can:\n\nView information about a user’s identity, granted by 1 team member (admin)\n\nOn behalf of the app, Chezie can:\n\nSend messages as @chezie\n\nView basic information about public channels in a workspace\n\nSend messages as @chezie with a customized username and avatar\n\nView messages and other content in public channels that Chezie has been added to\n\nView messages and other content in private channels that Chezie has been added to\n\nView messages and other content in direct messages that Chezie has been added to\n\nView messages and other content in group direct messages that Chezie has been added to\n\nView basic information about private channels that Chezie has been added to\n\nView people in a workspace\n\nView email addresses of people in a workspace\n```\n\n```plaintext\n💡 Scopes\n\nBot Token Scopes - Click on scope for a detailed overview of their access.\n\nChannels:history\n\nChannels:read\n\nChat:write\n\nChat:write.customize\n\nGroups:history\n\nGroups:read\n\nIm:history\n\nmpim:history\n\nUsers:read\n\nUsers:read.email\n```\n\n```plaintext\nUser Token Scopes\n\nidentity.basic\n```\n\n## Google Calendar Integration\n\nProvided are details on Chezie’s Google Integration:\n\n**User role to install app**\n\nAccount admin(s)\n\n```plaintext\nPermissions\n\nOn behalf of the app, Chezie can:\n\nView information about a user’s identity, granted by 1 team member (admin)\n\nOn behalf of the app, Chezie can:\n\nSee your primary Google Account email address\n\nSee your personal info, including any personal information you’ve made publicly available.\n\nView events on all your calendars\n\nAssociate you with your personal information on Google\n\nView calendar settings\n\nSee, edit, share, and permanently delete all calendars you can access using Google Calendar\n```\n\n```plaintext\nScopes\n\nClick on scope for a detailed overview of their access.\n\nuserinfo.email\n\nuserinfo.profile\n\nopenid\n\ncalendar\n```\n\n## Microsoft Chat Integration\n\nProvided are details on Chezie’s Microsoft Integration - Chat:\n\n**User role to install app**\n\nAccount admin(s)\n\n```plaintext\nPermissions\n\nOn behalf of users, Chezie can:\n\nSend channel messages in Microsoft Teams\n\nOn behalf of the app, Chezie can:\n\nView a user’s display name, given name, job title, office location, email, surname.\n\nRetrieve the properties and relationships of a profile object for a given user. Properties include user ID. Relationships include, accounts, anniversaries, interests, interests, positions. A full list of relationships can be viewed here.\n\nCreate groups and read all group properties and memberships on behalf of the signed-in user. Additionally allows group owners to manage their groups and allows group members to update group content.\n\nCreate groups and read all group properties and memberships on behalf of the signed-in user. Additionally allows group owners to manage their groups and allows group members to update group content.\n\nList groups, and to read their properties and all group memberships on behalf of the signed-in user. Also allows the app to read calendar, conversations, files, and other group content for all groups the signed-in user can access.\n```\n\n```plaintext\nScopes\n\nClick on scope for a detailed overview of their access.\n\nUser.Read\n\nGroup.Read.All\n\nGroup.ReadWrite.All\n\nChannelMessage.Send offline_access\n```\n\n## Microsoft Teams Integration - Video\n\nProvided are details on Chezie’s Microsoft Integration Video:\n\n**User role to install app**\n\nAccount admin(s)\n\n```plaintext\nPermissions\n\nOn behalf of the app, Chezie can:\n\nRetrieve the properties and relationships of a profile object for a given user. Properties include user ID. Relationships include, accounts, anniversaries, interests, interests, positions. A full list of relationships can be viewed here.\n\nView a user’s display name, given name, job title, office location, email, surname.\n\nDelete a profile object\n\nCreate a Microsoft event.\n\nMaintain access to data you have given it access to.\n\nAll of the aforementioned data.\n```\n\n```plaintext\nScopes\n\nClick on scope for a detailed overview of their access.\n\nprofile\n\nCalendars.ReadWrite\n\noffline_access\n\nUser.Read\n```\n\n## Outlook Calendar Integration\n\nProvided are details on Chezie’s Microsoft Integration - Outlook Calendar:\n\n**User role to install app**\n\nAccount admin(s)\n\n```plaintext\nPermissions\n\nOn behalf of users, Chezie can:\n\nHave full access to user calendars.\n\nUsed to create calendar events associated with Teams Event.\n\nCan readily view, read, update and delete calendar events.\n\nSpecify time zones in event creation.\n\nCreate a CalendarGroup\n\nGet the free/busy availability information for a collection of users, distributions lists, or resources, for a specified time period.\n\nFull list of functionality granted here.\n\nOn behalf of the app, Chezie can:\n\nAccess to calendar(s). Create, read, update, delete calendar events.\n\nView a user’s display name, given name, job title, office location, email, surname.\n\nSuggest meeting times and locations based on organizer and attendee availability and time or location constraints.\n\nRetrieve the properties and relationships of a profile object for a given user. Properties include user ID. Relationships include, accounts, anniversaries, interests, interests, positions. A full list of relationships can be viewed here.\n```\n\n```plaintext\nScopes\n\nClick on scope for a detailed overview of their access.\n\nprofile\n\nCalendars.ReadWrite\n```\n\n## Zoom Integration\n\nProvided are details on Chezie’s Zoom Integration:\n\n**User role to install app**\n\nAccount admin(s)\n\n```plaintext\nPermissions\n\nOn behalf of users, Chezie can:\n\nView Settings and preferences.\n\nView Profile and Contact Information.\n\nView and access to calendar of scheduled Zoom meetings and webinars.\n\nRegistration information relevant to a Zoom meetings - name, contact info., responses.\n\nContent generated in Zoom products may include invite details, poll data, meeting name.\n\nParticipant profile, name, display name, email, phone number, user ID, other information.\n\nOn behalf of the app, Chezie can:\n\nManage registration information, which may include scheduling Zoom experiences or adding or deleting registrants.\n\nManage participants, which may include assigning participants to specific breakout rooms and specifying an interpreter for the session.\n\nManage content and information generated in the context of Zoom experiences, which may include audio, video, messages, meeting or chat name, agenda, transcriptions, and responses to polls and Q&A.\n```\n\n```plaintext\nScopes\n\nClick on scope for a detailed overview of their access.\n\nmeeting:read:admin\n\nmeeting:write:admin\n\nuser:read:admin\n```\n\n## Password Policy\n\n```plaintext\nGeneral\n```\n\nGenerally our password policy dictates that we don’t use birthdays, anniversaries, or dates of noteworthiness that someone would be able to associate with employees through personal research. Long form passwords should be at least 12 characters in length and include symbols, numbers, upper and lower case letters.\n\nOur core team and stakeholders with access or exposure to sensitive information use password managers to handle password generation/storage for all Chezie related services.\n\nTechnical details of password generation and management are as follows:\n\n- Passwords are randomly generated and over 12 characters in length.\n\n- Master passwords should be at least 12 characters in length and include symbols, numbers, upper and lower case letters.\n\nAll Chezie employees are required to install and use Dashlane for secure password storage.\n\n```plaintext\nDevices\n```\n\n**Computers**\n\nPasswords should be at least 12 characters in length and include symbols, numbers, upper and lower case letters. Passwords should not reference birthday or anniversary information.\n\n**Mobile Devices**\n\nMobile devices should be protected by a password at least 6 characters in length and should not reference birthday or anniversary information. Screen should lock immediately or after a short time (no more than 5 minutes) of inactivity.\n\n```plaintext\nCloud\n```\n\nDigitalOcean\n\nDigitalOcean password is password manager generated and maintained. MFA is implemented for access into our DigitalOcean services.\n\n## Incident Management Program\n\n```plaintext\nGeneral\n```\n\nWe define an incident as anything that degrades a client’s user experience in such a way that they are not able to use our service. Our response is critical to ensuring our momentum moves forward and our users are able to use Chezie without any hindrances.\n\nThe use cases considered are mainly service outages but an incident can really be a number of things. We give team members the latitude to label something an incident but they must follow some guidelines:\n\n- Be consistent with incident labeling. Although we will not put a lid on incidents, not everything should be considered an incident.\n\n- Consider how different stakeholders will help with the incident and have everyone execute their identified function.\n\n- Team members are required to fill out a form of incident details.\n\n- There is a post mortem that the team should be part of. Discuss and examine why the incident happened and how it can be avoided in the future.\n\n\n\n

Stage	Incident Value	Chezie Value	Rationale
Detect	Chezie has identified an issue before it causes serious disruptions.	Focus on issue(s).	Our automated vulnerability tools should be able to alert us of incidents before stuff hits the fan.
Respond	Notify team members. Leverage skill sets.	Team work makes the dream work.	No fuss, we focus on taking care of the incident. Is it more work? Sure, now imagine we let it fester, now let’s get it done.
Recover	We can fix this, so let’s fix it!	We are fixing the issue for the customer! Let’s not turn them off.	Minimize impact on customers. Ensure we can get back online and everything is secure.
Learn	What happened? We win as a team and learn as a team.	So what actually happened? Don’t be bitter, be better.	Things happen. There is no such thing as a perfect system. Accountability and support will stimulate growth, pointing fingers will not.
Improve	Let’s not have this happen again.	We all have opportunities! Let’s enact those opportunities.	We’ve identified the underlying issues, now we must implement changes to ensure this bug is in the books.

\n\n```plaintext\nTools of the trade\n\nIssue tracking - Every issue will be tracked using Linear. The issue(s) will be transparent and tracked until resolution (completed).\n\nGoogle Meet - Real time communication and interfacing will help identify issues.\n\nNotion - We use Notion to detail incidents/issues and share postmortems.\n\nSlack/Teams/Email - Communicating status with customers will help keep everyone informed.\n```\n\n```plaintext\nIncident Manager\n```\n\nEvery incident will have an incident manager (IM). The incident manager is a role and they are empowered to take any action necessary to resolve the incident. The IM can call, message, and contact anyone in the company to ensure the resolution of the incident is swift. We define roles during an incident because incidents have range so we leverage whoever best fits certain roles to ensure efficient success.\n\n```plaintext\nIncident Table\n```\n\nFollowing is filled for every incident:\n\n\n\n

Summary	What’s the emergency?
Description	What’s the impact on customers? Include contact info so responders can interface.
Severity/Priority	Urgent or High means team members will be contacted immediately
Faulty Service	The service that has the fault that's causing the incident. Indicate “unknown” if you don’t know.
Affected Products	Which products/features/views/integrations are affected by the incident. Indicate any that apply

\n\nFill out Notion doc with above details ☝🏽\n\n```plaintext\nAssessing the incident\n```\n\nAfter we’ve established communication, it’s time to assess the incident.\n\nThings to consider:\n\n- What is the extent of business impact?\n\n- What is the customer experience like?\n\n- Who is affected?\n\n- When did the incident begin?\n\n- How many support cases have customers opened?\n\nAs we assess, we will record data in our Notion Incident Document to gather as much data as possible and so that visibility is company wide. Our Incident Document will be our single source of truth.\n\nBased on the business impact of the incident we will assign a severity level to it. We have 4 different levels of severity\n\n\n\n

Level	Description	Example
Urgent	A critical incident with very high impact.	-Customer data loss. -Chezie is down for all customers. -Privacy has been breached.
High	A major incident with significant impact.	-Some customers cannot access Chezie or one of its integrations. -Functionality is inconsistent or buggy.
Medium	A moderately visible incident with some measurable impact.	-Customers are reporting data inconsistencies in data visualizations and/or reporting. -Data sync issues, can be updated and resolved.
Low	A minor incident with low impact.	-Performance degradation -Minor inconvenience to customers.

\n\nEstablish the severity of the incident and report it to the team. An urgent incident is essentially all hands on deck immediately. Medium and low do not require as many resources but get bumped to the top of our TODO list.\n\n```plaintext\nRaise a new issue\n```\n\nCreate an issue in Linear that addresses all of the above. Assign issue to Incident Manager.\n\n```plaintext\nCommunication\n```\n\nIt’s clear the incident is real, you want to communicate internally and externally as soon as you can.\n\nInternal communication is to reduce confusion and optimize clarity in order to respond ASAP.\n\nThe goal of external communication is to let the customer know you know something is wrong and that you’re looking to fix the incident as soon as possible.\n\nCommunication is important for both your team members and customers, this kind of transparency breeds trust in all parties. After all, we follow best practices, and always have our customer's best interest in mind.\n\nWe will use Slack/Teams and email as our external/internal communication tools.\n\nWe will send follow ups at every stage of the incident management process until resolution is reached.\n\n```plaintext\nDelegation\n```\n\nThe IM will delegate roles that best fit team members.\n\nTeam members will be responsible and responsive, as long as the role is clear, they will be able to work quickly as part of the incident team.\n\nOur roles are:\n\n1. Incident Manager - Varies\n\n2. Tech Lead - Varies\n\n 1. Senior technical responder. Responsible for identifying what’s broken and why. Will also be responsible for implementing changes and running the tech team. Works in conjunction with IM.\n\n3. Communications Manager - Dumebi\n\n 1. A person familiar with public communications. Should be our company’s communications point of contact. Responsible for writing and sending communications to all stakeholders.\n\n```plaintext\nReview and Resolve\n```\n\n- We’ve figured out what the issue is. Time for resolution.\n\n - Watch for team fatigue.\n\n - Ensure team members are focusing on issues at hand and that resolution is imminent.\n\n - If it’s a long night, consider rotating roles. Who has been working the longest, time zones to be considered.\n\n - Make sure everyone feels like they are working toward a singular and shared goal, this is no time for segmentation in thought.\n\nWhen business impact has ended the incident is over.\n\nWe will fill out our Notion incident template with issues, post mortem notes. Points of interest.\n\n- Start of impact time\n\n- Detection time\n\n- Time to recover\n\nWe close out linear issues and go in depth into the post mortem in the next stand up meeting.\n\n## Privacy\n\n1. **Is there collection, access, processing, disclosure, or retention of any classification of personal information or personal data of individuals on behalf of the client?**\n\n Chezie will ask for targeted user data for the purpose of data aggregation and compilation of insights.\n\n2. **Is there a Third Party Risk Management Program (including ongoing monitoring) in place to address data protection safeguards (administrative, technical, and physical safeguards for the security of the client-scoped data?**\n\n [Please refer to Third Party Risk Management Policy](https://docs.google.com/document/d/16yFrnYdBQY9S9RYxv-I8U0ZdQ7MqMJwX8VeA3OuZwcs/edit#bookmark=id.o79orvakiptv)\n\n3. **Is there a documented policy or process to maintain accurate, complete, timely and relevant records of client-scoped data?**\n\n We maintain only data that is relevant.\n\n## All-Encompassing\n\n1. **Employee Onboarding**\n\n Employees are subject to background checks and confidentiality agreements.\n\n2. **Log Retention Policy**\n\n We have a log retention policy of 90 days. Within 90 days, all logs are readily available, and then after 90 days, logs are archived and retained for 6 years. After 6 years, all archives are destroyed.\n\n3. **What is client data used for?**\n\n Aggregation and Analysis. No marketing.\n\n## Appendix - Google Scope Details\n\n![](https://fb-usercontent.fra1.cdn.digitaloceanspaces.com/0195060e-200c-7ee8-a110-9eb0828c327e.png)\n\n![](https://fb-usercontent.fra1.cdn.digitaloceanspaces.com/0195060e-378c-77cc-a567-9f205b8a5334.png)\n\n![](https://fb-usercontent.fra1.cdn.digitaloceanspaces.com/0195060e-4c33-7fd9-8dbe-b6a351e66215.png)\n\n![](https://fb-usercontent.fra1.cdn.digitaloceanspaces.com/0195060e-6661-7c98-9128-2c7387d16650.png)\n\nFor more details regarding google scopes:\n\n","2026-04-16T19:06:35.794Z","2026-07-31T13:09:13.470Z","27be62db-f521-4ae8-a5b6-ed149ef7a113",[],[],[],"Admin permissions, explained","admin-permissions-explained-chezie-2","# Administrators Permissions\n\n### Get insights into the roles and capabilities of administrators in Chezie.\n\nIf you want to control what access different Admins have, you can do that by managing Admin permissions.\n\nThere are three different groups of Admin permissions:\n\n## **Managing groups**\n\n- **Create new Groups** - Admin can create new Groups\n\n- **View members** - Admin can view membership data for all Groups, including in-group vs. ally membership, and membership by department, office, and level.\n\n## **Managing Users**\n\n- **Add new Leads** - Admin can add new Leads for any Groups.\n\n- **Add new Admins** - Admin can give another user Admin permissions. Users with this permission can also edit permissions for other Admins.\n\n## **Events**\n\n- **Approve events** - Admin can Approve events that are in draft or pending status. Users with this permission will receive notifications whenever a Lead requests approval for an event.\n\n- **Create events** - Admin can create new events for any Group.\n\n- **Cancel events** - Admin can cancel an event as long as the event has not already passed.\n\n## Reporting\n\n- **View reports** - Admin can view reports in the Reporting tab.\n\n## Expenses\n\n- **Approve expenses** - Admin can approve expenses that are submitted.\n\n# Lead Permissions\n\n### Understand the roles and responsibilities of group leads in Chezie.\n\nIf you want to control what access your Group Leads have, you can do that by managing Lead permissions. Note that if someone is a Lead for multiple ERGs, they will have two sets of permissions.\n\n## **Managing groups**\n\n- **View members** - Lead can view membership data for the Group they lead, including in-group vs. ally membership, and membership by department, office, and level.\n\n- Customize Join Forms - Lead can customize the questions new members see when they join a group\n\n## **Managing Users**\n\n- **Add new Leads** - Lead can add new Leads for the Group they Lead.\n\n## **Events**\n\n- **Create events** - Lead can create new events for any Group.\n\n- **Cancel events** - Lead can cancel an event as long as the event has not already passed.\n\n- **Approve events** - Lead can approve an event that is in draft status. To do this, an Admin must [disable the event approval requirement](https://docs.chezie.co/docs/chezie-2026/events-3/723e8880-58d8-435f-aec1-a9768d7e8669).\n\n## Reporting\n\n- **View reports** - Lead can view reports in the Reporting tab.","2026-04-16T19:07:05.402Z","2026-08-27T19:51:35.114Z","382c326e-fcb3-4fdd-9dcf-5dac8aa9522f",[],[],[],"Adding & Managing Admins","1. Go to **Settings**\n\n ![1.png](/api/knowledge-base/images/f5c88185-8e89-42e2-9d43-dbe4ce020ee3)\n2. Click on **Admins**\n\n ![2.png](/api/knowledge-base/images/e5028756-5b54-4e0b-bce2-1a9fad47060a)\n3. Click on **Add new admin**\n\n ![3.png](/api/knowledge-base/images/b1e90e8c-9514-4db4-9e2d-bdcfccadb6c8)\n4. Type Employee name\n\n ![4.png](/api/knowledge-base/images/30bca00e-e4e3-41de-902d-ee7d6a72f92d)\n5. Select Employee name\n\n ![5.png](/api/knowledge-base/images/e9d4ec42-0fad-46de-9042-5aa692bd9aa0)\n6. Select applicable permissions\n\n ![6.png](/api/knowledge-base/images/d553a4f2-371a-49bb-a138-3c3726e12419)\n7. Click on **Invite**\n\n ![7.png](/api/knowledge-base/images/abb20c81-9cee-4119-9366-53869d0d6786)","2026-07-02T17:00:57.520Z","2026-07-02T17:04:58.742Z","5543fb2b-7582-4774-a901-6f640700f7fe",[],[],[],"2026 Platform Migration Hub","2026-platform-migration-hub","Everything you need to know about our upcoming Platform Migration","lightbulb","2026-04-16T14:52:41.918Z","2026-04-16T15:01:55.977Z","6ca5168a-b8b5-4175-8fe9-4ca238467e70",[1305,1306],[],{"_57":778,"_103":1316,"_112":-5,"_113":1317,"_115":1302,"_116":-5,"_117":1318,"_119":1319,"_22":1320,"_24":25,"_122":1321,"_124":-5,"_125":1322,"_127":1323},{"_57":1307,"_103":1308,"_112":-5,"_113":1309,"_115":1302,"_116":-5,"_117":1310,"_119":1311,"_22":1312,"_24":25,"_122":1313,"_124":-5,"_125":1314,"_127":1315},"Overview","overview","Chezie is upgrading to a new platform foundation this spring!\n\nOver the last few years, Chezie has grown quickly, and we’ve reached a point where we need to invest in a stronger foundation to meet our customers' demands. This upgrade gives us the ability to improve performance and reliability, ship new features faster, and support more types of internal communities over time, not just ERGs.\n\nThis is a full platform migration, but for most users, the experience should still feel familiar. The goal here is not to force everyone to learn a completely new tool. It’s to move Chezie onto infrastructure that is more stable, more scalable, and better suited for where the product is going.\n\n---\n\n# What’s new?\n\nHere’s a quick rundown of some of the improvements that are coming with this migration:\n\n## **1. Teams - Support for multiple types of communities**\n\n![Events - Invites Tab.png](https://firebasestorage.googleapis.com/v0/b/trnout-co.appspot.com/o/u-chezie-wg8g5%2Fknowledge-base%2F7eb34936-4ce2-4ca4-a3ed-1044605aeef9.png?alt=media)\n\nChezie will no longer be limited to ERGs alone (though we will 100% continue to support ERGs). You’ll be able to manage different types of internal communities (for example: ERGs, interest-based groups, location-based groups, or other programs) within a single platform, with clearer structure and permissions.\n\n## **2. Improved events and engagement workflows**\n\n![Events - Invites Tab.png](https://firebasestorage.googleapis.com/v0/b/trnout-co.appspot.com/o/u-chezie-wg8g5%2Fknowledge-base%2F44feb567-7898-43fe-afe5-221ff5cf0818.png?alt=media)\n\nWe’re making meaningful improvements to events, including better invite management, more flexible event setup (including hybrid events!), and improved visibility into participation and engagement.\n\n## **3. Faster performance and a more reliable foundation**\n\n![CleanShot 2026-04-13 at 13.34.31@2x.png](https://firebasestorage.googleapis.com/v0/b/trnout-co.appspot.com/o/u-chezie-wg8g5%2Fknowledge-base%2F9bac3d8d-37c5-4605-8179-f4db4c7e7789.png?alt=media)\n\nPages will load faster, exports will be more consistent, and the overall experience will feel smoother and more predictable. This foundation also allows us to move faster on reporting, approvals, and analytics going forward.\n\n# Migration Timeline\n\nWe’ve already started communicating about the platform upgrade and what customers can expect.\n\n![CleanShot 2026-04-08 at 14.01.11@2x.png](https://firebasestorage.googleapis.com/v0/b/trnout-co.appspot.com/o/u-chezie-wg8g5%2Fknowledge-base%2Fba7c2c5f-20da-4772-bb14-41a3cce75c8c.png?alt=media)\n\n> ***💡 Customers will be migrated in phases, and each organization will receive its own migration window in advance.***\n\n## March-April 2026 (Done ✅)\n\nWe began sharing early updates with customers and IT teams about the upcoming Chezie platform migration, including what’s changing at a high level and which integrations will need to be reconnected later in the process.\n\n## Early May 2026 (In Progress)\n\nWe expect to begin with a small beta group of customers. The purpose of this phase is to validate data migration, integration reconnection, core workflows, and overall platform reliability before broader rollout.\n\n## Mid-to-late May 2026\n\nWe expect to begin broader customer migrations in phases. Each customer will receive a specific migration window, along with more detailed instructions for admins and IT teams.\n\n## Late May / Early June 2026\n\nMost standard customer migrations are expected to be complete by this point, with any remaining edge cases or custom integrations handled separately.\n\nExact dates will be updated once our internal testing and beta testing commence. We’ll continue updating this page as the rollout plan becomes more concrete.\n\n---\n\n# What Admins and IT Teams Need to Do\n\nThe goal is to make this migration as predictable and low-effort as possible. There’s nothing most customers need to do right away, but there are a few things to be aware of.\n\n## For Company Admins / ERG Owners\n\nYou should:\n\n- Keep an eye out for your migration window and any customer-specific instructions\n- Make sure the right IT contact is looped in for setup work if your organization uses SSO or calendar/video integrations\n- Review any updates we share about sign-in links, timing, or known migration-day changes\n\nIf your organization uses custom integrations, we’ll reach out directly with more specific guidance.\n\n## For IT Teams\n\nMost customers will need IT involvement to reconnect the following in the new environment:\n\n- Single Sign-On (SSO), which will migrate to SAML\n- Calendar integration, either Google or Microsoft\n- Video meeting integration, such as Zoom or Webex if used (MS Teams and Google Meet are handled with the Calendar integrations, so they do not need to be re-connected separately)\n\n**Your HRIS integration does not need to be migrated** and requires no action as part of this transition.\n\nWe’re still finalizing a few migration steps through beta testing, so we’re intentionally holding off on publishing detailed integration setup guides until those flows are validated. Before your migration window, we’ll share the exact instructions your team needs.\n\n---\n\n# What Changes During Migration\n\nEach customer will be notified individually about their migration window. When your migration window arrives, there are a few practical changes to expect.\n\n## 1. Your sign-in URL will change\n\nCustomers will receive a new sign-in URL for the new Chezie environment\n\nEx: chezie.app/***company*** → [***company***.chezie.io](http://company.chezie.app)\n\n## 2. Group URLs will change\n\nLinks to specific groups in Chezie will also change as part of the migration.\n\nEx: chezie.app/***company/groupid*** → ***company***.chezie.io/***groupid***\n\n## 3. Some technical setup may happen during or around your migration window\n\nIf your organization uses SSO, calendar, or video integrations, your IT team may need to complete reconnection steps in the new environment before the migration is fully complete. We’ll share customer-specific instructions ahead of time.\n\n## 4. There will be a cutoff date for events\n\nWe are still finalizing a few migration details through internal and beta testing, but one known area we’re evaluating closely is how legacy events behave after migration. We’ll share customer-specific guidance in advance if any limitations apply to events created before your migration window.\n\nPlease note that each customer will receive a hard deadline to create events on the current Chezie platform. After that date, events will no longer be editable from within Chezie (but you can still edit them directly in your service account calendar, if need be).","2026-04-16T14:50:51.044Z","2026-06-10T14:47:01.970Z","a46adb27-f74b-4885-b67e-a39114dc95d7",[],[],[],"faqs","## Why is Chezie making this change?\n\nWe’ve outgrown the infrastructure Chezie was originally built on. This upgrade gives us a stronger foundation for performance, reliability, and future product development. It also helps us support more types of internal communities over time.\n\n## Will the platform look completely different?\n\nNo. The platform should still feel largely familiar. This is primarily a foundation upgrade, not a full reinvention of the user experience.\n\n## **Will there be downtime?**\n\nOur goal is to make the transition as seamless as possible by deactivating customer’s old platforms and activating new ones in sync. However, this will be confirmed during internal and beta testing. More details on timing and exact downtime will be shared as we perform this testing.\n\nAs of now, no downtime is anticipated, as this is a new application launch. The transition will happen simultaneously — the new app will be enabled and the old one disabled over the weekend. If testing reveals that any migration downtime becomes necessary, we will notify you in advance.\n\n## Will our data be migrated?\n\nYes. The migration includes customer data such as members, groups, event history, budgets, communications, and related records. Data validation is one of the main goals of our testing and rollout process.\n\n## Will we need to reconnect integrations?\n\nMost customers will need to reconnect SSO, calendar, and video meeting integrations in the new environment. HRIS integrations do not need to be migrated.\n\n## Does IT need to be involved?\n\n**Yes.** We’ll need to work with your IT team to reconnect integrations in the new environment and support any setup or validation steps during migration. Please have your IT partners connect directly with us during the migration window so we can coordinate with them in real time.\n\n## Does our HRIS integration need to be migrated?\n\nNo. HRIS integrations do not require action as part of this migration.\n\n## Will our login URL change?\n\nYes. Your sign-in URL will change as part of the migration, and group URLs will change as well.\n\n## How will we know when it’s our turn to migrate?\n\nWe’ll contact your team directly with your migration window and any required next steps before your migration begins.\n\n## Are the dates final?\n\nNot yet. We’re still finalizing details through internal testing and beta testing. This page will be updated as dates become more concrete, and each customer will receive direct communication ahead of their migration window.\n\n## What if our company uses a custom integration?\n\nWe’ll communicate directly with customers using custom integrations or edge-case setups, since those may require a slightly different migration path.\n\n## What support will be available during migration?\n\nWe’ll share customer-specific instructions ahead of your migration window, including what admins and IT teams need to do and who to contact with questions. We’re holding off on publishing detailed setup guides until those flows are validated through beta testing.\n\n## What attributes are required in the SAML assertion?\n\nOnly three attributes are needed: first name, last name, and email. These should match the configuration of your existing SAML application.\n\n## Will SSO be tested in both non-production and production environments?\n\nTesting will be conducted in the production environment. However, access to the new platform will be restricted to admins only until it is fully opened to the rest of the company.\n\n## Will we use the same SAML URLs\n\nTo access the new app, you will have to use the metadata and ACS URLs from this [documentation](https://docs.chezie.co/docs/integrations/saml-sso-chezie-2026-migration)\n\nThe default relay state will change to \\[companyname\\].chezie.io.\n\n## Which SAML attributes will Okta pass, and what values should they contain?\n\nThe attributes you are currently passing are sufficient and will be the same.\n\n## Will the SAML assertion and response be signed?\n\nYes, both assertion and response will be signed.","2026-04-16T14:53:35.937Z","2026-06-10T14:41:41.409Z","88b00c7f-2478-4b0f-b330-a04c7f8327c2",[],[],[],{"_57":409,"_103":-5,"_112":-5,"_113":410,"_115":328,"_116":62,"_117":411,"_119":412,"_22":413,"_24":25,"_10":1835,"_122":1836,"_124":-5,"_125":1837,"_127":1838},{"_57":1288,"_103":-5,"_112":-5,"_113":1289,"_115":1244,"_116":62,"_117":1290,"_119":1291,"_22":1292,"_24":25,"_10":1831,"_122":1832,"_124":-5,"_125":1833,"_127":1834},{"_57":137,"_103":-5,"_112":-5,"_113":138,"_115":106,"_116":62,"_117":139,"_119":140,"_22":141,"_24":25,"_10":1827,"_122":1828,"_124":-5,"_125":1829,"_127":1830},{"_57":219,"_103":220,"_112":-5,"_113":221,"_115":185,"_116":62,"_117":222,"_119":223,"_22":224,"_24":25,"_10":1823,"_122":1824,"_124":-5,"_125":1825,"_127":1826},{"_57":401,"_103":-5,"_112":-5,"_113":402,"_115":328,"_116":62,"_117":403,"_119":404,"_22":405,"_24":25,"_10":1819,"_122":1820,"_124":-5,"_125":1821,"_127":1822},{"_57":1279,"_103":1280,"_112":-5,"_113":1281,"_115":1244,"_116":62,"_117":1282,"_119":1283,"_22":1284,"_24":25,"_10":1815,"_122":1816,"_124":-5,"_125":1817,"_127":1818},{"_57":718,"_103":719,"_112":-5,"_113":720,"_115":675,"_116":62,"_117":721,"_119":722,"_22":723,"_24":25,"_10":1811,"_122":1812,"_124":-5,"_125":1813,"_127":1814},{"_57":129,"_103":-5,"_112":-5,"_113":130,"_115":106,"_116":62,"_117":131,"_119":132,"_22":133,"_24":25,"_10":1807,"_122":1808,"_124":-5,"_125":1809,"_127":1810},{"_57":887,"_103":888,"_112":-5,"_113":889,"_115":782,"_116":62,"_117":890,"_119":891,"_22":892,"_24":25,"_10":1803,"_122":1804,"_124":-5,"_125":1805,"_127":1806},{"_57":1159,"_103":-5,"_112":-5,"_113":1160,"_115":976,"_116":62,"_117":1161,"_119":1162,"_22":1163,"_24":25,"_10":1799,"_122":1800,"_124":-5,"_125":1801,"_127":1802},{"_57":625,"_103":626,"_112":-5,"_113":627,"_115":450,"_116":62,"_117":628,"_119":629,"_22":630,"_24":25,"_10":1795,"_122":1796,"_124":-5,"_125":1797,"_127":1798},{"_57":878,"_103":879,"_112":-5,"_113":880,"_115":782,"_116":62,"_117":881,"_119":882,"_22":883,"_24":25,"_10":1791,"_122":1792,"_124":-5,"_125":1793,"_127":1794},{"_57":869,"_103":870,"_112":-5,"_113":871,"_115":782,"_116":62,"_117":872,"_119":873,"_22":874,"_24":25,"_10":1787,"_122":1788,"_124":-5,"_125":1789,"_127":1790},{"_57":275,"_103":276,"_112":-5,"_113":277,"_115":251,"_116":62,"_117":278,"_119":279,"_22":280,"_24":25,"_10":1783,"_122":1784,"_124":-5,"_125":1785,"_127":1786},{"_57":1270,"_103":1271,"_112":-5,"_113":1272,"_115":1244,"_116":62,"_117":1273,"_119":1274,"_22":1275,"_24":25,"_10":1779,"_122":1780,"_124":-5,"_125":1781,"_127":1782},{"_57":963,"_103":964,"_112":-5,"_113":965,"_115":900,"_116":62,"_117":966,"_119":967,"_22":968,"_24":25,"_10":1775,"_122":1776,"_124":-5,"_125":1777,"_127":1778},{"_57":1150,"_103":1151,"_112":-5,"_113":1152,"_115":976,"_116":62,"_117":1153,"_119":1154,"_22":1155,"_24":25,"_10":1771,"_122":1772,"_124":-5,"_125":1773,"_127":1774},{"_57":1141,"_103":1142,"_112":-5,"_113":1143,"_115":976,"_116":62,"_117":1144,"_119":1145,"_22":1146,"_24":25,"_10":1767,"_122":1768,"_124":-5,"_125":1769,"_127":1770},{"_57":1230,"_103":-5,"_112":-5,"_113":1231,"_115":1208,"_116":62,"_117":1232,"_119":1233,"_22":1234,"_24":25,"_10":1763,"_122":1764,"_124":-5,"_125":1765,"_127":1766},{"_57":1195,"_103":1196,"_112":-5,"_113":1197,"_115":1171,"_116":62,"_117":1198,"_119":1199,"_22":1200,"_24":25,"_10":1759,"_122":1760,"_124":-5,"_125":1761,"_127":1762},{"_57":436,"_103":437,"_112":-5,"_113":438,"_115":101,"_116":62,"_117":439,"_119":439,"_22":440,"_24":25,"_10":1755,"_122":1756,"_124":-5,"_125":1757,"_127":1758},{"_57":616,"_103":617,"_112":-5,"_113":618,"_115":450,"_116":62,"_117":619,"_119":620,"_22":621,"_24":25,"_10":1751,"_122":1752,"_124":-5,"_125":1753,"_127":1754},{"_57":1133,"_103":-5,"_112":-5,"_113":1134,"_115":976,"_116":62,"_117":1135,"_119":1136,"_22":1137,"_24":25,"_10":1747,"_122":1748,"_124":-5,"_125":1749,"_127":1750},{"_57":607,"_103":608,"_112":-5,"_113":609,"_115":450,"_116":62,"_117":610,"_119":611,"_22":612,"_24":25,"_10":1743,"_122":1744,"_124":-5,"_125":1745,"_127":1746},{"_57":1222,"_103":-5,"_112":-5,"_113":1223,"_115":1208,"_116":62,"_117":1224,"_119":1225,"_22":1226,"_24":25,"_10":1739,"_122":1740,"_124":-5,"_125":1741,"_127":1742},{"_57":598,"_103":599,"_112":-5,"_113":600,"_115":450,"_116":62,"_117":601,"_119":602,"_22":603,"_24":25,"_10":1735,"_122":1736,"_124":-5,"_125":1737,"_127":1738},{"_57":1124,"_103":1125,"_112":-5,"_113":1126,"_115":976,"_116":62,"_117":1127,"_119":1128,"_22":1129,"_24":25,"_10":1731,"_122":1732,"_124":-5,"_125":1733,"_127":1734},{"_57":211,"_103":-5,"_112":-5,"_113":212,"_115":185,"_116":62,"_117":213,"_119":214,"_22":215,"_24":25,"_10":1727,"_122":1728,"_124":-5,"_125":1729,"_127":1730},{"_57":954,"_103":955,"_112":-5,"_113":956,"_115":900,"_116":62,"_117":957,"_119":958,"_22":959,"_24":25,"_10":1723,"_122":1724,"_124":-5,"_125":1725,"_127":1726},{"_57":111,"_103":-5,"_112":-5,"_113":114,"_115":106,"_116":62,"_117":118,"_119":120,"_22":121,"_24":25,"_10":1719,"_122":1720,"_124":-5,"_125":1721,"_127":1722},{"_57":392,"_103":393,"_112":-5,"_113":394,"_115":328,"_116":62,"_117":395,"_119":396,"_22":397,"_24":25,"_10":1715,"_122":1716,"_124":-5,"_125":1717,"_127":1718},{"_57":778,"_103":1316,"_112":-5,"_113":1317,"_115":1302,"_116":-5,"_117":1318,"_119":1319,"_22":1320,"_24":25,"_10":1711,"_122":1712,"_124":-5,"_125":1713,"_127":1714},{"_57":710,"_103":711,"_112":-5,"_113":712,"_115":675,"_116":62,"_117":713,"_119":713,"_22":714,"_24":25,"_10":1707,"_122":1708,"_124":-5,"_125":1709,"_127":1710},{"_57":589,"_103":590,"_112":-5,"_113":591,"_115":450,"_116":62,"_117":592,"_119":593,"_22":594,"_24":25,"_10":1703,"_122":1704,"_124":-5,"_125":1705,"_127":1706},{"_57":383,"_103":384,"_112":-5,"_113":385,"_115":328,"_116":62,"_117":386,"_119":387,"_22":388,"_24":25,"_10":1699,"_122":1700,"_124":-5,"_125":1701,"_127":1702},{"_57":580,"_103":581,"_112":-5,"_113":582,"_115":450,"_116":62,"_117":583,"_119":584,"_22":585,"_24":25,"_10":1695,"_122":1696,"_124":-5,"_125":1697,"_127":1698},{"_57":860,"_103":861,"_112":-5,"_113":862,"_115":782,"_116":62,"_117":863,"_119":864,"_22":865,"_24":25,"_10":1691,"_122":1692,"_124":-5,"_125":1693,"_127":1694},{"_57":1115,"_103":1116,"_112":-5,"_113":1117,"_115":976,"_116":62,"_117":1118,"_119":1119,"_22":1120,"_24":25,"_10":1687,"_122":1688,"_124":-5,"_125":1689,"_127":1690},{"_57":946,"_103":-5,"_112":-5,"_113":947,"_115":900,"_116":62,"_117":948,"_119":949,"_22":950,"_24":25,"_10":1683,"_122":1684,"_124":-5,"_125":1685,"_127":1686},{"_57":937,"_103":938,"_112":-5,"_113":939,"_115":900,"_116":62,"_117":940,"_119":941,"_22":942,"_24":25,"_10":1679,"_122":1680,"_124":-5,"_125":1681,"_127":1682},{"_57":571,"_103":572,"_112":-5,"_113":573,"_115":450,"_116":62,"_117":574,"_119":575,"_22":576,"_24":25,"_10":1675,"_122":1676,"_124":-5,"_125":1677,"_127":1678},{"_57":1106,"_103":1107,"_112":-5,"_113":1108,"_115":976,"_116":62,"_117":1109,"_119":1110,"_22":1111,"_24":25,"_10":1671,"_122":1672,"_124":-5,"_125":1673,"_127":1674},{"_57":661,"_103":662,"_112":-5,"_113":663,"_115":637,"_116":62,"_117":664,"_119":665,"_22":666,"_24":25,"_10":1667,"_122":1668,"_124":-5,"_125":1669,"_127":1670},{"_57":1186,"_103":1187,"_112":-5,"_113":1188,"_115":1171,"_116":62,"_117":1189,"_119":1190,"_22":1191,"_24":25,"_10":1663,"_122":1664,"_124":-5,"_125":1665,"_127":1666},{"_57":374,"_103":375,"_112":-5,"_113":376,"_115":328,"_116":62,"_117":377,"_119":378,"_22":379,"_24":25,"_10":1659,"_122":1660,"_124":-5,"_125":1661,"_127":1662},{"_57":652,"_103":653,"_112":-5,"_113":654,"_115":637,"_116":62,"_117":655,"_119":656,"_22":657,"_24":25,"_10":1655,"_122":1656,"_124":-5,"_125":1657,"_127":1658},{"_57":1097,"_103":1098,"_112":-5,"_113":1099,"_115":976,"_116":62,"_117":1100,"_119":1101,"_22":1102,"_24":25,"_10":1651,"_122":1652,"_124":-5,"_125":1653,"_127":1654},{"_57":1088,"_103":1089,"_112":-5,"_113":1090,"_115":976,"_116":62,"_117":1091,"_119":1092,"_22":1093,"_24":25,"_10":1647,"_122":1648,"_124":-5,"_125":1649,"_127":1650},{"_57":643,"_103":644,"_112":-5,"_113":645,"_115":637,"_116":62,"_117":646,"_119":647,"_22":648,"_24":25,"_10":1643,"_122":1644,"_124":-5,"_125":1645,"_127":1646},{"_57":928,"_103":929,"_112":-5,"_113":930,"_115":900,"_116":62,"_117":931,"_119":932,"_22":933,"_24":25,"_10":1639,"_122":1640,"_124":-5,"_125":1641,"_127":1642},{"_57":1177,"_103":1178,"_112":-5,"_113":1179,"_115":1171,"_116":62,"_117":1180,"_119":1181,"_22":1182,"_24":25,"_10":1635,"_122":1636,"_124":-5,"_125":1637,"_127":1638},{"_57":1079,"_103":1080,"_112":-5,"_113":1081,"_115":976,"_116":62,"_117":1082,"_119":1083,"_22":1084,"_24":25,"_10":1631,"_122":1632,"_124":-5,"_125":1633,"_127":1634},{"_57":1070,"_103":1071,"_112":-5,"_113":1072,"_115":976,"_116":62,"_117":1073,"_119":1074,"_22":1075,"_24":25,"_10":1627,"_122":1628,"_124":-5,"_125":1629,"_127":1630},{"_57":769,"_103":770,"_112":-5,"_113":771,"_115":731,"_116":62,"_117":772,"_119":773,"_22":774,"_24":25,"_10":1623,"_122":1624,"_124":-5,"_125":1625,"_127":1626},{"_57":1061,"_103":1062,"_112":-5,"_113":1063,"_115":976,"_116":62,"_117":1064,"_119":1065,"_22":1066,"_24":25,"_10":1619,"_122":1620,"_124":-5,"_125":1621,"_127":1622},{"_57":919,"_103":920,"_112":-5,"_113":921,"_115":900,"_116":62,"_117":922,"_119":923,"_22":924,"_24":25,"_10":1615,"_122":1616,"_124":-5,"_125":1617,"_127":1618},{"_57":428,"_103":-5,"_112":-5,"_113":429,"_115":101,"_116":62,"_117":430,"_119":431,"_22":432,"_24":25,"_10":1611,"_122":1612,"_124":-5,"_125":1613,"_127":1614},{"_57":266,"_103":267,"_112":-5,"_113":268,"_115":251,"_116":62,"_117":269,"_119":270,"_22":271,"_24":25,"_10":1607,"_122":1608,"_124":-5,"_125":1609,"_127":1610},{"_57":1052,"_103":1053,"_112":-5,"_113":1054,"_115":976,"_116":62,"_117":1055,"_119":1056,"_22":1057,"_24":25,"_10":1603,"_122":1604,"_124":-5,"_125":1605,"_127":1606},{"_57":1043,"_103":1044,"_112":-5,"_113":1045,"_115":976,"_116":62,"_117":1046,"_119":1047,"_22":1048,"_24":25,"_10":1599,"_122":1600,"_124":-5,"_125":1601,"_127":1602},{"_57":1034,"_103":1035,"_112":-5,"_113":1036,"_115":976,"_116":62,"_117":1037,"_119":1038,"_22":1039,"_24":25,"_10":1595,"_122":1596,"_124":-5,"_125":1597,"_127":1598},{"_57":701,"_103":702,"_112":-5,"_113":703,"_115":675,"_116":62,"_117":704,"_119":705,"_22":706,"_24":25,"_10":1591,"_122":1592,"_124":-5,"_125":1593,"_127":1594},{"_57":851,"_103":852,"_112":-5,"_113":853,"_115":782,"_116":62,"_117":854,"_119":855,"_22":856,"_24":25,"_10":1587,"_122":1588,"_124":-5,"_125":1589,"_127":1590},{"_57":562,"_103":563,"_112":-5,"_113":564,"_115":450,"_116":62,"_117":565,"_119":566,"_22":567,"_24":25,"_10":1583,"_122":1584,"_124":-5,"_125":1585,"_127":1586},{"_57":842,"_103":843,"_112":-5,"_113":844,"_115":782,"_116":62,"_117":845,"_119":846,"_22":847,"_24":25,"_10":1579,"_122":1580,"_124":-5,"_125":1581,"_127":1582},{"_57":833,"_103":834,"_112":-5,"_113":835,"_115":782,"_116":62,"_117":836,"_119":837,"_22":838,"_24":25,"_10":1575,"_122":1576,"_124":-5,"_125":1577,"_127":1578},{"_57":736,"_103":-5,"_112":-5,"_113":752,"_115":739,"_116":62,"_117":753,"_119":754,"_22":755,"_24":25,"_10":1571,"_122":1572,"_124":-5,"_125":1573,"_127":1574},{"_57":744,"_103":-5,"_112":-5,"_113":745,"_115":739,"_116":62,"_117":746,"_119":747,"_22":748,"_24":25,"_10":1567,"_122":1568,"_124":-5,"_125":1569,"_127":1570},{"_57":257,"_103":258,"_112":-5,"_113":259,"_115":251,"_116":62,"_117":260,"_119":261,"_22":262,"_24":25,"_10":1563,"_122":1564,"_124":-5,"_125":1565,"_127":1566},{"_57":420,"_103":-5,"_112":-5,"_113":421,"_115":101,"_116":62,"_117":422,"_119":423,"_22":424,"_24":25,"_10":1559,"_122":1560,"_124":-5,"_125":1561,"_127":1562},{"_57":366,"_103":-5,"_112":-5,"_113":367,"_115":328,"_116":62,"_117":368,"_119":369,"_22":370,"_24":25,"_10":1555,"_122":1556,"_124":-5,"_125":1557,"_127":1558},{"_57":294,"_103":295,"_112":-5,"_113":296,"_115":289,"_116":62,"_117":297,"_119":298,"_22":299,"_24":25,"_10":1551,"_122":1552,"_124":-5,"_125":1553,"_127":1554},{"_57":553,"_103":554,"_112":-5,"_113":555,"_115":450,"_116":62,"_117":556,"_119":557,"_22":558,"_24":25,"_10":1547,"_122":1548,"_124":-5,"_125":1549,"_127":1550},{"_57":544,"_103":545,"_112":-5,"_113":546,"_115":450,"_116":62,"_117":547,"_119":548,"_22":549,"_24":25,"_10":1543,"_122":1544,"_124":-5,"_125":1545,"_127":1546},{"_57":535,"_103":536,"_112":-5,"_113":537,"_115":450,"_116":62,"_117":538,"_119":539,"_22":540,"_24":25,"_10":1539,"_122":1540,"_124":-5,"_125":1541,"_127":1542},{"_57":1261,"_103":1262,"_112":-5,"_113":1263,"_115":1244,"_116":62,"_117":1264,"_119":1265,"_22":1266,"_24":25,"_10":1535,"_122":1536,"_124":-5,"_125":1537,"_127":1538},{"_57":526,"_103":527,"_112":-5,"_113":528,"_115":450,"_116":62,"_117":529,"_119":530,"_22":531,"_24":25,"_10":1531,"_122":1532,"_124":-5,"_125":1533,"_127":1534},{"_57":1307,"_103":1308,"_112":-5,"_113":1309,"_115":1302,"_116":-5,"_117":1310,"_119":1311,"_22":1312,"_24":25,"_10":1527,"_122":1528,"_124":-5,"_125":1529,"_127":1530},{"_57":517,"_103":518,"_112":-5,"_113":519,"_115":450,"_116":62,"_117":520,"_119":521,"_22":522,"_24":25,"_10":1523,"_122":1524,"_124":-5,"_125":1525,"_127":1526},{"_57":1252,"_103":1253,"_112":-5,"_113":1254,"_115":1244,"_116":62,"_117":1255,"_119":1256,"_22":1257,"_24":25,"_10":1519,"_122":1520,"_124":-5,"_125":1521,"_127":1522},{"_57":357,"_103":358,"_112":-5,"_113":359,"_115":328,"_116":62,"_117":360,"_119":361,"_22":362,"_24":25,"_10":1515,"_122":1516,"_124":-5,"_125":1517,"_127":1518},{"_57":1026,"_103":-5,"_112":-5,"_113":1027,"_115":976,"_116":62,"_117":1028,"_119":1029,"_22":1030,"_24":25,"_10":1511,"_122":1512,"_124":-5,"_125":1513,"_127":1514},{"_57":202,"_103":203,"_112":-5,"_113":204,"_115":185,"_116":62,"_117":205,"_119":206,"_22":207,"_24":25,"_10":1507,"_122":1508,"_124":-5,"_125":1509,"_127":1510},{"_57":508,"_103":509,"_112":-5,"_113":510,"_115":450,"_116":62,"_117":511,"_119":512,"_22":513,"_24":25,"_10":1503,"_122":1504,"_124":-5,"_125":1505,"_127":1506},{"_57":1214,"_103":-5,"_112":-5,"_113":1215,"_115":1208,"_116":62,"_117":1216,"_119":1217,"_22":1218,"_24":25,"_10":1499,"_122":1500,"_124":-5,"_125":1501,"_127":1502},{"_57":499,"_103":500,"_112":-5,"_113":501,"_115":450,"_116":62,"_117":502,"_119":503,"_22":504,"_24":25,"_10":1495,"_122":1496,"_124":-5,"_125":1497,"_127":1498},{"_57":911,"_103":-5,"_112":-5,"_113":912,"_115":900,"_116":62,"_117":913,"_119":914,"_22":915,"_24":25,"_10":1491,"_122":1492,"_124":-5,"_125":1493,"_127":1494},{"_57":1017,"_103":1018,"_112":-5,"_113":1019,"_115":976,"_116":62,"_117":1020,"_119":1021,"_22":1022,"_24":25,"_10":1487,"_122":1488,"_124":-5,"_125":1489,"_127":1490},{"_57":1008,"_103":1009,"_112":-5,"_113":1010,"_115":976,"_116":62,"_117":1011,"_119":1012,"_22":1013,"_24":25,"_10":1483,"_122":1484,"_124":-5,"_125":1485,"_127":1486},{"_57":999,"_103":1000,"_112":-5,"_113":1001,"_115":976,"_116":62,"_117":1002,"_119":1003,"_22":1004,"_24":25,"_10":1479,"_122":1480,"_124":-5,"_125":1481,"_127":1482},{"_57":349,"_103":-5,"_112":-5,"_113":350,"_115":328,"_116":62,"_117":351,"_119":352,"_22":353,"_24":25,"_10":1475,"_122":1476,"_124":-5,"_125":1477,"_127":1478},{"_57":341,"_103":-5,"_112":-5,"_113":342,"_115":328,"_116":62,"_117":343,"_119":344,"_22":345,"_24":25,"_10":1471,"_122":1472,"_124":-5,"_125":1473,"_127":1474},{"_57":761,"_103":-5,"_112":-5,"_113":762,"_115":731,"_116":62,"_117":763,"_119":764,"_22":765,"_24":25,"_10":1467,"_122":1468,"_124":-5,"_125":1469,"_127":1470},{"_57":692,"_103":693,"_112":-5,"_113":694,"_115":675,"_116":62,"_117":695,"_119":696,"_22":697,"_24":25,"_10":1463,"_122":1464,"_124":-5,"_125":1465,"_127":1466},{"_57":490,"_103":491,"_112":-5,"_113":492,"_115":450,"_116":62,"_117":493,"_119":494,"_22":495,"_24":25,"_10":1459,"_122":1460,"_124":-5,"_125":1461,"_127":1462},{"_57":194,"_103":194,"_112":-5,"_113":195,"_115":185,"_116":62,"_117":196,"_119":197,"_22":198,"_24":25,"_10":1455,"_122":1456,"_124":-5,"_125":1457,"_127":1458},{"_57":824,"_103":825,"_112":-5,"_113":826,"_115":782,"_116":62,"_117":827,"_119":828,"_22":829,"_24":25,"_10":1451,"_122":1452,"_124":-5,"_125":1453,"_127":1454},{"_57":684,"_103":685,"_112":-5,"_113":686,"_115":675,"_116":62,"_117":687,"_119":687,"_22":688,"_24":25,"_10":1447,"_122":1448,"_124":-5,"_125":1449,"_127":1450},{"_57":815,"_103":816,"_112":-5,"_113":817,"_115":782,"_116":62,"_117":818,"_119":819,"_22":820,"_24":25,"_10":1443,"_122":1444,"_124":-5,"_125":1445,"_127":1446},{"_57":806,"_103":807,"_112":-5,"_113":808,"_115":782,"_116":62,"_117":809,"_119":810,"_22":811,"_24":25,"_10":1439,"_122":1440,"_124":-5,"_125":1441,"_127":1442},{"_57":797,"_103":798,"_112":-5,"_113":799,"_115":782,"_116":62,"_117":800,"_119":801,"_22":802,"_24":25,"_10":1435,"_122":1436,"_124":-5,"_125":1437,"_127":1438},{"_57":481,"_103":482,"_112":-5,"_113":483,"_115":450,"_116":62,"_117":484,"_119":485,"_22":486,"_24":25,"_10":1431,"_122":1432,"_124":-5,"_125":1433,"_127":1434},{"_57":472,"_103":473,"_112":-5,"_113":474,"_115":450,"_116":62,"_117":475,"_119":476,"_22":477,"_24":25,"_10":1427,"_122":1428,"_124":-5,"_125":1429,"_127":1430},{"_22":450,"_65":444},[],[],[],{"_22":450,"_65":444},[],[],[],{"_22":782,"_65":778},[],[],[],{"_22":782,"_65":778},[],[],[],{"_22":782,"_65":778},[],[],[],{"_22":675,"_65":670},[],[],[],{"_22":782,"_65":778},[],[],[],{"_22":185,"_65":180},[],[],[],{"_22":450,"_65":444},[],[],[],{"_22":675,"_65":670},[],[],[],{"_22":731,"_65":727},[],[],[],{"_22":328,"_65":323},[],[],[],{"_22":328,"_65":323},[],[],[],{"_22":976,"_65":972},[],[],[],{"_22":976,"_65":972},[],[],[],{"_22":976,"_65":972},[],[],[],{"_22":900,"_65":896},[],[],[],{"_22":450,"_65":444},[],[],[],{"_22":1208,"_65":1204},[],[],[],{"_22":450,"_65":444},[],[],[],{"_22":185,"_65":180},[],[],[],{"_22":976,"_65":972},[],[],[],{"_22":328,"_65":323},[],[],[],{"_22":1244,"_65":1238},[],[],[],{"_22":450,"_65":444},[],[],[],{"_22":1302,"_65":1296},[],[],[],{"_22":450,"_65":444},[],[],[],{"_22":1244,"_65":1238},[],[],[],{"_22":450,"_65":444},[],[],[],{"_22":450,"_65":444},[],[],[],{"_22":450,"_65":444},[],[],[],{"_22":289,"_65":284},[],[],[],{"_22":328,"_65":323},[],[],[],{"_22":101,"_65":102},[],[],[],{"_22":251,"_65":248},[],[],[],{"_22":739,"_65":736},[],[],[],{"_22":739,"_65":736},[],[],[],{"_22":782,"_65":778},[],[],[],{"_22":782,"_65":778},[],[],[],{"_22":450,"_65":444},[],[],[],{"_22":782,"_65":778},[],[],[],{"_22":675,"_65":670},[],[],[],{"_22":976,"_65":972},[],[],[],{"_22":976,"_65":972},[],[],[],{"_22":976,"_65":972},[],[],[],{"_22":251,"_65":248},[],[],[],{"_22":101,"_65":102},[],[],[],{"_22":900,"_65":896},[],[],[],{"_22":976,"_65":972},[],[],[],{"_22":731,"_65":727},[],[],[],{"_22":976,"_65":972},[],[],[],{"_22":976,"_65":972},[],[],[],{"_22":1171,"_65":1167},[],[],[],{"_22":900,"_65":896},[],[],[],{"_22":637,"_65":634},[],[],[],{"_22":976,"_65":972},[],[],[],{"_22":976,"_65":972},[],[],[],{"_22":637,"_65":634},[],[],[],{"_22":328,"_65":323},[],[],[],{"_22":1171,"_65":1167},[],[],[],{"_22":637,"_65":634},[],[],[],{"_22":976,"_65":972},[],[],[],{"_22":450,"_65":444},[],[],[],{"_22":900,"_65":896},[],[],[],{"_22":900,"_65":896},[],[],[],{"_22":976,"_65":972},[],[],[],{"_22":782,"_65":778},[],[],[],{"_22":450,"_65":444},[],[],[],{"_22":328,"_65":323},[],[],[],{"_22":450,"_65":444},[],[],[],{"_22":675,"_65":670},[],[],[],{"_22":1302,"_65":1296},[],[],[],{"_22":328,"_65":323},[],[],[],{"_22":106,"_65":107},[],[],[],{"_22":900,"_65":896},[],[],[],{"_22":185,"_65":180},[],[],[],{"_22":976,"_65":972},[],[],[],{"_22":450,"_65":444},[],[],[],{"_22":1208,"_65":1204},[],[],[],{"_22":450,"_65":444},[],[],[],{"_22":976,"_65":972},[],[],[],{"_22":450,"_65":444},[],[],[],{"_22":101,"_65":102},[],[],[],{"_22":1171,"_65":1167},[],[],[],{"_22":1208,"_65":1204},[],[],[],{"_22":976,"_65":972},[],[],[],{"_22":976,"_65":972},[],[],[],{"_22":900,"_65":896},[],[],[],{"_22":1244,"_65":1238},[],[],[],{"_22":251,"_65":248},[],[],[],{"_22":782,"_65":778},[],[],[],{"_22":782,"_65":778},[],[],[],{"_22":450,"_65":444},[],[],[],{"_22":976,"_65":972},[],[],[],{"_22":782,"_65":778},[],[],[],{"_22":106,"_65":107},[],[],[],{"_22":675,"_65":670},[],[],[],{"_22":1244,"_65":1238},[],[],[],{"_22":328,"_65":323},[],[],[],{"_22":185,"_65":180},[],[],[],{"_22":106,"_65":107},[],[],[],{"_22":1244,"_65":1238},[],[],[],{"_22":328,"_65":323},[],[],[],{"_65":1850,"_1842":1851,"_1843":-5,"_59":1852,"_1844":1847,"_117":1853,"_119":1854,"_22":64,"_24":25},{"_65":66,"_1842":66,"_1843":-5,"_59":-5,"_1844":1847,"_117":1848,"_119":1849,"_22":62,"_24":25},{"_65":180,"_1842":-5,"_1843":-5,"_59":-5,"_1844":-5,"_117":1845,"_119":1846,"_22":63,"_24":25},"supportName","supportLogo","defaultTriageChannelId","2026-07-31T14:34:32.898Z","2026-07-31T14:34:50.778Z","C0BDF0TSEKS","2024-11-05T00:57:58.627Z","2026-07-21T06:18:30.110Z","Chezie - 2026","Chezie Support","External support for customer inquiries and issues","2026-06-22T14:39:06.365Z","2026-06-23T16:11:28.007Z","user",{"_1858":1859,"_1857":27},"anonymous","uid","anon_1790071704225_x2o8uls","apiKey","AIzaSyDCG_xdkCxQ0mNJT1LKg2XIf0cHJwSISYU","authDomain","unthread"]

Managing Members

Add/remove members

Approve private join requests

Export member list