Hi Gabriela, Gabriela Radu wrote: I more or less can figure out what you need. Our take was to use a space as metaphor for a what we could call a "document" (a paper, report,...) The WebHome of this space will held the table of contents and each entry in this toc will point to a different XWiki document. You can them manage the access to each of the entries on a per user basis and restrict the capability of doing changes in the WebHome to whom you want. It is of course possible to control who can read a section of a document using #if-#else-#end structures, but users that can read the document can see the used code. And users with edit rights can change it, of course. Another options could be to use any other available XWiki technique to construct the "document", #include for instance, and add some link to edit the sections each user has edit access to. Just an idea... XWiki is plenty of options to do what you are looking for... the point is to formalize it :-( There is a thread somewhere in the lists where some topic related with publishing were discussed. Somebody said that XWiki was not meant to be a complete publishing solution, just a tool to draw a draft. I am not so sure about this. Of course I have not skills enough, yet, to go ahead with such a project, but XWiki seems to me to be a perfect platform to construct the draft that will be enter any other professional publishing environment (just thinking about things like FrameMaker, Arbotek, or any FOSS alternative...). Thanks for your time, Ricardo -- Ricardo Rodríguez Your EPEC Network ICT Team