Project Journey: Zaqms_ajz — Dynamic Task Management & RBAC Architecture
1. The Essentials
- Project Name: Zaqms_ajz Task Automation
- Client/Organization: Casper D (Zaqms ajz)
- Your Role: Lead App Architect & Automation Developer
- Duration: November 2022 – December 2022 (Initial Build & Scaling)
- Project Type: Operational Task Logging & Departmental Approval System
2. The "Why" (The Problem)
- What was the challenge? The client needed a system that could handle task logging across different departments with strict privacy and approval hierarchies. The existing workflow lacked accountability—there was no clear way to verify that a task logged by a user was actually reviewed and approved by the correct supervisor.
- What was at stake? Without a structured approval process, departmental task data was unreliable. Furthermore, different activities required different levels of evidence (some needed photos, some just comments), and a "one-size-fits-all" form was causing data fatigue for the users.
3. The "How" (The Action)
- What was the solution? We built a high-granularity task management app in AppSheet featuring a custom-coded Role-Based Access Control (RBAC) system and conditional form logic.
- Key Tech/Skills Used: AppSheet, RBAC Logic, Conditional Branching, UX Design, Departmental Data Partitioning.
- Your Specific Contribution:
- Triple-Tier RBAC Implementation: Engineered a robust user role system:
- Admin: Full oversight of users, roles, and master activity/department lists.
- Staff: A departmental "Gatekeeper" role that can only see and approve tasks within their assigned domain.
- User: A streamlined interface for logging tasks based on filtered departmental activities.
- Dynamic Activity Configuration: Developed a feature that allows Admins to "Activate" or "Deactivate" form fields (Comments, Photos, Staff Names) on a per-activity basis.
- Departmental Mapping: Built the logic to assign specific users to specific departments via the Admin portal, ensuring that data silos are maintained for security and clarity.
4. The "So What?" (The Results)
- Quantifiable Success: * Successfully transitioned the app from a prototype to a "Final Touch-up" state within a 2.5-hour engineering window.
- Reduced form completion time for users by hiding unnecessary fields through activity-wise dynamic logic.
- Qualitative Success: The client gained a professional-grade management tool that handles departmental oversight automatically. The "Staff Approval" feature ensured that task logging became a verified process rather than just a data entry task.
5. LinkedIn "Hook" Potential
Don't build an app; build a Hierarchy.
In late 2022, I worked with Zaqms_ajz to solve a common business problem: Data Chaos across departments. We didn't just give them a form; we gave them a Permission Engine.
The Innovation: By building a "Dynamic Activity Configurator," we allowed the Admin to decide exactly what evidence is needed for each task. Need a photo for a "Maintenance" task but just a comment for "Safety Check"? One click in the Admin settings changes the entire user experience.
The Lesson: The best way to increase user adoption is to make the app smarter, not more complex. When you only show a user what they need to see, efficiency skyrockets.
Authored by: [OmmNoMi AutomationLLP] Project Code: 1005 (Zaqms_ajz)