Event Management Company Accounting App Development
Budget: ₹11,000 – ₹25,000 INR
USER ROLES, AUTHORITY & DATA SECURITY MODEL
(Event Management Accounting App)
Core Objective of App
Accounting accuracy
Data security
Zero data leakage between managers
Full control with Super Admin
---
USER ROLES OVERVIEW
Role Count Data Access
Super Admin 1 (or very limited) Full database control
Admin Multiple Read + manage operations
Event Manager Multiple Only their own data
---
SUPER ADMIN (Highest Authority)
Core Powers
Super Admin is not involved in daily operations.
Super Admin CAN:
Create / Block / Delete:
Admins
Event Managers
Freeze or Disable App Access for any user
Full Database Control:
Backup
Restore
Export full database
Control:
Bank accounts list
GST rules
Payment modes
View ALL data (read-only preferred
Security Controls:
Mandatory:
2-Factor Authentication
Device binding
IP logging
All actions logged:
Who blocked whom
When data was exported
---
3️⃣ ADMIN ROLE (Operational Authority)
Admin CAN:
Create & manage:
Event Managers
Leads
Events
Assign leads to Event Managers
View ALL events & accounting data
Download:
Reports
Invoices
Ledgers
Approve:
Final billing
GST invoices
View all bank account inflows (read-only)
Admin CANNOT:
Delete confirmed accounting entries
Access Super Admin controls
Change GST rules
Delete bank accounts
Admin Access Type:
Read + Controlled Write
No database-level permissions
---
EVENT MANAGER ROLE (Restricted Access)
Event Manager CAN:
View ONLY their assigned clients
Add:
Follow-ups
Event notes
Service details
Upload:
Client confirmations
Bills
See:
Payments related ONLY to their events
Pending balances for their clients
Event Manager CANNOT:
View:
Other managers’ clients
Bank account details (only account nickname)
Profit margins
Download bulk data
Delete payments
Edit GST values
Data Isolation Rule:
> Event Manager sees only rows linked to their User ID
---
DATA SECURITY ARCHITECTURE (VERY IMPORTANT)
Data Segmentation
Every record stores:
Created_By_User_ID
Assigned_Manager_ID
Client_Code
This ensures:
Automatic filtering at database level
No accidental data exposure
---
ACCOUNTING & PAYMENT SECURITY
Payment Entry Rules:
Event Manager:
Can request payment entry
Admin:
Must approve payment entry
Super Admin:
Audit-only access
Bank Accounts:
Actual account numbers:
Visible ONLY to Super Admin
Admin & Event Manager:
See alias names only
Example: “HDFC-01”, “ICICI-GST”
---
DOWNLOAD & EXPORT CONTROL
Download Permissions:
Role Download Data
Super Admin Full DB
Admin Reports only
Event Manager Their own event PDFs
Export Protection:
Watermark with:
User Name
Date & Time
Logs stored permanently
---
AUDIT LOG & TRACEABILITY
Every action logged:
Login / Logout
Data viewed
Payment added
Payment edited
User blocked
Logs are:
Read-only
Only Super Admin can view
---
9️⃣ APP ACCESS CONTROL (BLOCKING SYSTEM)
Super Admin Can:
Temporarily block:
Admin
Event Manager
Permanently disable account
Force logout from all devices
Block Scenarios:
Data misuse
Employee exit
Suspicious activity
---
EXTRA SECURITY FEATURES (Recommended)
End-to-end encryption
No screenshots allowed (Android flag)
Auto logout after inactivity
Night-time access restriction (optional)
Cloud + local encrypted backup
---
AI ROLE IN SECURITY
Detect unusual login locations
Detect abnormal data downloads
Alert Super Admin on suspicious activity
Predict fraud patterns
---
FINAL SUMMARY (For Developer)
> This app follows Role-Based Access Control (RBAC) with strict accounting-grade security, where:
Super Admin controls people + database
Admin controls operations
Event Manager controls only their work
Accounting data is immutable, auditable & encrypted
(Event Management Accounting App)
Core Objective of App
Accounting accuracy
Data security
Zero data leakage between managers
Full control with Super Admin
---
USER ROLES OVERVIEW
Role Count Data Access
Super Admin 1 (or very limited) Full database control
Admin Multiple Read + manage operations
Event Manager Multiple Only their own data
---
SUPER ADMIN (Highest Authority)
Core Powers
Super Admin is not involved in daily operations.
Super Admin CAN:
Create / Block / Delete:
Admins
Event Managers
Freeze or Disable App Access for any user
Full Database Control:
Backup
Restore
Export full database
Control:
Bank accounts list
GST rules
Payment modes
View ALL data (read-only preferred
Security Controls:
Mandatory:
2-Factor Authentication
Device binding
IP logging
All actions logged:
Who blocked whom
When data was exported
---
3️⃣ ADMIN ROLE (Operational Authority)
Admin CAN:
Create & manage:
Event Managers
Leads
Events
Assign leads to Event Managers
View ALL events & accounting data
Download:
Reports
Invoices
Ledgers
Approve:
Final billing
GST invoices
View all bank account inflows (read-only)
Admin CANNOT:
Delete confirmed accounting entries
Access Super Admin controls
Change GST rules
Delete bank accounts
Admin Access Type:
Read + Controlled Write
No database-level permissions
---
EVENT MANAGER ROLE (Restricted Access)
Event Manager CAN:
View ONLY their assigned clients
Add:
Follow-ups
Event notes
Service details
Upload:
Client confirmations
Bills
See:
Payments related ONLY to their events
Pending balances for their clients
Event Manager CANNOT:
View:
Other managers’ clients
Bank account details (only account nickname)
Profit margins
Download bulk data
Delete payments
Edit GST values
Data Isolation Rule:
> Event Manager sees only rows linked to their User ID
---
DATA SECURITY ARCHITECTURE (VERY IMPORTANT)
Data Segmentation
Every record stores:
Created_By_User_ID
Assigned_Manager_ID
Client_Code
This ensures:
Automatic filtering at database level
No accidental data exposure
---
ACCOUNTING & PAYMENT SECURITY
Payment Entry Rules:
Event Manager:
Can request payment entry
Admin:
Must approve payment entry
Super Admin:
Audit-only access
Bank Accounts:
Actual account numbers:
Visible ONLY to Super Admin
Admin & Event Manager:
See alias names only
Example: “HDFC-01”, “ICICI-GST”
---
DOWNLOAD & EXPORT CONTROL
Download Permissions:
Role Download Data
Super Admin Full DB
Admin Reports only
Event Manager Their own event PDFs
Export Protection:
Watermark with:
User Name
Date & Time
Logs stored permanently
---
AUDIT LOG & TRACEABILITY
Every action logged:
Login / Logout
Data viewed
Payment added
Payment edited
User blocked
Logs are:
Read-only
Only Super Admin can view
---
9️⃣ APP ACCESS CONTROL (BLOCKING SYSTEM)
Super Admin Can:
Temporarily block:
Admin
Event Manager
Permanently disable account
Force logout from all devices
Block Scenarios:
Data misuse
Employee exit
Suspicious activity
---
EXTRA SECURITY FEATURES (Recommended)
End-to-end encryption
No screenshots allowed (Android flag)
Auto logout after inactivity
Night-time access restriction (optional)
Cloud + local encrypted backup
---
AI ROLE IN SECURITY
Detect unusual login locations
Detect abnormal data downloads
Alert Super Admin on suspicious activity
Predict fraud patterns
---
FINAL SUMMARY (For Developer)
> This app follows Role-Based Access Control (RBAC) with strict accounting-grade security, where:
Super Admin controls people + database
Admin controls operations
Event Manager controls only their work
Accounting data is immutable, auditable & encrypted