There are several ways to adjust access. The easiest way to limit editors is with the 'access-question' field in the configuration file; if you use the field,

There are several ways to adjust access. The easiest way to limit editors is with the 'access-question' field in the configuration file; if you use the field, then the "question" must be answered by anyone setting up an account. # Example: # access-question: What is the code given to you by Ms. X? # access-question-answers: RED DOG, red dog See http://github.com/jgm/gitit/blob/master/data/default.conf http://github.com/jgm/gitit/blob/master/data/default.conf Or see, e.g. http://groups.google.com/group/gitit-discuss/msg/e07fcabd70bd7495 http://groups.google.com/group/gitit-discuss/msg/e07fcabd70b... On patch-tag.com (which hosts darcs projects) the gitit wikis are set up differently, with the natural default that they are only editable by members of the project. You might sign up there with an arbitrary 'test project' so you could try out the wiki mechanism. (Many users just use it for the wiki, apparently, though I can't point to an example.) (The patch-tag gitit wikis are the only publicly accessible gitit wikis I've used regularly. I use a git-backed gitit wiki locally for everything; it's awesome because of the connection to Pandoc and the indifference between LaTeX/HTML/RTF output).