![]() Specific user permissions on content take precedence over group permissions on content. Unspecified results in Denied if no other permissions are specified. When the parent project permissions are not locked, owners can change permissions for their published content.įor more information, see Set Users’ Site Roles and Use Projects to Manage Content Access. Owners always get full access to the content they’ve published. Server and site administrators can access all site content and take actions on it. Site rolesĪ user’s site role determines the maximum permissions allowed for that user. ![]() ![]() Hover over a capability box to see a tooltip with details on whether a capability is allowed or denied.Ĭustom indicates a user’s capabilities have been changed from the initial settings for their site role or content role.įor more information, see Permissions. 4 View a user’s effective permissionsĪfter you save the permissions rule for the group, you can view the effective permissions for that content.Ĭlick a group name to see the group's users and their permissions. Whether a user can set permissions is based on their site role and how their Set Permissions capability is set. Click a capability to set it to Allowed or Denied, or leave it Unspecified. Select a permissions role template to apply an initial set of capabilities for the group. 3 Create a permissions ruleĬlick Add a user or group rule, select Group, and then find and select the group. If you’re not sure where to find a child project, display filters, and select Show all projects. Navigate to the project you want to update, select its Actions ( …) menu, and then select Permissions. The site’s Content page shows the top-level projects.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |