Viva Glint will manage report attribute access solely at the user-role level, removing client-level restrictions to ensure consistent permissions. This change rolls out globally in November 2026. Organizations should review and update user-role permissions to maintain intended access, with no compliance issues identified.
Viva Glint is simplifying report attribute access management by making user-role permissions the single source of truth for report attribute access.
Previously, some migrated customers may have had client-level attribute restrictions configured by their Customer Experience Program Managers (CxPMs). These client-level restrictions could override the permissions configured in the Glint UI, creating inconsistencies between the permissions administrators configured and the access users actually received.
As part of this change, client-level restrictions for report breakdowns, report filters, and comment filters will be removed. Attribute access will be governed by the permissions configured on the User roles > Report attributes page in Viva Glint.
Rollout Schedule
Global: We will begin rolling out on mid November 2026 and expect to complete by late November 2026.
Impact on Your Organization
After this change, client-level restrictions configured will no longer be supported for the in-scope attribute permissions. The permissions configured for each user role in the Glint platform will determine which report attributes users can access.
For customers who previously relied on client-level restrictions, this may change the report attributes available to users if their existing user-role permissions do not reflect the intended access.
Action Required/Recommendations
- Review the report attribute permissions configured for your user roles in Viva Glint before this change takes effect.
- Confirm that each role grants access only to the report attributes its assigned users should be able to access. Update role-level permissions as needed to ensure that access aligns with your organization’s requirements.
Compliance considerations
No compliance considerations identified. Review as appropriate for your organization.