High-Level Overview of How Granting Permissions Works

Author: Carmen Santos

Updated: October 2024

Audience: Everyone

Products Applicable: Jama Connect®

Use Case

High-Level Overview of How Granting Permissions Works

System Admins and Organization Admins may grant permissions by default. If authorized by System Admins, Project Managers may grant them as well.

*Cloud customers cannot access the Jama Software System Administration console.

Best Practice

Permission levels (granted by Org. Administrators via Admin > Permissions)

• Administrator: Access to the Admin Panel
  • It grants the ability to delegate organization permissions
    
    
  • Grants permissions to users and groups
    
    
• Manage Project: Allows the user to manage a particular project via Project > Configure Project > Configure Project.
  
  
• Project Create/Edit: Grants the ability to create and edit items within projects in the Organization
  
  
• Project Read: Grants read access to projects in the organization
  
  
• Review Center Administrator: Grants the ability to manage reviews
  
  
• Reuse Administrator: Grants the ability to create/edit/delete reuse rules

User group permissions should be set at the project level or one or two top-level components or sets. By default, all lower levels will inherit those permissions. 

You can override inherited permissions on any container: project, component, set, or folder. As groups' permissions are modified with the override, a container can be hidden from Groups or Users by not granting it Read permissions. This also means that an Organization Admin may not be an Administrator of a project where inheritance has been overridden.

We recommend keeping permissions manageable in the Project Tree since breaking inheritance too much will complicate permissions management.

To confirm if permissions are inherited from top-level containers, view the Inherited column under System Admin (root) view > Permissions or Organization Admin > Permissions. You can always remove an override under the Permission > Actions column. That will re-apply the inherited permissions.

Permissions" title="Admin Permissions" class="img-responsive" style="font-style: normal; font-variant-caps: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; box-sizing: border-box; border: 0px; vertical-align: middle; max-width: 100%; display: block; height: auto; caret-color: rgb(85, 88, 90); color: rgb(85, 88, 90); font-family: proxima-nova, Helvetica, Arial, sans-serif; font-size: 18px; font-weight: 300;"

If permissions have been granted only to that particular project's location, the inheritance is always set to FALSE, and the Remove option will clear the Group or User from that container.

Org. Administration permissions can be granted both by other Org. Administrators from the Admin Panel > Permissions > Select Org. name > Add Permissions, and by System Administrators (root user) under Jama Software System Administration view > Permissions.

Users can be assigned to one or more groups that may contain conflicting permissions. The highest available access level will be applied to the user or group in this situation.

Permissions and Licenses
The user's permissions must be aligned to the license type applied so that it works correctly.

Test Center and Releases
Permissions are required to create test plans and edit permissions for the entire project. Users with Manage Project permissions and Organization Admins can manage releases. 

Permissions and Relationships Trace 

Please feel free to leave feedback in the comments below.