Calendar Connection permission shouldn't require Phone/Numbers access
K
Katherine Jones
Previously, we could grant a sub-account user permission to access and connect their own Calendar without exposing anything else. They'd see the Calendar tab, connect their personal calendar (Google/Outlook), and that was it.
At some point this changed. Now, in order for a user to connect their own calendar, we have to grant broader permissions that also expose Phone/Numbers settings for the entire sub-account including phone numbers, call settings, and configuration that has nothing to do with calendar connection.
This is a security and privacy issue for us. We have partner agents and team members who need to connect their own calendar for scheduling, but they have no business reason to see or access our sub-account's phone numbers, call routing, or telephony settings. Bundling these permissions together forces us to either:
Over-expose sensitive account settings to users who only need calendar access, or
Withhold calendar connection entirely to protect phone/number settings
Please decouple "Calendar Connection" permission from "Phone/Numbers" visibility. Restore the ability to grant a user access to connect their own calendar in isolation, without bundling in phone number/telephony visibility for the sub-account.
This is a basic least-privilege access control issue and should be treated as a permissions bug, not just a feature request.
Log In