Question
I would like to restrict specific content visibility in a topic to specific authorized users. In this way a user in a specific group can see content that other users cannot.
I would also like to use this in the web map in the LeftBar topic, which would allow me to hide webs that a user is not authorized to access.
I've tried this by using INCLUDE statements that link to DENYWEBVIEW limited webs but the page then displays a "no permission" error, which lacks the subtlety of what I'm l looking for.
Are there statements that can limit visibility of the content they contain based upon certain criteria, such as group membership?
Environment
--
CharlesLong - 20 Jun 2007
Answer
If you answer a question - or someone answered one of your questions - please remember to edit the page and set the status to answered. The status selector is below the edit box.
I don't use include in my twikis and I have been able to totally hide topics and webs from users. You can hide webs by simply add denywebview in the preferences to group and users. This web will not appear in the leftbar for the particular users. How are you doing the include?
--
ZakaiKinan - 20 Jun 2007
I am not trying to limit the access to whole topics or webs but more to content IN a topic. Essentially a statement like such:
%CONDITIONALSTART{group == AuthorizedGroup}%
hidden content- you can't see this unless you're authorized
%CONDITIONALEND%
In this example, if the user is in the group
AuthorizedGroup, they can see the
, in best example an include from a web that is also protected with a ALLOWEBVIEW. Otherwise the content is suppressed.
Another example could be
%CONDITIONALSTART{user == TWikiGuest}%
Hi and welcome to my TWiki! Please register to have access to editing and creating pages!
%CONDITIONALEND%
Where only a new user (or one not logged in) gets the welcome message.
-- CharlesLong - 21 Jun 2007
I THINK this should address my issue, with a creative application of twiki variables. I'll detail later.
IfStatements
-- CharlesLong - 21 Jun 2007
Seems to be resolved...
-- PeterThoeny - 10 Aug 2007