You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Add vault_id column to team_permissions and user_permissions tables
- Teams and users can have different permission levels per vault
- Update get_user_permissions and user_has_permission functions for vault scoping
- Add vault selector UI to PermissionsEditor and UserPermissionsDialog
- Schema version bumped to v20
Copy file name to clipboardExpand all lines: CHANGELOG.md
+11Lines changed: 11 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,17 @@
2
2
3
3
All notable changes to BluePLM will be documented in this file.
4
4
5
+
## [2.20.0] - 2025-12-31
6
+
7
+
### Added
8
+
-**Per-vault permissions**: Teams and individual users can now have different permission levels per vault. Set "All Vaults (Global)" for org-wide permissions, or select a specific vault for vault-scoped permissions. Example: Engineering team can have admin on Production vault but view-only on Archive vault
9
+
10
+
### Changed
11
+
-**Schema version**: Bumped to v20
12
+
-**Permission functions**: `get_user_permissions` and `user_has_permission` now accept optional `vault_id` parameter for vault-scoped checks
0 commit comments