Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit 41232a8

Browse filesBrowse files
committed
Merge branch '5.0'
* 5.0: Renaming "Securing Individual Objects"
2 parents 2eeb8ef + de3dfb2 commit 41232a8
Copy full SHA for 41232a8

File tree

Expand file treeCollapse file tree

1 file changed

+3
-3
lines changed
Filter options
Expand file treeCollapse file tree

1 file changed

+3
-3
lines changed

‎security.rst

Copy file name to clipboardExpand all lines: security.rst
+3-3Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -669,11 +669,11 @@ Securing other Services
669669

670670
See :doc:`/security/securing_services`.
671671

672-
Securing Individual Objects
673-
~~~~~~~~~~~~~~~~~~~~~~~~~~~
672+
Setting Individual User Permissions
673+
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
674674

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

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.