Tree: 81be0c9a76

cached-config-operations

main

revert-7033-patch-1

test_dylint

v2-1-blob-ciphers-key-ids

v2-2-registration

v2-3-key-rotation

v2-4-sdk-live-tests

v2-registration

0.10.0

0.11.0

0.12.0

0.13.0

0.9.0

1.0.0

1.1.0

1.10.0

1.11.0

1.12.0

1.13.0

1.13.1

1.14

1.14.1

1.14.2

1.15.0

1.15.1

1.16.0

1.16.1

1.16.2

1.16.3

1.17.0

1.18.0

1.19.0

1.2.0

1.20.0

1.21.0

1.22.0

1.22.1

1.22.2

1.23.0

1.23.1

1.24.0

1.25.0

1.25.1

1.25.2

1.26.0

1.27.0

1.28.0

1.28.1

1.29.0

1.29.1

1.29.2

1.3.0

1.30.0

1.30.1

1.30.2

1.30.3

1.30.4

1.30.5

1.31.0

1.32.0

1.32.1

1.32.2

1.32.3

1.32.4

1.32.5

1.32.6

1.32.7

1.33.0

1.33.1

1.33.2

1.34.0

1.34.1

1.34.2

1.34.3

1.35.0

1.35.1

1.35.2

1.35.3

1.35.4

1.35.5

1.35.6

1.35.7

1.35.8

1.36.0

1.37.0

1.37.1

1.37.2

1.37.3

1.4.0

1.5.0

1.6.0

1.6.1

1.7.0

1.8.0

1.9.0

1.9.1

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '81be0c9a76'

${ noResults }

Commit Graph

1 Commits (81be0c9a76e9879e435f4482215ef3c561b6bb7d)

Author	SHA1	Message	Date
Brandon George	81be0c9a76	Add "Create new collections" custom role permission Bitwarden's custom role has a `Create new collections` permission which allows a member to create collections without giving them access to every collection in the organization. The three collection options were collapsed into the single access_all flag and all of them had to be checked to set it, so that role could not be configured. Store the permission separately in a new create_new_collections column on users_organizations so it can be granted on its own: - `Manage all collections` is now represented by `Edit any collection` and `Delete any collection` alone, since those are the only options the parent checkbox still drives - `Create new collections` is read and stored independently, and is implied by access_all - post_organization_collections accepts the request when the member has either flag, and assigns the creator to the new collection so a member without access_all does not lose access to it right after creating it, unless they already assigned themselves - limitCollectionCreation is reported accordingly so the clients enable the `New collection` button The nested `Create new collections` option was hidden by the web-vault CSS overrides, so show it as a stand-alone option. `Edit any collection` and `Delete any collection` stay hidden, as those are still only supported together through access_all. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2 months ago