Re: customizing menus on team site template

From: Mike Walsh (englantilainen_at_hotmail.com)
Date: 01/09/05 

Date: Sun, 9 Jan 2005 20:06:42 +0200

As Administrator you can get round this as I wrote by creating individual
web part pages for each group of users.

So Group One's webpart page could contain doc lib1; 2 and 3 (all of which
Group One can access)
Group Two's webpart page doc lib 1 and 3
etc.
Group 3 doclib 3, 4, 5.
I.e. there can be overlaps.

You would specify for each doc lib who can access that doc lib and would
have links from the site's main page specified as
Finance
Programmers
etc. (i.e. the group of people behind UserGroup 1, 2, 3) and if they then
click on the wrong *single* link (to a webpart page that isn't theirs) then
they are just testing your security.

So there is a workaround if the Admin works at it.

Most people would agree with you that they would prefer it to be done in
another way but there was a massive re-write between STS and WSS and I
suppose they simply ran out of time to re-write this security section too.
[Needless to say pure speculation, I don't know]

Mike Walsh, Helsinki, Finland

"Bob" <Bob@discussions.microsoft.com> wrote in message
news:CAA39733-1E26-4748-88BB-B5C89AD0301B@microsoft.com...
> Mike,
>
> I'm totally confused why Microsoft designed the security right in this
> way.
> Imagine you have over 10 different clients accessing your site and you
> have
> about 20 folders. All of these 10 clients will see 20 folders and each
> individual client might have access to 2-3 folders. They will click on 20
> folders and they will get the login box for 3 three times till they find
> out
> they do not have access. This is totally frustrating and is a major turn
> off
> for users to use SharePoint. I believe this is a major flaw in SharePoint
> design.
> Thanks for your help.
>
>
> Bob
>
> "Mike Walsh" wrote:
>
>> Unlike Jim I would see this as one of those common requests for a
>> different
>> look of a WSS web page depending on who the user / which site group is
>> who
>> is accessing the page.
>>
>> The standard answer is that everyone sees the same page and only when
>> they
>> click on a menu item they are not allowed to access (or in some cases
>> when
>> they come to save changes) are they asked for credentials if they don't
>> have
>> suitable rights.
>>
>> You can stop people from accessing an entire site / an entire subsite or
>> an
>> entire document library, but when there everyone will see the entire
>> site.
>>
>> Maybe Jim ois thinking about the special case of a web part page. This
>> will
>> contain various web parts and if (say) a particular user (or site group)
>> doesn't have rights to access a document library that is included in that
>> web part page in web part form, he will not be able to access the web
>> part
>> page at all.
>>
>> But basically (and you'll see many messages on this throughout the
>> newsgroups and comments that people want this functionality changed in
>> the
>> next release) you always see the same information once you can access a
>> WSS
>> page irrespective of site group membership and rights.
>>
>> Mike Walsh, Helsinki, Finland
>> WSS FAQ at http://wss.collutions.com
>> Please reply to the newsgroup
>>
>> "Bob" <Bob@discussions.microsoft.com> wrote in message
>> news:03547C04-9DB6-463F-9D9F-6C78DFE7D667@microsoft.com...
>> >I have various groups access my site based on team site template, and
>> >based
>> > on users I need to eithr hide or display a menu on the left menu. For
>> > example
>> > if user 1 login ot the site he should not see the task, discussion,
>> > survey
>> > and some folders under documents. The user 2 login and see different
>> > menu
>> > based on his login. Is this possible?
>> >
>> > Thanks,
>>
>>
>>

Relevant Pages

  • Re: User vs Administrator Doc Lib Security
    ... My assumption is that (and it's easily checkable by looking at what rights are listed as removable when you amend access rights to a doc lib, is that the admimistrator of the site is not listed - just as was the case in v2. ... I.e. you can't remove him/her so you just have to make sure the admin of the site is someone allowed to access the doc lib. ... Mike Walsh ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Secure shared web hosting using MAC Framework
    ... run the web server and web users shell in a jail, ... Those rights should have priority on any traditional unix file ... This directive allows you to disable certain functions for security reasons. ... Web users and executed web scripts shouldn't be able to read ...
    (FreeBSD-Security)
  • Orwell meets Kafka
    ... THE OTHER DAY, the new secretary of homeland security, Michael Chertoff, scrapped the moronic rule requiring everyone to stay seated for 30 minutes coming in or out of Ronald Reagan Washington National Airport. ... If the American republic was built on any core principle, that principle is the rights of people to be free from the abuses of unchecked power. ...
    (soc.culture.australian)
  • RE: Rights
    ... the benefit is improved security. ... in restricting rights in favor of increased security. ... EARN A MASTER OF SCIENCE IN INFORMATION ASSURANCE - ONLINE ... The NSA has designated Norwich University a center of Academic ...
    (Security-Basics)
  • Re: New to SMS - have a Collections question.
    ... I loaded the SMS Admin Console on the ... comprimise the security of the servers. ... SMS security is a bit different from normal Windows security. ... Access to objects is based on Security Rights (if you scroll down the list ...
    (microsoft.public.sms.admin)