RE: Very, very, very limited security options in SharePoint document l

From: Jim Buyens (news_at_interlacken.com)
Date: 01/26/05


Date: Wed, 26 Jan 2005 08:53:08 -0800

The mindset of Windows SharePoint Services is that of *team* Web Sites.

Usually, permissions within a team are very simple, such as "everyone has
the same permissions" or "everyone has the same except a few administrators".

If you find the need for more complex permissions than a SharePoint library
can accomodate, then you probably have people from multiple teams using the
same library. This is not the intended use. Instead, you should set up a
separate Team Site for each team, with separate libraries, and then use
SharePoint Portal Server to integrate them into one view.

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Windows SharePoint Services Inside Out
|| Microsoft Office FrontPage 2003 Inside Out
||---------------------------------------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------

"G. Tarazi" wrote:

> This is the second release, and something as simple as simple as simple as
> having a document library, 20 users, 5 groups, and giving different
> permission to individual users and or groups to the document library is not
> possible.
>
>
>
> Just a very limited set of permissions to that library in a very limited
> way.
>
>
>
> Perhaps in Microsoft Share Point Windows Services Release 430,556,123
> Service Pack 12, this problem will be solved, and the security then will be
> like Windows NT 4.0 today.
>
>
>
> Folder security was introduced by Microsoft back in Windows NT 3 long long
> long time ago. And improved a lot in 2000, and 2003, if you happen you are a
> developer on the share point team, and you have not heard about it (windows
> folder security), make sure your file system is NTFS, right click a file,
> and go to the security tab, and have a look at the options :-)
>
>
>
> The security here is much primitive than NT 3, what is the point of going 20
> years back?
>
>
>
>
>



Relevant Pages

  • RE: Error 1402
    ... >Microsoft Corporation ... >>This is a permissions issue that must be fixed through ... >>the Windows operating system. ... >>Do not use the registry key given in the Microsoft ...
    (microsoft.public.windowsxp.security_admin)
  • RE: Computer & Local Profile Migration Trouble
    ... We can adjust registry permissions by using GPO in AD-based domains. ... the Windows 2000 Resource Kit Tools document or run the following command: ... |Subject: RE: Computer & Local Profile Migration Trouble ... Produced By Microsoft MimeOLE V5.50.4910.0300 ...
    (microsoft.public.windows.server.migration)
  • Re: Question regarding microsoft security policy
    ... Microsoft does not consider an application certified for Windows 2000 [or whatever ... permissions to give regular users the same permissions as power users. ... then you can logon to a computer as a regular user and then use runas ...
    (microsoft.public.win2000.security)
  • RE: Access 97 runtime on XP
    ... permissions on the following registry keys: ... inherit parent permissions). ... Microsoft Access Support ... Running the SCAN program from the Windows Update site will help ...
    (microsoft.public.access.setupconfig)
  • Re: Microsoft to limit Windows apps on IA64
    ... > I think that Longhorn on IA64 will be the last version of Windows for ... > IA64. ... Microsoft is probably constractually obligated to release it. ...
    (comp.os.vms)