You can now decide whether scoped admins are allowed to edit user attributes within their assigned scope.
screenzy-1774264199122
What’s new?
We’ve introduced a new permission setting in the Role Selection modal:
  • “User can edit user attributes” toggle (true / false)
  • Control whether scoped admins can update user attributes for users within their scope
The permission is now clearly displayed as:
“Can edit user attributes” with a dynamic true/false indicator
Why this matters
Previously, scoped admins could not edit user attributes at all — even for users within their own scope.
This created bottlenecks where global admins had to step in for simple updates like:
  • Updating hire dates
  • Correcting user attributes
  • Maintaining data accuracy across teams
What this enables
With this new setting, you can:
  • Delegate attribute management to local or regional admins
  • Reduce dependency on global admins for routine updates
  • Keep user data accurate and up to date within each scope
Real-world example
If your HR or regional teams need to manage attributes like employee hire date, you can now grant them access—without expanding their permissions beyond their scope.