Security Examples
Review this information for low, medium, and high security scenarios and how to implement them in Users & security.
|
•
|
Low security scenario: Your Board Members require view permissions only for Board Member specific site pages. They should not have rights to create, edit, or delete content. |
|
|
To establish this low-level security, in Roles, create a role to group Board Members. You can do this by selecting a query or by including the individual members on the Members tab. Do not associate the role with a task group because Board Members should not be granted permissions for administrative tasks. Because there is not a role and task group association, there is not a security assignment for the role. |
Note: Task groups assign feature permissions for administrative tasks. To provide view rights for Board Members on your website, assign the View permission to the role on the Targeting & Security tab for the applicable pages, parts, and images. For more information, see Targeting & Security Tab.
|
•
|
Medium security scenario: Your Development Staff requires unique permissions for content author rights to specific site pages. |
|
|
To establish this medium-level security, in Roles, create a role to group Development Staff members. You can do this by selecting a query or by including the individual members on the Members tab. In Task groups, select the following site task rights under Website security. |
|
|
Under Page tasks, select Can create new Pages and Has access to Pages in Site Explorer. |
|
|
Under Part tasks, select Can create new Parts and Has access to the Part Gallery. |
|
|
Under Image tasks, select Can upload Images and Has access to Image Library. |
|
|
In Security assignments, associate the role and task group and assign it to the development site. |
Note: Task groups assign feature permissions for administrative tasks. To provide security for the Development Staff from your website, assign the View and Edit permission to the role on the Targeting & Security tab for the applicable pages, parts, and images. For more information, see Targeting & Security Tab.
|
•
|
High security scenario: Your Web Designer requires unique permissions for rights to edit pages, templates, and layouts. However, they cannot access Workflows and Merchant accounts. |
|
|
To establish this high-level security, in Roles, include individual Web Designer users in a role. |
|
|
Under Page tasks, select Has all Page related rights. |
|
|
Under Template tasks, select Has all Template related rights. |
|
|
Under Layout tasks, select Has all Layout related rights. |
|
|
In Security assignments, associate the role and task group and assign it to your default site. |
Note: To provide security for the Web Designers from your website, you can assign all permissions to the role on the Targeting & Security tab for the applicable pages, parts, and images. For more information, see Targeting & Security Tab.
|
|
For more information about Roles, see Roles. |
|
|
For more information about Task groups, see Task Groups. |