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

DOCS Grammar fixes

Browse Source
This commit is contained in:
Ingo Schommer 2019-05-23 10:38:56 +12:00
parent 1cb22b665d
commit 75f87ac409
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/en/02_Developer_Guides/14_Files/03_File_Security.md
View File

@ -23,7 +23,7 @@ Versioning stage:
Access restrictions:
* "Unprotected file" (default): A file without access restrictions
* "Unprotected file" (default): A file without access restrictions.
* "Protected file": A file with access restrictions.
Note that draft files are always protected, and even published files
can be protected if they have access restrictions.
@ -35,10 +35,10 @@ for example `canView()` (see [permissions](/developer_guides/security/permission
The permission model defines the following actions:
* View: Access file metadata in the database
* Edit: Edit file metadata as well as replacing the file content
* Create: Create file metadata and upload file content
* Delete: Delete file metadata and the file content
* View: Access file metadata in the database.
* Edit: Edit file metadata as well as replacing the file content.
* Create: Create file metadata and upload file content.
* Delete: Delete file metadata and the file content.
* Download: Access the file content, but not the file metadata.
Usually treated the same as "View".
@ -48,7 +48,7 @@ There's a few rules guiding their access, in descending order of priority:
They bypass any SilverStripe permission checks (served directly by the webserver).
* Access can be restricted by custom `can*()` method implementations on `File`
(through [extensions](/developer_guides/extending/extensions)).
This logic can overrule any further restrictions below.
This logic can overrule any further restrictions below.
* Users with "Full administrative rights" (`ADMIN` permission code)
have view and edit access by default, regardless of further restrictions below.
* Users with "Edit any file" permissions (`FILE_EDIT_ALL` permission code)