Improvements to Dataset Level Permissions
We’ve made dataset-level permissions clearer and easier to understand.
When we introduced dataset-level permissions, we heard from many of you that the new permissions experience was confusing—especially in Build apps. We listened to that feedback and made several updates to make permissions clearer and more consistent.
Here’s what’s improved:
- A simpler Build apps permissions view. Since datasets don’t apply to Build apps, separating app and dataset permissions created unnecessary confusion. Permissions now appear together in a single matrix, making it easier to see and manage access for an app.
- Clearer permission names. Design and Publish this app is now Configure this app, and Administer this dataset is now Administer documents.
- More descriptive permission statuses. Updated labels make it clearer whether someone has a permission, doesn’t have it, or whether the permission isn’t available.
- Clearer permission indicators. Updated labels and hover text help explain where permissions come from and what happens when you change them.
- Helpful guidance. Help text provides additional context about permissions when you need it.
These updates don’t change what dataset-level permissions are designed to do. You can still give people access to the specific content they manage without giving them broader administrative access. We hope these changes make that functionality clearer, and we apologize that our initial rollout didn’t make the permissions experience as clear as it should have been.
One of the main benefits we want to highlight with the new dataset-level permissions is the separation of Configure this app and Administer documents. This gives you more flexibility to let groups like a Sponsored Programs Office or Registrar’s Office administer documents without also giving them access to change the form or app configuration.