Re: restricted area
From: Bil Simser [MVP] (bsimser_at_shaw.ca)
Date: 02/17/05
- Next message: Juhani: "Re: Edit In Data*** Control"
- Previous message: xyrus: "restricted area"
- In reply to: xyrus: "restricted area"
- Next in thread: xyrus: "Re: restricted area"
- Reply: xyrus: "Re: restricted area"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 17 Feb 2005 02:54:53 +0000
As always, the answer is it depends.
If you're just interested in hiding an area that's easy.
1. Create an audience in the portal for your users
2. Add the users/domain groups you want in the audience
3. Compile it
4. Assign it to an area
5. Set the security so those users do not have access to it
You need to do both. Security will lock it down and not give them
access, even if they had the url. The audience will filter the view of
it so they don't see it.
If it's a list or library, you can open it up in FrontPage 2003 (no
other way that I know of) and select the list from the site, bring up
it's properties and mark it hidden. A user can still get to it if he
knows the url but at least it won't show up in lists and such. Note:
This action will *not* unghost your site/page as you're modifying a
list, not a page in the portal.
-- Bil Simser http://weblogs.asp.net "xyrus" <xyrus@discussion.microsoft.com> wrote in message news:xyrus@discussion.microsoft.com: > Hi all, > > How could we hide the area or even a list or library from showing to user > > who doesn't have access into it? Instead of prompting for username and > password, i think it would be better if we hide it straight away. Are > there > any way to do this? > > Thank you.
- Next message: Juhani: "Re: Edit In Data*** Control"
- Previous message: xyrus: "restricted area"
- In reply to: xyrus: "restricted area"
- Next in thread: xyrus: "Re: restricted area"
- Reply: xyrus: "Re: restricted area"
- Messages sorted by: [ date ] [ thread ]