brainstorming1Add my vote for this tag create new tag
, view all tags
Allow access to topic pages to check permissions, overriding web permissions.

Currently TWiki's permissions checking stops when a deny is reached on any of the following:

  • Access to site
  • Access to web
  • Access to topic

Some sites have a need to allow access to specific topics in specific webs, but to disallow otherwise. Examples:

  • collaboration webs for confidential (multiple) client / service-provider (multiple) projects a sort of inter-company "intranet" for particular projects.
  • school web - schools don't like the idea of open webs because they like to guard their reputation, parents don't like the idea of open webs because of fears of "advertising" information about their children on the internet
  • A TWiki server might allows lots of people to join, but keep everyone's details private by default. You would then deny access to everything, and then very specifically open up holes, rather than have the default being open, and close down pages.

For more examples see the parent of this topic.

The suggestion here is to add a 3rd form of access control in addition to READ & WRITE - ACCESSCHECKONLY. ACCESSCHECKONLY would mean the site was read access denied.

Currently I'm thinking a syntax along the lines of:


Though it might be nicer to have an implicit group of "Main.AllUsers", and have the definition as:

In terms of open access to data this does go against TWiki's principles, but in terms of corporate appeal, unfortunately secrecy is a major factor, and as a result this sort of feature matches that criterion.

Suggestions/ideas for syntax welcomed!

-- TWikiGuest - 11 Jun 2003

Edit | Attach | Watch | Print version | History: r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r3 - 2008-08-25 - TWikiJanitor
  • Learn about TWiki  
  • Download TWiki
This site is powered by the TWiki collaboration platform Powered by Perl Hosted by OICcam.com Ideas, requests, problems regarding TWiki? Send feedback. Ask community in the support forum.
Copyright © 1999-2018 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.