tonyair/silverstripe-framework
1
0
Fork 0
mirror of https://github.com/silverstripe/silverstripe-framework synced 2024-10-22 12:05:37 +00:00
Code Issues Projects Releases Wiki Activity

Merge pull request #2704 from Juanitou/patch-1

Browse Source 
Typography review
This commit is contained in:
Will Rossiter 2013-12-05 18:57:55 -08:00
commit 8ad172cff5
1 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/en/topics/access-control.md
View File

@ -9,9 +9,9 @@ There are a number of ways to restrict access in SilverStripe. In the security
that have access to certain parts. The options can be found on the [permissions](/reference/permission) documentation. that have access to certain parts. The options can be found on the [permissions](/reference/permission) documentation.
Once you have groups, you can set access for each page for a particular groups. This can be: Once you have groups, you can set access for each page for a particular groups. This can be:
- anyone * anyone;
- any person who is logged in * any person who is logged in;
- a specific group * a specific group.
It is unclear how this works for data-objects that are not pages. It is unclear how this works for data-objects that are not pages.
@ -20,13 +20,13 @@ It is unclear how this works for data-objects that are not pages.
In the security tab you can make groups for security. The way this was intended was as follows (this may be a counter In the security tab you can make groups for security. The way this was intended was as follows (this may be a counter
intuitive): intuitive):
* employees * employees
* marketing * marketing
* marketing executive * marketing executive
Thus, the further up the hierarchy you go the MORE privileges you can get. Similarly, you could have: Thus, the further up the hierarchy you go the MORE privileges you can get. Similarly, you could have:
* members * members
* coordinators * coordinators
* admins * admins
@ -36,7 +36,7 @@ privileges from its parent group.
## Permission checking is at class level ## Permission checking is at class level
SilverStripe provides a security mechanism via the *Permission::check* method (see `[api:LeftAndMain]` for examples on how SilverStripe provides a security mechanism via the *Permission::check* method (see `[api:LeftAndMain]` for examples on how
the admin screens work) the admin screens work).
(next step -- go from *Permission::checkMember*...) (next step -- go from *Permission::checkMember*...)