One thing that is getting on my nerves is that controls and links such as "New Item" and "Modify Settings and Columns" appear in list views even for users who have read-only access to the list. For various reasons, I don't want them there, and I don't want users to be requesting access, or even be aware that they can request access. If a user does not have rights to do something, then the option to do it should not appear. But how on earth do I get rid of them???
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Locking down controls and links in a list view
- Thread starter mhiney
- Start date
- Thread starter
- #3
Cheers. Deeply nasty work-around though. I'd prefer a more elegant solution, one that lets people with admin or editorial rights see the links. Hoping as I am to devolve a lot of editorial responsibility to actual users, this is kinda necessary. Time to hack the "schema.xml" then...
lolz
i wished they had included this feature. Many people are asking for it. and I know using frontpage seems odd to do this but until now i found it to be the only solution (unless you develop some custom stuff).
if you are lucky to have it done through modifying the schema please let us know.
I had allready some developers look for it but they haven't found a good sollution (or one that's not "dirty")
//Bart
i wished they had included this feature. Many people are asking for it. and I know using frontpage seems odd to do this but until now i found it to be the only solution (unless you develop some custom stuff).
if you are lucky to have it done through modifying the schema please let us know.
I had allready some developers look for it but they haven't found a good sollution (or one that's not "dirty")
//Bart
- Thread starter
- #6
- Thread starter
- #7
Well, I've just spent a day working at it with an SP guru, and we got it working with a deeply nasty ADSI hack.
Basically, we assign a windows security group to a SharePoint role (and we must never ever add users to SharePoint roles), then use some client-side VBScript in schema.xml to enumerate the current user's group membership, then, after having bunged an ID on any HTML elements we want to selectively display, set their style to "display:none" if the user is not a member of the windows group that should be able to see the stuff.
I told you it was deeply nasty. Both of us ended up shaking our heads and muttering darkly at the end of it all...
Basically, we assign a windows security group to a SharePoint role (and we must never ever add users to SharePoint roles), then use some client-side VBScript in schema.xml to enumerate the current user's group membership, then, after having bunged an ID on any HTML elements we want to selectively display, set their style to "display:none" if the user is not a member of the windows group that should be able to see the stuff.
I told you it was deeply nasty. Both of us ended up shaking our heads and muttering darkly at the end of it all...
- Status
Similar threads
