Hi Trevor, I just want to complete what Guillaume had said. For any documents it exists 2 authors: - the last _author_ of the document, the one that have saved any information into the document - the last _content author_ of the document, the one that have saved the _content_ of the document The first one is show in the about div at the bottom of each document, the second one is very hidden and could only be checked in an XAR export, a raw XML view of the document or using code. For some operations, like accessing the internal privileged API from velocity or running groovy scripts, the _content author_ of the document containing the (velocity) code (or the one your are looking at for groovy) should have programming rights. Currently, with the new rendering engine, the document on which the content author is checked is always the document your are looking at, not necessarily the one that directly contains the code. This should be improved later, when the new 2.0 macros received more context information. Therefore, the rights to do an operation has usually nothing to do with the programming rights of the currently connected user. AFAIK, there is almost no case where the currently connected user is check against programming rights in a standard XWiki. So most of the page of a basic XWiki does not require such rights, some does. And due to the way new wikis are setup, generally by an import procedure, there may be additional issues, regarding programming rights: - most pages has XWiki.Admin as content author at initial stage - in a farm, those having XWiki.Admin as content author in another wiki than the main one, does not have programming rights (XWIKI-4066) - importing non-backup pack does not help in fixing content authors (XWIKI-3725) So this is currently a bad idea to remove XWiki.Admin, and I generally change its password to some random one for securing that somewhat internal account. As Guillaume said, there is room for improvement: - ensure proper context for 2.0 macros (in progress I think) - ensure better support of content authors during import (XWIKI-3725, XWIKI-4066, XWIKI-4073) - allow importing backup pack (like the XWiki provided ones) as non- backup one, this would allow importing non-backup pack with another admin as content author - it could also be useful for admin to see who is the content author more easily, since there is no interface showing them Hope that this will help you understanding potential programming issues. Regards, Denis On 24 août 09, at 17:37, Guillaume Lerouge wrote: