DeliverPoint allows a variety of users: DeliverPoint permission operators, site collection administrators, site owners, power users, and end users; to manage SharePoint permissions in Microsoft® SharePoint® Server 2013, Microsoft® SharePoint Foundation 2013, or Microsoft® SharePoint 2016 on-premises deployments.

Users can use DeliverPoint to manage permissions from:

DeliverPoint allows you to manage permissions at the account, farm, Web Application, site collection, site, list, folder, and list item levels. To manage account permissions or permissions at a web application, site collection or site level, you use the DeliverPoint dashboard. You can also use the Discover Site Permissions link from the Settings Click Settings menu to manage permissions at a site level. By default, to manage list, folder, or item permissions, navigate to the list and use the DeliverPoint Ribbon. List and folder permissions can also be managed using the DeliverPoint dashboard when the Show Lists and Libraries in Reports check box is selected on the DeliverPoint Treeview settings page.

For example, when using the DeliverPoint dashboard, where you can switch between an Account or Farm centric view, select one or more checkboxes to the left of a SharePoint object in the tree view, which activates the Commands Ribbon and then click the required command.

Initiate DeliverPoint Command

The DeliverPoint command you choose affect all permissions for the targeted account in scope. For example, when you select Copy Permissions at the Managed Path level, since all site collections within the Managed Path are part of the inheritance chain, they are said to be in scope. Site collections that exist under other Managed Paths would not be in scope because they are not part of the selected Managed Path’s inheritance chain.

It is important to know which objects are in scope for every command you execute using DeliverPoint. For example, if you select the Delete Permissions command at the Farm level, then all Web Applications, Managed Paths, site collections, sites (webs), lists, folders, and list items are in scope for this action. Be sure to target the execution of permissions at the intended level of inheritance so you don’t change permissions for a user on the wrong or unintended objects.

References

Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Please do not use this for support questions.
For customer support, please contact us here.

Post Comment