Tree: d5f3584ee4

cached-config-operations

main

revert-7033-patch-1

test_dylint

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.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 'd5f3584ee4'

${ noResults }

Commit Graph

1 Commits (d5f3584ee4681ffc91b9dda71aa098c55557c060)

Author	SHA1	Message	Date
tom27052006	5482855dc4	Notify the grantors whose emergency access the auto confirm policy drops Dropping an emergency access hits two people, and only one of them is the member the organization acts upon. The other one is the grantor of a grant the member merely held, who can be a complete outsider to that organization and would otherwise silently lose a part of its account setup. Every grantor now gets a single mail listing all of the contacts it lost, which is how Bitwarden notifies as well. The mail deliberately does not name a reason: a recipient can be outside of the organization which triggered this and has no business learning about the memberships of others. The rows are gone by the time the mail goes out, so a failing send is logged instead of failing the request, which would report a rollback that did not happen.	1 week ago