| Project Role | Permissions |
---|
1 | ROLE_VIEWER | Any new user registration will be assigned ROLE_VIEWER. The user will not be able to view data for any project unless given permission of the project/s. Users can request access to any project with any role. Users can add a new project and the user will be project admin on added project/s.
|
2 | ROLE_PROJECT_VIEWER | Any user can be assigned ROLE_PROJECT_VIEWER on one or more projects. Users can view dashboard/s having ROLE_PROJECT_VIEWER access on the project/s but will not be able to modify any configuration, and cannot run processor User can create their own project and modify configuration, run processor, after creating a project user becomes PROJECT_ADMIN of that project and possesses all the rules of ROLE_PROJECT_ADMIN
|
3 | ROLE_PROJECT_ADMIN | Any user can be a project admin on one or more projects. User with ROLE_PROJECT_ADMIN access will be able to view the dashboard/s and will be able to edit the configuration of the project/s. Can grant/reject the access request to the project the ROLE_PROJECT_ADMIN rolled user has access. They have the permission to delete processor’s data, refer Processor Execution to delete processor’s data
|
4 | ROLE_SUPERADMIN | The user of this group will have all the permission. They can view all the configured projects and can change the configuration at the instance level including adding new projects. Only users with ROLE_SUPERADMIN will be able to approve access requests of login raised by users. Can grant/reject the access request of any project raised by users. They can see/modify the role of other users. They can change the projects access. They have the permission to delete processor’s data, refer Processor Execution to delete processor’s data
|
5 | ROLE_GUEST | |