Granular Permissions System


"Granular permissions" simply means that you have control over who does what and what they are allowed to do respective to every single folder and file on the system and more importantly who is not allowed to do what.

System administrators can control not only what each user can do with an asset but what they can do to it. For instance, the copyeditor should be the only one who can update files in the "Copyedited Files" folder. The Typesetter will need to download those files but he will not be allowed to affect them so protecting their integrity. 1st Proofs should only be uploaded by the Typesetter but Proofreaders, Authors and possibly Indexers will need to be able to download them. Permissions are totally granular in as much as each individual user can be totally controlled in what they can see and what they can do down to individual file level. You could set up a permission that allows a user to see only a single file on the entire system.

Example: Say you had a 1000 page contributed title with 150+ chapters and 250+ authors. Every chapter of 1st Proofs can be seen in their entirety by everyone who should see them all but individual Authors would only be able to see the individual files for which they have responsibility.

A simple guide we have developed is as follows:

Copyeditors only need to see the original MS and be able to upload into the Copyedited Files directory
Authors need access only to Marked Proofs and maybe Copyedited Files if a review is required
Proofreaders need access only to Copyedited files but need to be able to upload into their Marked files folder
Typesetters need access only to Art files and Copyedited Files but they must be able to upload into 1st proofs, 1st Revises etc
Indexers need access only to Marked Proofs but must be able to upload into the Index folder . . .
. . . and so it goes on.

All of the above is of course customisable depending on each clients preferences or to suit the individual job.

Example directory Structure