Permission | Definition |
Domain Level |
Users with this permission can view the contents of a domain |
Domain Level |
Users with this permission can view all projects within a domain. |
Domain Level |
This permission allows the user to view a StartPage in which s/he can monitor projects in which they are involved. |
Permission | Definition |
Project Level |
Users with this permission can view audit log entries. |
Domain Level |
Users with this permission have the ability to administer the domain. With this permission, users are granted access to the administrative pages. |
Domain Level |
Users with this permission can add, edit or delete licenses from the domain Only licenses with no associated projects can be deleted. |
Host Level |
Users with this permission can make use of the Administrative Utilities, can dump the cache and view and use the Task List. |
Domain Level |
This permission allows users to lock or unlock projects. |
Domain Level |
This permission allows the user to approve projects that have been proposed by other users. Additionally, users with this permission allows the user to create projects without going through the approval process |
Domain Level |
Users with this permission can view all active sessions of other users logged into the domain. |
Permission | Definition |
Project Level |
Users with this permission can view source code, the project home page, news items and other project features. This permission can be duplicated using the Project - View in conjunction with permissions for the individual project items. |
Project Level |
This permission allows users to delete a project. |
Project Level |
This permission allows users to make changes to basic project information. This includes reassigning the parent project, editing the project and the owner's message, as well as changing the project category and designating the project as private. |
Project Level |
Users with this permission can send email to invite users to join the project. |
Domain Level |
Users with this permission can suggest new projects within the domain. Suggested projects must be approved by a user with the Project - Approve permission. |
Project Level |
Users with this permission can view project lists and and view public projects on Projects and Categories page. This permission is required by many other project level permissions. |
Project Level |
This permission allows the user to view web pages associated with the resource to which it has been granted. Example: A user with this role granted to a project with the ".*" resource can view all pages within the domain. A user with this role granted on a project with access to the "/project/.*" resource can only see pages belonging to the project project. This permission requires a resource. |
Project Level |
This permission allows users to view a list of users with roles in a project. |
Permission | Definition |
Project Level |
Users with this permission can create forums within this project. |
Project Forum - Delete Project Level |
Users with this permission can delete forums within this project. |
Project Forum - Edit Project Level |
Users with this permission can edit forums within this project. |
Project Forum - Post Project Level |
Users with this permission can post messages to forums within this project. |
Project Forum - Subscribe Project Level |
Users with this permission can subscribe to forums within this project |
Project Forum - Unsubscribe Others Project Level |
Users with this permission can unsubscribe others from forums within this project. |
Project Forum - View Project Level |
Users with this permission can view forums within this project. |
Permissions granted for project issue tracking determine the level of access set within IssueZilla for that project.
NOTE: users must have a role within the project to which they need access to IssueZilla.
NOTE: Domains with single-database mode for issue tracking do not use these permissions after the user is initially created. The administrator must set permissions within the IssueZilla interface for user access levels to be affective.
Permission | Definition |
Project Level |
Users with this permission can view and approve suggested News items within the project to which the permission has been granted. Users with this permission can create news items without going through the approval process. |
Project Level |
This permission allows users to delete any news item within the project. |
Project Level |
This permission allows users to edit news items within the project |
Project Level |
Users with this permission can suggest news items within the project. Suggested news items must be approved by a user with the Project News - Approve permission. |
Project Level |
Users with this permission can view news items within the project. |
Permission | Definition |
Project Level |
Users with this permission can add new resources to the project. |
Project Level |
Users with this permission can edit resources within the system. Users can edit the regular expression (eg; ".*") and the description of the resource. |
Permission | Definition |
Domain Level |
Users with this permission can create new users within the domain. |
Domain Level |
Users with this permission can delete any user within the domain. |
Domain Level |
Users with this permission can edit user preferences for any user within the domain. |
Domain Level |
Users with this permission in the domain in which they are registered can edit their own user information. For a user to edit his or her organization with this permission the "userEditSelfAllowsEditOrg" must be set. |
Domain Level |
Users with this permission can view a list of all users registered and the details of any user in the domain. |
Domain Level |
Users with this permission can view information on any user registered in the domain. |
Domain Level |
This permission allows users to view their own user profile. |
Permission | Definition |
Domain Level |
Users with this permission can create new user groups within the domain. |
Domain Level |
Users with this permission can delete any user group in the domain. |
Domain Level |
Users with this permission can edit any user group within the domain |
Domain Level |
Users with this permission can add users to any usergroup in the domain. |
Domain Level |
Users with this permission can delete any user from any user group within the domain. |
Domain Level |
Users with this permission can view any user group within the domain. |
Domain Level |
Users with this permission can view the details of any user group within the domain. |
These permissions require a resource. Users with these permissions can apply them to any file within the project with a pattern matching the resource. For example, a user with the VersionControl - Commit permission on the "*.txt" resource in the project project can change any existing file with an extension of .txt in the project project repository.
Permission | Definition |
Project Level |
This permission gives the user cvs add privileges. The add privilege allows users to add a file to a directory in a repository. After the user adds the file, the file must be "committed" to the repository. |
Project Level |
This permission allows use of the cvs admin command. The cvs admin command should be reserved for users who have extensive knowledge of CVS and administering CVS |
Project Level |
This permission gives the user cvs annotate privileges. The annotate command provides a line by line description a file in the "head" and all changes made to that file, including version number, user and date. |
Project Level |
This permission gives the user cvs commit privileges. The commit command is used to incorporate changes from the working directory into the repository. |
VersionControl - Edit
Project Level |
Users with this permission can use the cvs edit command. The cvs edit command allows users to make edits to locked files. |
Project Level |
This permission gives the user cvs diff privileges. The diff command is used to compare different versions of a file. |
Project Level |
This permission gives the user access to the CVS history file. The history file tracks each use of the commit, checkout, rtag, update and release commands. |
Project Level |
This permission gives the user the right to import into the CVS source repository. The import command incorporates an entire external source base into the source repository. |
Project Level |
This permission gives the user cvs log privileges. cvs log displays a log of all activity of the files requested. The log includes author, date, version and notes provided for each entry. |
VersionControl - Module
Project Level |
Users with this permission can checkout modules to the standard output and/or request a status of all files checked out in the module. |
VersionControl - Release
Project Level |
This permission gives the user cvs release privileges. The cvs release command checks to make sure no changes have been made to files checked out using cvs checkout before deleting them in a local directory. |
Project Level |
This permission gives the user cvs remove privileges. The cvs remove command marks files for removal at a later date. To complete the removal process, the cvs commit command must also be used. |
Project Level |
This permission gives the user the ability to tag a version of the source files in the CVS repository. Tagging a version allows development in that tag to proceed without touching the HEAD. |
Project Level |
This permission gives the user the cvs co and cvs update privileges. The cvs co, meaning checkout, command allows the user to copy the source from the repository to a local directory. CVS tracks changes made in the local directory and allows the user to commit changes to the repository using the cvs commit command. The cvs update command allows the user to update the local copy from the repository and to commit changes to the repository using the cvs commit command. |
VersionControl - Watch
Project Level |
This permission gives the user the cvs watch privileges. Once the cvs watch command has been applied to a file, updates to the file must be made using cvs edit. Using cvs watch effectively marks a file as read-only except to those users who have cvs edit privileges. |