Skip to content

Commit 63543e8

Browse files
committed
minor #13553 Renaming "Securing Individual Objects" (ThomasLandauer)
This PR was merged into the 4.4 branch. Discussion ---------- Renaming "Securing Individual Objects" Reason: I never understood what "objects" referred to in "Securing Individual Objects". Renaming it to "Individual User Permissions" is another step forward at solving the "discoverability" problem I mentioned in #11505 However, I would still move it higher up on the page (above Roles), since I see it like this: Having *Individual* users is basic for any security system; grouping those users into something called Roles is advanced. Second, since Voters are described on a separate page, I would also defer Roles to another page, off the main security page. Commits ------- bce240d Renaming "Securing Individual Objects"
2 parents 2209ca2 + bce240d commit 63543e8

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

security.rst

+3-3
Original file line numberDiff line numberDiff line change
@@ -663,11 +663,11 @@ Securing other Services
663663

664664
See :doc:`/security/securing_services`.
665665

666-
Securing Individual Objects
667-
~~~~~~~~~~~~~~~~~~~~~~~~~~~
666+
Setting Individual User Permissions
667+
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
668668

669669
Most applications require more specific access rules. For instance, a user
670-
should be able to only edit their own comments on a blog. Voters allow you
670+
should be able to only edit their *own* comments on a blog. Voters allow you
671671
to write *whatever* business logic you need to determine access. Using
672672
these voters is similar to the role-based access checks implemented in the
673673
previous chapters. Read :doc:`/security/voters` to learn how to implement

0 commit comments

Comments
 (0)