Why does AttendList need these Google permissions?
An explanation of each Google permission (OAuth scope) that AttendList requests and why it's needed.
When you connect AttendList to Google, you'll be asked to grant a set of permissions. Here's exactly what each one is for:
Email & profile info — Powers the "Sign in with Google" flow — gives AttendList your name, email, and profile photo for your account.
Google Meet — The core permission. Lets AttendList fetch participant data (join/leave times) from your meetings.
Google Contacts — Used to look up participant emails and names after a meeting. Google only allows email lookups if the participant is in your contacts, "other" contacts, or the same Workspace directory — so all three scopes are needed to identify participants as reliably as possible.
Google Calendar — Links meetings to their calendar events, enriching reports with the meeting title, expected attendees, and RSVP statuses.
Google Drive — If enabled, AttendList exports attendance reports to a Drive folder you choose (powering the Google Sheets integration).
AttendList requests only the permissions it needs, and uses them only to power the features described above. If you have any questions, feel free to message us.