Specifications

Setting File and Folder Permissions (Windows)
50 Snap Server Administrator Guide
• Interaction between share-level and file-level access permissions —
When both
share-level and file-level permissions apply to a user action, the more restrictive
of the two applies. Consider the following examples:
Example A: More restrictive file-level access trumps more permissive share-level
access.
Example B: More restrictive share-level access trumps more permissive file-level
access.
The NFS Warning Message
The Administration Tool displays a warning that security settings for a share may
not apply to NFS clients when all of the following criteria are met:
• Access to the server via NFS is enabled
• Access to the share via NFS is enabled
• The AllUsers group is not given full access
Setting File and Folder Permissions (Windows)
On files and directories following the Windows security model, the GuardianOS
supports the use of the Windows NT, 2000, or XP interface to set directory and file
permissions for local and domain/ADS users and groups on the Snap Server. On a
directory, administrators can also set inheritance permissions that will be inherited
by subordinate folders and files created within the directory.
Default File and Folder Permissions
When a file or directory is created, the GuardianOS grants access to the accounts
listed in the following table. Access permissions for each account are inherited from
Share Level File Level Result
Full control Read-only to FileA Full control over all directories and files in
SHARE1 except where a more restrictive file-level
permission applies. The user has read-only
access to FileA.
Share Level File Level Result
Read-only Full control to FileB Read-only access to all directories and files in
SHARE1, including where a less restrictive file-
level permission applies. The user has read-only
access to FileB.