Understanding and managing roles within our system is essential for ensuring users have the appropriate permissions and access levels. Here, we'll explore the different types of roles and their purposes.

The system is already built out-of-the-box roles based on Qmarkets best practice, but every customer can add unlimited number of roles in order to support his methodologies and operation.


Pls see more specific explanation here What is the difference between System Admin, Subsystem Admin and Tenant Admin Roles
Check this article in order to better understand how the right setting can help you to increase efficiency and quality.


If you prefer to watch videos, check these that focus on the Role Management and Auto-User Assignment. It overviews the creation and assignment of user roles within the system. 




Out-of-the-Box Roles


These are the roles that come predefined in our system templates. They cannot be removed and serve fundamental functions within the system:


System Roles:

  • Sysadmin: This role has the highest level of access, responsible for overall system administration.
  • IT Sysadmin: This role is designed to configure the technical aspects of the system. See below table.
  • Campaign Creator: This role is designated for users who create and manage campaigns.
  • Employee: This role is for end-users who are employees of the company (This role is not needed for non Q-open systems).
      

You can see what the role(s) of a specific user in the user list are and of course on his/her profile page.


Click here in order to learn how to add/remove roles.


Roles Defined Per Domain:

  • Sub System Admin: Defined at the subsystem level, this role is relevant only when there is more than one subsystem.
  • Tenant Admin: Defined at the tenant level, this role is relevant only when there is more than one tenant.
  • Campaign Manager: Defined at the campaign level, responsible for managing individual campaigns.

See here what are the differences between the sysadmin, the subsystem admin and the tenant admin,


Additional Roles (Workflow):

  • Author/Co-author: Regular users who are authored/Co-authored ideas.
  • Review Committee Members: Selected per evaluation session/s of specific campaigns.
  • Roles Per Feature: These roles are defined based on specific functionalities within the system:
    •  Expert: Defined based on expertise level, experts provide specialized knowledge.
    • Task Owner: Defined at the task level, responsible for managing specific tasks. 
    • Idea Team: Users whose join requests to collaborate on ideas have been approved.


Permissions per role: 





Additional Subsystem roles:


If you wish to involve additional stakeholders in the workflow, as a sysadmin, you can add new roles as explained in this article