I can't see how people ask to be enrolled as writers on our new wiki

How does the 'page-level only' permission level work in 2.0? Does this prevent the user from accessing any folders other than those they are given specific permission to access? If so, that would be great.

I want anyone who knows the name of my wiki to have writer permission (because it's for students *and* prospective students, and I won't know who all of the prospective students are before they want to access the wiki, so issuing one-by-one invitations won't work for me).

How do I do that? And if I can't do that, what is the closest I can come to it?

I have a "Gold" wiki and am confused about how the different types of users work. I am a teacher in an elementary school and want to use it in the following ways:
1) Students can edit.
2) I will be notified when students edit and it will tell me who edited.
3) Nobody else can edit, but they can read.

I thought by adding users and setting them up as contributors or readers, this is how it would work. But I just received an email notification that someone "unknown" had edited the page. Based on the information edited, I knew which student it was, however, it didn't say his name. It just said "unknown". That makes me wonder if anyone can edit it. If so, have I set it up incorrectly?

Is there a max number of allowed administrators on one pbwiki site accessing a page at the same time? I have 25 administrators in a training, trying to post comments; some administrators were unable to gain the permissions needed to comment on a page? What would restrict their access, as an administrator, to not allow them to have permission to add a comment?
Thanks....

For licensing purposes, what's consitutes a "user"? We have 5-user license business license with a private wiki. We have 5 staff members who will have access of varying levels above "read". Will we need to upgrade our license to allow anyone else "read" access? Would the same be true for a public wiki? Would the same be true for a mostly-private pbwiki 2.0 with at least one "public" folder?

Thanks!

Would someone be able to explain how permissions work?
I run a consulting company. I also handle sales for a small local company.

Here's what I'd like to accomplish. Four different things.

(1) My own intranet. Private notes about websites, referrals, clients, customer feedback, data, etc. Viewable only by me.

(2) Client-to/from-Me communication. Like a Private Messaging board where we have a permanently recorded discussion, and share documents and drafts. Ideally I would not be able to edit what they say, and they would not be able to edit what I say - just add on to the current discussion. Viewable only by me and the specific client.

(3) Policies and procedures for my staff. Viewable by me and my staff. Editable by just me.

(4) Interactive pages that my staff or me could add to and change.

I hope PBwiki can do a lot of this. Maybe not everything, it isn't an all-in-one toolbox and understand that. I'm also evaluating TikiWiki and a hosted ticketing system (for possible use as a private message board.) I use DabbleDB for my sales CRM. Any thoughts on complementary software is also appreciated.

Hi,

Me again about the eagerly awaited page permissions. Is there going to be an option make a page or a folder public or private i.e. the default is private but you have the option to 'publish' it so it can be picked up by search engines. Currently this is only available as a wiki-wide option. I suppose if the wiki was 'public' the all you would have to do would assign permissions to each new page which would stop Jo public seeing it. However, I want my wiki to default to private and then have the option to 'publish' it. Is this going to be possible.

Seanmac

Hi Guys,

Just come out of the webinar! Really good , thanx. Page-level access is definitely going in the right direction. I think not integrating groups of users is a big mistake though. Lets go through an example. You use pbwiki as an intranet and you have 200 users. The CEO wants to produce a page on an exciting new update and he has given his senior managers read and edit access to the page so they can collaborate on it. Fine. Couple of days later, page is finalised and CEO wants to 'publish' it up to all of the employees to have read access. Are you seriously trying to advocate that the CEO assigns access to each of the 200 individual users. Not going to happen! How can you make this workable without having groups?? Would be interested on your take on this.