Preset Feature Feedback
What is the problem or goal you're trying to solve or accomplish?
The customer needs to grant a group of 100+ users access to a specific set of dashboards and datasets. They already maintain that audience as a Google Group. Because Preset doesn't consume group membership from Google, they must rebuild and hand-maintain the same list inside Preset — as workspace members and as Data Access Role members — for every audience they manage. At 100+ users this is unsustainable and creates a security gap: someone removed from the Google Group keeps Preset access until an admin notices. Customers on Okta solve this with SCIM group push; Google-Workspace-only customers have no equivalent.
How are you solving it currently?
Manually. Membership is maintained by hand in Preset and kept in sync with the Google Group through periodic review. The alternative is a customer-owned script against Google's Directory API plus the Preset API, which requires engineering capacity most customers don't have for an access-control task.
What is your recommended solution?
Read the group membership attribute Google already sends in the SAML response, and let admins map a group name to a Team Role, Workspace Role, and Data Access Role in Manager. Google has supported group membership in outbound SAML responses since May 2022, so no work is required on the customer's side beyond adding the groups in their attribute mapping. Known limitation to set expectations: SAML-based mapping applies at login, so revocation is not immediate — a Directory API sync would be needed for parity with the current Okta SCIM behavior.
