About BrightWork and SharePoint Security

BrightWork uses standard SharePoint security. See below for the various permissions required to

See the links below for some information from Microsoft on managing SharePoint security:

Managing permissions and security

Create a Personal Report

Users require Contribute level or higher permissions to create a personal report. This is enabled by BrightWork Reporter having the non-default property of allowing users to edit scriptable web parts. To restore BrightWork Reporter to the default setting, and only allow users with Designer level or higher to create personal reports, you can edit the web.config file.

Design Sync Permissions

This section outlines the various permissions needed to use the Design Sync features.

To Sync a Site with a Template design, or to Bind a Site to a Template, you Need:

Create Projects, Templates and Portfolios using BrightWork Copy Site

This section outlines the various permissions needed to use the BrightWork Copy Site.

For maximum simplicity, BrightWork recommends that individuals tasked with creating projects, templates and portfolios have Full Control at the site collection level and that Permission Inheritance is enabled through out the site collection; however, we appreciate that there will be many situations where it is not possible to have permission inheritance globally enabled, therefore we have detailed the various local permissions that are required to create projects, templates and portfolios.

To:

You Need:

Custom Security

BrightWork Copy site does not copy custom security settings such as unique website permissions or fine-grained permissions such as permissions on a list or library, folder, or item or document.

Note:

If a user creates a template or a project from a project, that contains items (e.g. a list) that she has fine-grained access to, then those items will be copied and viewable to all users in the target site. This is the same behavior as SharePoint. This means you should exercise caution when using sites with fine-grained permission as a source for a template or a project.

If a user creates a template or a project from a project, that contains items (e.g. a list) that she does not have access to, then those items will not be copied to the target site.

If a user creates a template or a project from a template, that contains items (e.g. a list) that she does not have access to, then those items will be copied to the target site. This means you should not use fine-grained permissions in templates.

Send feedback on this help.