Adaptec 5325301638 - Snap Server 4500 NAS, Administrator'S Manual

Page: 63 / 148

Share-Level Access Permissions
Chapter 6 Share and File Access 49
Security Models, SnapTrees, and Shares
In the course of creating a share that points to a volume or to a directory on the root
of the volume (aka SnapTree directory), you must assign a security model to the
volume or SnapTree directory. Thereafter, security models for these entities are
managed on the
Security > SnapTrees
screens.
Share-Level Access Permissions
Share access permissions for all client platforms are configured by navigating to the
Security > Share Access
screen and clicking a share name. When a share is created,
the default permission granted to users, groups, and NFS clients is full control. You
can restrict selected users and groups to read-only access; and you can specify how
the share will be exported to NFS clients.
Share Access Behaviors
Administrators tasked with devising security policies for the Snap Server will find
the following share access behaviors of interest:
• Share access defaults to full control —
The default permission granted to users
and groups when they are granted access to the share is full control. You may
restrict selected users and groups to read-only access.
• Share access permissions are cumulative —
A user's effective permissions for a
resource are the sum of the permissions that you assign to the individual user
account and to all of the groups to which the user belongs. For example, if a user
has read-only permission to the share, but is also a member of a group that has
been given full-access permission to the share, the user gets full access to the
share.
Share-Level Access Permissions and Attributes
Read-only R Users can navigate the share directory structure and view files.
Full control RW Users can read, write, modify, create, or delete files and folders
within the share.
Hidden H The share is hidden in Web View to clients accessing the server
over the SMB, HTTP, AFP, and FTP (but visible to NFS) protocols.
Invalid B Path invalidation is most commonly caused by deleting or renaming
the directory to which the share points. To remedy this situation,
restore the original path as shown in the Path column of the table or
remap the share.