We have modernized the legacy System Settings page for better user clarity, accessibility, and experience. This includes splitting out tenant-wide configurations from product licensing information.
Problem
The System Settings page currently uses an older UX framework that doesn’t meet our accessibility standards. Its information architecture also made it harder to distinguish between tenant-wide configurations (which are configurable by org admins) and licensed products (which aren’t configurable in-app).
Solution
The tenant-wide behavior System Settings (Admin → System Settings) has been visually refreshed and given a clearer user experience. This includes updating to our modern design framework, which means improved responsiveness and accessibility. The functionality on these pages has not changed.
Additionally, we have broken out the prior System Features page into two pages:
Feature Settings: Tenant-wide behavior configurations controllable by Org Administrators
Product Licenses:
Who is affected?
This affects all customers in all regions.
Action Required:
There is no action required.
Important Dates
We have rolled this change back due to a minor issue. New dates will be posted below when this release is scheduled.
Sandbox Rollout : Week of September 22, 2025 Production Rollout : Week of October 6, 2025
Calendar
By RSVP’ing to this event you will be reminded of this release prior.
Looks good on first glance! Looking forward to check it out in sandbox next week.
Based on your screenshot of product licenses. How do these active and inactive licenses correspond to the values found with the API GET /v2025/tenant? It seems many licenses are missing in your UI screenshot, and I don’t see how we can map them to each other. The UI does not seem to mention the IDs and the API does not seem to mention the display name.
In addition, wouldn’t it make sense to have the UI specify which licenses are grouped as Business, which ones as Business+ or something like that? Such that you can easily see in this UI why you have certain licenses and why you don’t have others?
Great question - the licenses section of the tenant API is certainly imperfect (as is that API). This UI does it’s best to feed from both the tenant API, as well as some backend services that control SKU licensing. Where there was imperfection, we deferred more in the direction of matching the SKUs that are licensable, since this is much more accessible to the average admin. This should continue to evolve over time, but this was laying the foundation of splitting out the old “Features” page which included both licenses and tenant-wide configurations.
Hi all - There’s a minor issue with this change and out of an abundance of caution we’ve rolled this back. We’ll slow-roll back out to Sandbox and Prod and update the dates later. It will follow the normal release process when we do so.
By RSVP’ing to this event you will be reminded of this release prior.
