Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

modify webparts permission

  Asked By: Colt    Date: Sep 25    Category: Sharepoint    Views: 4691

I've been trying to figure this out for a couple days no to no avail.
Your help would be much appreciated. So here it is. How do I take away
user's (user that belongs to the sharepoint 'member'/'contributor'
ability to modify web parts without taking away their ability to edit
list and document library content?



6 Answers Found

Answer #1    Answered By: Talia Johns     Answered On: Sep 25

The contribute permission  level includes a permission called 'Add/Remove
Personal Web Parts' which controls a user's ability  to personalize the
page. Unless you want to change the default contribute permission level
you would need to create a 'Policy for Web Application' in Central
Admin. If you create a new permission Policy Level in Central Admin you
can deny the 'Add/Remove Personal Web parts' permission and then apply
that policy to the user. This will remove that one permission from the
user anywhere they receive it in the Web Applications.

Answer #2    Answered By: Tera Callahan     Answered On: Sep 25

You can also create a new permission  group at the Top level site of your
Site Collection that gives someone the ability  to edit items in lists and
libraries while not giving them the ability to modify  web parts. This would
do the same sort of thing that Paul is suggesting, but at the Site
Collection level and not the entire web  application. Furthermore, you could
break permission inheritance and create this permission group for a given
site, or library  as well. Depends on how granular you would like to be.

To check this out, while at a top level site go to Site Actions>Site
Settings>(if publishing is enabled then)Modify All Site Settings then People
and groups. Once in People and groups select Site Permissions. Next go to
Settings>Permission Levels and the select Add a Permission level and take a
look at the permissions you can assign.

Answer #3    Answered By: Mark Davis     Answered On: Sep 25

That does not seem to do it. User with contribute role appear to be
able to still modify  web parts. Now, I don't know if this has anything
to do with it but the permission  you mentioned to take away appears to
refer to personal web  parts. Any thoughts?

Answer #4    Answered By: Delilah Mcpherson     Answered On: Sep 25

Did you create a web  Application policy to deny them that permission  or
edit the contribute permission level? If you just removed it from
contribute they may be getting it from a different group. That's why I
suggested the web app policy.

I just tried it on my test environment and when I remove that permission
from the user  it won't allow the user to add web parts  to the page.
They can still modify  existing web parts, but can't add new ones.
Personal web parts simply refers to web parts placed on a personal view
of a shared page.

Answer #5    Answered By: Gobinda Navalagi     Answered On: Sep 25

I think there was a misunderstanding somewhere along the way. I don't
want my users to be able to add or modify  existing web  parts. Can that
be done?

Answer #6    Answered By: Rose Silva     Answered On: Sep 25

If you remove the Add/Remove Personal web  Parts permission  they will not
be able to add web parts  to the page. They will still be able to move
existing web parts on the page or modify  the properties of those web
parts. Removing the Update Personal Web Parts permission will keep them
from editing the page and therefore prevent them from modifying existing
web parts. You must either remove those permissions from any Permission
level that the user  gets their rights from or create a Web Application
Security Policy that blocks those permissions for the user. Sorry, I
thought you just wanted to prevent them from adding new web parts.

Didn't find what you were looking for? Find more on modify webparts permission Or get search suggestion and latest updates.