Roles and Access Rights

The tool is tightly integrated with JIRA ecosystem and as a consequence users have the same user credentials as maintained by JIRA. Please note that

RMsis also defines many other roles, so as to give a more fine grained control to users on the application.
It also provides the facility to define custom roles.

Default Roles in RMsis

RMsis defines and this document assumes the following (pre-defined) default roles:

User defined in RMsis	Default Role Description
Administrator	Installs the system and manages, licenses, database backup, system upgrades etc Identifies the system users. Defines the access rights against a role. Assigns users to projects. ** Please note that Administrator has all the rights (regarding a project in RMsis) by default. However the Administrator should be assigned at least one role in JIRA configuration (ex. jira-users) for this project. These rights have to be explicitly turned off, if the Project Manager / Senior Managers want to give only a limited access to the Administrators.
Product Manager / Project Manager / Project Lead / Requirement Manager (as referred to in this document)	Owns all the requirements and artifacts mapped to the requirements. Schedules releases and assigns requirements to the same, Maintains an oversight of the product / project. Assigns the role to users. Defines the Baselines.
Team Member	Can contribute requirement(s) Reviews the requirement(s) and can comment on the same. Refers to the requirements for other downstream activities. Can view Tests and Test Runs
Analyst	Can create, update and delete requirements. Map requirements to Baselines.
Test Manager	Owns all Validation artifacts, including Tests and Test runs. Defines, composes and commits Test Runs. Manages artifacts associated with tests. Can manage references to requirements.
Testing Team Member	Can create, update and delete tests. Assign tests to test runs Can manage artifacts associated with tests. Can manage references to requirements.
Tester	Executes the tests. Can log issues against a Test Case in Test Run.
Customer	Has limited RW access, as defined by the administrator. Can contribute requirement(s)

These users can map into various designations / roles for your specific context. Some examples of this mapping are enumerated below:

User defined in RMsis	Context	Equivalent Roles
Project Manager / Project Lead	Agile (Scrum) teams	Product Owner, who is generally responsible for consolidating, analyzing and allocating requirements.
All other roles	Agile (Scrum) teams	Team Member. Scrum Master will be a part of the team and will be allocated a set of requirements (as sprint backlog) by the Product Owner.
Customer	Agile (Scrum) teams	Stakeholders.

Default Set of Permissions

Default permissions and their assignment to roles is specified at Permissions, and their assignment to Roles.