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.
For Group/Chapter Admins
The calendar invite shows the wrong name
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.
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.
What you can do:
- 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.
- 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.
Who owns it: Your IT team.
I can't get the attendance report, or attendance is missing
What you'll see: No attendance data for an event, or you can't open the Attendance tab.
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.
What you can do:
- Always create events using the connected integration rather than pasting a personal Zoom/Teams link.
- 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.
Who owns it: Shared — use the integration to keep it automatic; otherwise the meeting host owns the data.
Where's the meeting recording?
What you'll see: You're looking for a recording of an ERG event and expect to find it in Chezie.
Why: Chezie schedules and tracks meetings, but it doesn't record them and doesn't store recordings.
What you can do:
- Recordings live in your video platform. Contact your service account admin for access.
- If a Host Key was used to start the meeting, Zoom typically sends the recording link directly to whoever hosted.
Who owns it: Your video platform (Zoom/Teams/Webex) and its admin.
Some members didn't get the email, or it went to spam
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.
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.
What you can do:
- Ask recipients to check spam/junk and to add your sending address to their safe senders.
- For company-wide delivery issues, your IT team can allowlist Chezie's sending domain.
- 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.
Who owns it: The recipient's email system / your IT team.
Why is my big event email taking so long to arrive?
What you'll see: For large groups, some members get the email right away and others get it noticeably later.
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.
Who owns it: This is expected Chezie behavior, by design.
Add to Calendar isn't working in Outlook
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.
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.
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.
Who owns it: The recipient's calendar application.
For IT Admins
The service account, and why reconnection sometimes matters
What you'll see: Invites suddenly stop sending, attendance stops being captured, or an integration shows as "disconnected."
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.
What you can do:
- 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.)
- If the service account uses SSO, make sure whoever reconnects can actually sign in as it.
Who owns it: Your IT team.
Microsoft permission scopes and automatic attendance
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.
Why: Those scopes power automatic attendance capture (Microsoft's change-notifications for meetings aren't available with narrower delegated permissions today).
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.
Who owns it: Your IT/security team.
HRIS attributes (department, location, level) aren't showing
What you'll see: Member records or report filters are missing HRIS attributes like department or location.
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.
What you can do:
- Confirm your IdP/HRIS is configured to pass the attributes you want into Chezie to WorkOS.
- 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.
Who owns it: Your IT/HRIS configuration.
Login problems and wrong-identity sign-ins
What you'll see: A member logs in and sees no group memberships, or gets an SSO error.
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.
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.
Who owns it: Your identity provider (SSO). Related: SAML SSO.
Changes made directly on the connected calendar
What you'll see: An event that's still approved and active in Chezie is missing from attendees' calendars.
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.
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.
Who owns it: Your calendar system / whoever has access to the service account.
The short version
| You expected to control in Chezie… | It's actually controlled by… |
|---|---|
| Invite sender / organizer name | Your service account (IT) |
| Meeting recordings & host keys | Your video platform + its admin |
| Automatic attendance | The connected integration (personal links break it) |
| Whether an email reaches the inbox | The recipient's mail system |
| HRIS attributes in member data | Your IdP/HRIS configuration |
| Who a member is logged in as | Your SSO / identity provider |
If 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.