...
Admin View - The Admin role in this system has limited permissions, focused on viewing information across all pages and details. This role enables users to access the admin panel but restricts them from initiating or approving actions. The primary function is to observe and gather insights, maintaining a comprehensive view of the system's data and activities.
Permissions for Admin View role:
Support - The Admin role with support permissions has exclusive access to requesting actions within the admin panel but lacks configuration capabilities. This user can submit requests, seeking assistance or changes, but is restricted from modifying system configurations. This focused role ensures streamlined support functionalities without compromising system integrity.
Permissions for Support role:
Business Analyst - The Admin role with Business Analyst permissions has broad access, viewing all pages and details. While equipped with configuration permissions, the role is limited to initiating requests rather than making direct changes. This ensures a comprehensive understanding of the system while maintaining controlled adjustments through the request-based workflow.
Permissions for Business Analyst role:
DevOps - The Admin role with DevOps permissions is specialized, allowing access solely to the DevOps page. This focused view empowers the user to oversee and manage specific aspects related to development and operations, streamlining their responsibilities within a targeted scope
Permissions for DevOps role:
Finance Controller -The Admin role with Finance Controller permissions enjoys comprehensive access to all pages, facilitating a thorough overview. With the authority to approve configuration requests, as well as deposit and withdrawal operations, this role plays a crucial role in financial management, ensuring control over critical actions within the system.
Permissions for Finance Controller role:
Super Admin - The Admin role with all available permissions is a central and powerful entity within the system. With access to all pages, this administrator can comprehensively oversee the entire platform. They possess the authority to make configurations without requiring approval, enabling swift adjustments. The ability to execute deposit and withdrawal operations without external validation streamlines financial processes. Furthermore, this Admin can manage user privileges by editing and adding other privileged users, fostering user management flexibility. The capability to edit permissions for privileged users ensures a tailored access control mechanism. Additionally, the administrator can view, edit, and create workflows, contributing to a dynamic and adaptable system. This broad spectrum of permissions grants the Admin unparalleled control, emphasizing their pivotal role in managing and shaping the platform's functionalities.
Workflow nodes
Admin Deposit
Approve_Deposit_Test_Bank_PINew Workflow:
...
Edit name for Workflow
Workflow JSON : …..
Select ‘Workflow Initial Component’ : ….
+ Add param
- Key:
- Data type:'Enabled' toggle
1. userDecision [Flexible user decision]
...
Component:
Assignee User:
Assignee Role:
Assignee Permission:
Params Key:
Out port N:
- Name:
- Primary:
- Danger:+Add Out Port:
In:
Out Port:
actionCall [Call any action of any service]
...
Action:
Params Key:
Result Key:
In:
Success:
Error:
checkPermissions [Check permissions]
...
Params Key:
Permissions:
In:
True:
False:
checkRoles [Check roles]
...
Params Key:
Roles:
In:
True:
False:
copy [Copy data]
...
From:
To:
+Add Copy action:
In:
Out:
delete [Delete values]
...
Delete Item:
Add Delete action:
In:
Out:
if [If condition]
...
Condition:
In:
True:
False:
set [Set values]
...
Key:
Type:
Value:
Add Set action:
In:
Out:
startNode [Starting point of any workflow]
Out:
endNode [End point of workflow]
In:
Workflows
Admin Deposit
Conditions for nodes:
Conditions for permissions:
Requester Role: requestDeposit
Approver Role: acceptDeposit
...
Start node
Copy node
Copy node
Action Call node
A. Success → Set Fields node
B. Error → End node
Set Fields node
User Decision node
A. ‘Accept’ out port → Action Call node
Success → End node
Error → End node
B. ‘Reject’ out port → End node
C. ‘Delete request’ node → End nodeAudit logs:
Admin Withdraw
Conditions for nodes:Conditions for permissions:
Requester Role:
Approver Role:Audit logs:
Turn off user 2 FA
Conditions for nodes:Conditions for permissions:
Requester Role:
Approver Role:Audit logs:
User soft ban
Conditions for nodes:Conditions for permissions:
Requester Role:
Approver Role:Audit logs:
Create / Update Currency
Conditions for nodes:Conditions for permissions:
Requester Role:
Approver Role:Audit logs:
Create / Update Market
Conditions for nodes:Conditions for permissions:
Requester Role:
Approver Role:Audit logs:
User KYC
Conditions for nodes:Conditions for permissions:
Requester Role:
Approver Role:Audit logs:
Operations with error / Cancel order
Conditions for nodes:Conditions for permissions:
Requester Role:
Approver Role:Audit logs:
Create / Update referrals groups
Conditions for nodes:Conditions for permissions:
Requester Role:
Approver Role:Audit logs:
Blockchains configuration
Conditions for nodes:Conditions for permissions:
Requester Role:
Approver Role:Audit logs:
Create / Update Workflow
Conditions for nodes:Conditions for permissions:
Requester Role:
Approver Role:Audit logs:
Create / Update Manual rates
Conditions for nodes:Conditions for permissions:
Requester Role:
Approver Role:Audit logs:
Create / Update roles
Conditions for nodes:Conditions for permissions:
Requester Role:
Approver Role:Audit logs:
Create / Update Privileged Users
Conditions for nodes:Conditions for permissions:
Requester Role:
Approver Role:Audit logs:
Soft ban / Soft unban all users
Conditions for nodes:Conditions for permissions:
Requester Role:
Approver Role:Audit logs:
_______________________________________
Creating a workflow for an admin panel with distinct roles for requesting and approving actions involves defining a series of steps and permissions. Below is a basic outline of the workflow, along with the roles and their respective responsibilities. Keep in mind that the actual implementation may vary depending on your specific requirements and the technology stack you are using.
...