more minor typo fixes

This commit is contained in:
Rachid Mrad 2023-11-28 13:32:48 -05:00
parent bd6eabe916
commit b6b251b287
No known key found for this signature in database
GPG key ID: EF38E4CEC4A8F3CF
3 changed files with 8 additions and 8 deletions

View file

@ -19,7 +19,7 @@ To do this, do the following:
3. Click on their username, then scroll down to the `User Permissions` section.
4. Under `User Permissions`, see the `Groups` table which has a column for `Available groups` and `Chosen groups`. Select the permission you want from the `Available groups` column and click the right arrow to move it to the `Chosen groups`. Note, if you want this user to be an analyst select `cisa_analysts_group`, otherwise select the `full_access_group`.
5. (Optional) If the user needs access to django admin (such as an analyst), then you will also need to make sure "Staff Status" is checked. This can be found in the same `User Permissions` section right below the checkbox for `Active`.
6. Click `Save` to apply all changes
6. Click `Save` to apply all changes.
## Removing a user group permission via django-admin
@ -30,7 +30,7 @@ If an employee was given the wrong permissions or has had a change in roles that
3. In this table, select the permission you want to remove from the `Chosen groups` and then click the left facing arrow to move the permission to `Available groups`.
4. Depending on the scenario you may now need to add the opposite permission group to the `Chosen groups` section, please see the section above for instructions on how to do that.
5. If the user should no longer see the admin page, you must ensure that under `User Permissions`, `Staff status` is NOT checked.
6. Click `Save` to apply all changes
6. Click `Save` to apply all changes.
## Editing group permissions through code
@ -40,4 +40,4 @@ We can edit and deploy new group permissions by:
2. Duplicating migration `0036_create_groups_01`
and running migrations (append the name with a version number
to help django detect the migration eg 0037_create_groups_02)
3. Making sure to update the dependency on the new migration with the previous migration
3. Making sure to update the dependency on the new migration with the previous migration.