Licenses and permissions explained

Alexander Cerrato
Alexander Cerrato
  • Updated

Author: Alexander Cerrato

Date: April 25, 2024

Audience: Everyone

Environmental details: Cloud and Self Hosted customers

 

Summary: 

Licenses are some times misunderstood.

Solution:

When a user account is first created a license must be assigned. This can be one of two types: a "named" or a "float" license. It is implied that if a license is not a "float" license then it is a "named" license.
 
Examples of named license:
Creator
Stakeholder
Test Runner
Reviewer
 
Examples of float:
Creator (float)
Collaborator (float)
Reviewer (float)
 
These types do two things:
For named licenses;  It reserves a seat enabling a user account to always have access to Jama and depending which one is assigned, defines to which center(s) the account has access to view.
 
For example: if account "A" was assigned a "Creator" license, then that user account will always have that seat reserved to log in with and will have access to all centers:

In contrast, if the account "A" was assigned  a "Creator (float)"  license then that user account will have a seat or will be able to log in only if there is a "Creator (float)" license available at that time but will still be able to view all the centers as mentioned.
 
A "Reviewer" license, whether that be a "float" or not will only be able to view the "Stream" and "Reviews" centers:

The user account can be added to a user group included in a specific project which defines which projects they can view in the project explorer:


 
As for permissions at a project level, you can assign these in the admin center: (here you can also override or modify permissions to specific (sub) items or item sets inherited from the project permissions for more granular control)

Three permission options are available either for an individual user account or groups:

More details on permissions for user accounts and groups in the following link:
Grant permissions
 
The combination of the license type and permissions stated above will provide the following tasks/actions that may be performed by a certain user:
new_perm_by_license_type_table.png
More details on license type and permissions in the the link below:
Licenses and permissions

More details about permission scenarios in the link below:
Permission and scenarios 

In addition, there are predefined sets of permissions that may be granted, these are called "Rolls" More details in the link below:
Permissions granted by Rolls
 
A "Test runner" license is different in that it will always have a reserved seat for logging in and is considered a  "named" license, with predefined tasks that may be performed by a user account that holds it. More on that in the link below:
Test runner license
 
In conclusion, a user account with the correct license, the correct permissions and access to the correct project (as stated above) will be able to perform tasks listed int he above permissions table depending on your needs for that account.

Related Articles, Work orders, Zendesk tickets, Defects, etc. 

Additional Information/Metadata:

  • Permissions
  • Licenses
  • Access
  • Projects
  • Scenarios

 

Please feel free to leave feedback in the comments below.

Related to

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.