Re: customizing menus on team site template

From: Bob (Bob_at_discussions.microsoft.com)
Date: 01/09/05


Date: Sun, 9 Jan 2005 09:35:02 -0800

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: FC1 - Evolution Pauses While Building Vfolders
    ... Due to the large amount of email received/sent each day to clients, ... > I use an elaborate email layout containing a separate folder ... > required folders for email sorting usage. ...
    (alt.os.linux.redhat)
  • Re: Slow network performance
    ... no antivirus since clients cannot access the Internet. ... folders containing a rather large amount of sub-folders. ... Please reply back to the newsgroup or forum for collaboration benefit among ... Microsoft Certified Trainer ...
    (microsoft.public.windows.server.networking)
  • Re: Exchange Benefits for Mac users
    ... > shared folders, etc. ... extremely large UNIX shops to Exchange, one of which also used Meeting ... WebDAV clients will have the best ... IMAP clients can download meeting invites that have URL's appended to them ...
    (microsoft.public.exchange.clients)
  • Re: Access Rights Confusion
    ... what do you tell clients looking for a collabration ... hack to hide all the admin options, which can be switched off if the user is ... > Could someone please help me understand the logic behind how Sharepoint ... > Administrator rights? ...
    (microsoft.public.sharepoint.portalserver.development)
  • Re: OSX users can not rename folders on W2K server
    ... When you say the Windows clients rights, ... If that is the case the network accout has ... OSX clients be connecting via SMB or via AFP, ... >> the folder off the W2K network and onto their local OSX ...
    (microsoft.public.win2000.macintosh)