10 thoughts on “So many choices – what's the best way to invite your users?

  1. I am so happy to have the new classroom accounts. I have several people that I just want to give a username and password to. This makes it so much easier.

  2. The “Coming Soon — Public editing” surprisedme. It is funny that you go from one extreme of requiring lots of hoops to be able to edit to adding open access. I think the option of open access is great, but I would also like one step back. I like the version 1 senerio of setting a wiki password, so anyone with that password can edit.

  3. I like the “anyone can edit” option. I think that there are definitely perils involved though — and so better management tools for wiki admins are needed… in order to make it easier to undo a single user’s edits across many pages… It should also be mandatory to create an account (which, with OpenID, is much easier) so that it’s easier to ban offenders.

    A better “activity stream” style view of edits would also be useful — especially combining multiple people’s edits of a single page into a single activity.

    Finally, making permissions cascade based on folder hierarchies would be useful too… perhaps each user would get their own Sandbox to try things out in… and perhaps it would be useful to create, in the case of the BarCamp wiki, a folder called “Events” which would be an “anyone can edit pages in this folder” folder… but top level pages would require elevated permissions…


  4. Really happy to see the “Coming Soon — Public editing” – this kind of functionality has been missing since PBWiki 1.0 invite keys, and it will be great to have something similar.

    “What more could you ask for?”

    1. Easy: Please edit the templates to add the ACCESSKEY support back that was in PBWiki 1.0 (E = Edit, P = Preview, S = Save, C = Cancel)

    2. Harder: Please ensure full fidelity roundtripping of any/all HTML elements and attributes that are not manipulated by the WYSIWYG editing tools (e.g. “class” attributes on all elements, “rel” on hyperlinks, etc.)



  5. Please bring back the 1.0 feature of just being able to assign an invite key with the ability to assign access levels. When dealing with multible teachers that may or may not be known to you, this is a great feature.

  6. I am looking forward to the public access feature.

    It would make creating a page or a wiki so much easier…Classroom accounts are great for young kids, but University students want more freedom and feel better signing in themselves..
    so do adults who are students


  7. Public editing for more mature participants is fine, but last year I had an experience with smut being liberally applied to a site for a New Testament class. This leaves me a firm believer in a hierarchy of permissions. So let us be able to keep a firm hand on who can edit, please.

    Could we have an Edit button/tab at the bottom of the page as well as the top? This would be a time-saver, for sure.

    Last but not least, could we have some way of uploading significant numbers of photos to our wiki pages. One of my wikis is an archaeology site for work between colleagues in the US, Europe, and Israel, and this would be most valuable. There are files totaling about 3,000 photos which I would like others to have access to and at present cannot.

  8. Hi there,

    It sounds like the request access feature is best for your public wiki. With request access you must approve every user who wants to gain access to your wiki.

    If you want tight control over the users on your wiki, turn off ‘request access’ and make sure to invite your users by email.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: