Permissions

View

1. viewReferralProgram

2. viewLedgerRecords

3. viewUserProfile

4. viewCurrency

5. viewUserRole

6. viewLiabilitiesAssests

7. viewBlockchain

8. viewMonitoring

9. viewUserDocument

10. viewUserBalance

11. viewOperation

12. viewPaymentInterface

13. viewWorkflow

14. viewTask

15. viewStaking

16. viewRole

17. viewAccountsAssets

18. viewWorkflowAudit

19. viewPermission

20. viewUser

21. viewDashboard

Edit / Create

1. editCurrency

2. editUserRole

3. editMarket

4. createCurrency

5. createMarket

6. reset2FA

7. editUserKYC

8. editStaking

9. editWorkflow

10. editRole

11. setSoftBan

12. editBlockchain

13. processOperation

14. editUserState

15. editPaymentInterface

Request

1. requestDeposit

2. requestWithdraw

Accept

1. securityAudit

2. useWorkspace

3. acceptWithdraw

4. acceptCurrency

5. acceptMarket

6. acceptReset2FA

7. acceprtSoftBan

8. acceptDeposit

Roles

...

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

...

Admin Deposit

...

1. Start node

2. Copy node
   

   Image Removed

3. Copy node
   

   Image Removed

4. Action Call node
   

   Image Removed

   A. Success → Set Fields node
   

   Image Removed

   B. Error → End node

5. Set Fields node

6. User Decision node
   

   Image Removed

   A. ‘Accept’ out port → Action Call node
   

   Image Removed

   • Success → End node

   • Error → End node

B. ‘Reject’ out port → End node

C. ‘Delete request’ node → End node
_______________________________________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.

Roles:

1. Requester Role:

   • Can initiate actions or requests.

   • Submits necessary information for the requested action.

   • Limited permissions, primarily focused on initiating requests.

2. Approver Role:

   • Reviews and approves/rejects requested actions.

   • Has broader permissions to manage approvals.

Workflow:

1. Request Initiation:

   • The Requester logs into the admin panel.

   • Navigates Navigate to the section for initiating actions or requests.

   • Fills out a request form, providing all necessary details.

   • Submits Submit the request.

2. Request Review:

   • The system logs the request and notifies the Approver role.

   • The Approver logs into the admin panel.

   • Navigates Navigate to the pending requests section.

   • Reviews Review the details of the request.

3. Approval Process:

   • The Approver has the option to approve or reject the request.

   • If approved, the system proceeds with the requested action.

   • If rejected, the system notifies the Requester with a reason for rejection.

4. Action Execution:

   • If the request is approved, the system executes the requested action.

   • This may involve database updates, changes in configurations, or other relevant operations.

5. Status Updates:

   • The system updates the status of the request to reflect whether it was approved, rejected, or is still pending.

6. Notification:

   • Both the Requester and Approver receive notifications on the status of the request.

   • Notifications may be in-app alerts, emails, or any other preferred communication method.

Additional Considerations:

• Logging and Auditing:

  • Maintain detailed logs of all actions, including who initiated requests and who approved them.

  • This helps with accountability and auditing.

• Role-Based Access Control (RBAC):

  • Ensure that permissions are well-defined for each role to prevent unauthorized access.

• User Interface:

  • Design a user-friendly interface that clearly indicates the status of requests and provides necessary information for both roles.

• Security:

  • Implement proper security measures to protect sensitive data and actions.

• Scalability:

  • Design the system to scale as the number of requests and users increaseincreases.

• Customization:

  • Allow for customization of approval workflows based on specific business needs.

Customize this basic outline according to your specific requirements, and consider involving stakeholders and end-users in the design process to ensure the workflow meets their needs effectively.

Troubleshooting

1. Common Issues and Solutions

2. Error Messages and Their Meanings

Glossary

1. Definitions of Key Terms Used in the Documentation

Appendix

1. Additional Resources

2. Contact Information for Support