Ben Thorner 171f911237 Audit when user permissions are changed ...

I've used the term "admin_roles" in the event data to try and show
that these are not the permissions we store in the DB. This is the
name we use for the abstracted form of permissions in the Admin app.
While we could store the DB permissions, that would be a bit more
effort and arguably it's clearer to keep the event data consistent
with the options the user actually saw / chose.

2021-07-21 15:32:03 +01:00

..

__init__.py

…

add_service.py

…

agreement.py

…

api_keys.py

…

broadcast.py

Allow users with new broadcast permissions access to routes

2021-07-19 14:40:13 +01:00

choose_account.py

…

code_not_received.py

…

conversation.py

…

dashboard.py

…

email_branding.py

…

feedback.py

…

find_services.py

…

find_users.py

…

forgot_password.py

…

history.py

…

inbound_number.py

…

index.py

…

invites.py

…

jobs.py

…

letter_branding.py

…

manage_users.py

Audit when user permissions are changed

2021-07-21 15:32:03 +01:00

new_password.py

…

notifications.py

…

organisations.py

Rename confusing variable

2021-07-15 14:21:58 +01:00

performance.py

…

platform_admin.py

…

providers.py

…

register.py

…

returned_letters.py

…

send.py

…

service_settings.py

Merge pull request #3969 from alphagov/fix-suspend-archive-perm-178770416

2021-07-15 09:29:20 +01:00

sign_in.py

Style link in wrong password error

2021-07-14 09:42:56 +01:00

sign_out.py

…

sub_navigation_dictionaries.py

…

templates.py

…

tour.py

…

two_factor.py

…

uploads.py

…

user_profile.py

…

verify.py

…

webauthn_credentials.py

…