Mobile Push
Easily noticeable and consumable, mobile-first experience.
An approval workflow is a structured process used to manage and track the approval of tasks or actions within an organisation.
This workflow ensures that certain tasks or decisions go through predefined stages and are reviewed by designated individuals or groups before it is executed.
The "All Approval" section in Advantus provides you a comprehensive view of all requests which are pending and have been approved. From this widnow, you can easily assess the status of all your request.
flowchart TD;
A([New Request Created by Maker]) --> B([Request Submitted to Checker]);
B --> C[Notification Sent to Checker];
B --> D{{Request Review}};
D -->|Approve| E[[Execute Task]];
D -->|Reject| F[[Close Request]];
E --> G[Notification Sent to Maker];
F --> H[Notification Sent to Maker];
Point to rememeber:
Once a request is rejected by the checker, it cannot be resubmitted; it can only be viewed to understand the reason for rejection. To seek approval for the same task, the maker must create a new request.
Who is a Maker and Checker?
Maker: The user who creates or submits a request or task.
Checker: The user responsible for reviewing, approving, or rejecting the request made by the maker.
Anyone can perform the checker's role when granted the appropriate authority.
The operations for each role are outlined in the Roles and Permissions table.
The following are some use cases that can be leveraged in Advantus. However, the owner of the application can customize the approval workflow by assigning the maker and checker roles to team members.
Scenario | Description |
---|---|
Notification Campaign | Every notification campaign created by the maker is drafted and sent to the checker for review. |
User Segmentation | Whenever a new user segment is added or an existing segment is updated by the maker, it is sent to the checker for approval. |
Automated Message Workflow | The maker designs the flow and timing of the messages, while the checker verifies the accuracy of the messaging, user journey alignment, and trigger logic before approval. |
A/B Test Setup | The maker configures A/B test parameters (e.g., messages, audience split), while the checker ensures alignment with overall goals. |
Platform Configuration | Any changes made to the platform configuration by the maker are sent to the checker for review to ensure security and compliance. |
Check all pending requests submitted by users, easily review and manage them.
Review previous requests to see who approved or rejected them, and check any feedback provided.
Create and define role-based access control in your organization.