Common Admin Workflow
Most admin work should follow the same pattern so records remain predictable and traceable.
Standard Flow
- Search or create the user record.
- Confirm identity, email, phone, and address.
- Assign the correct course, bundle, membership, mentorship, session, or event.
- Confirm batch number and source attribution.
- Generate or review invoice and payment schedule.
- Capture manual payment records where needed.
- Confirm final status and audit trail.
Record Actions
| Action | Use When |
|---|---|
| Save Draft | Admin needs to continue later without committing the record |
| Create | The record is ready to become active in the workflow |
| Publish | The item should be visible or usable publicly |
| Archive | The item should no longer be used but history must remain |
| Delete | Only when no business records depend on the item |
| Suspend | A student should temporarily lose access due to payment or admin decision |
| Unsuspend | Access can be restored |
UI Standards
- Use enterprise tables for records that need sorting, status, or action history.
- Use tabs for detail pages with multiple operational areas.
- Use color icon plus label for statuses.
- Use confirmation dialogs for destructive actions.
- Use toasts for success, warning, and failure feedback.
- Keep UUIDs out of user-facing tables unless no readable value exists.