Question

We're running TWiki on behalf of a client. They have a "middle-sized" Wiki which is used for organising and sharing information within the "IT Team": the client, some other IT consultants and ourselves. It holds things like meeting minutes, project-related documents, a GNats database and so forth.

This is all supported by TWiki running on a 1&1 Managed Server. We use Apache security to force people to log on, and after that everything is open.

Now, there is a desire to give an outside individual access to a part of this Wiki: those pages related to a specific project.

I can think of a way to do this, but I'm wondering if there isn't a better way...

Left to my own devices, the approach I would try is...

1. Create a TWiki group "Visitors"
2. Register this person, and put them in that group
3. Move all the pages we want shared to a new "Shared" web
4. Deny web access to "Visitors" in the sitewide preferences (can I do that?)
5. Allow web access to Visitors in the Shared web

On this approach, all "sharing" is with "everybody", in the sense that every "Visitor" could see everything that any "Visitor" could see. That's OK at the moment, because we've only got one visitor in mind. But it is the sort of thing that I can imagine coming up.

Is this actually going to work? Can anyone see anything wrong with it, or suggest a better approach?

Environment

-- RobertInder - 24 May 2007

Answer

If you answer a question - or have a question you asked answered by someone - please remember to edit the page and set the status to answered. The status is in a drop-down list below the edit box.

• Require users to login, also for view. That is, require auth for all TWiki scripts
• Do not use additional TWikiAccessControl for these webs: Main, TWiki, Sandbox. They are accessible to all registered users.
• Lock down view & edit to all webs where the outside individuals should not have access to. Do that by maintaining an InsidersGroup, and using this group to protect the insiders webs.

-- PeterThoeny - 06 Jul 2007