Access Control Overview
What is Access Control?
Access Control is your security and governance command center where you define who can do what in the system and how transactions get authorized. Configure role-based permissions to control feature access and design multi-level approval workflows to ensure proper authorization before critical business actions are executed.
Who Uses This?
System Administrators
Configure permissions and workflows across the entire organization
Business Owners
Establish governance policies and approval authority limits
Finance Heads
Set financial controls and multi-level authorization thresholds
Department Heads
Define department-specific access and approval chains
Core Components
Access Control consists of two integrated modules that work together to secure your business operations:
1. Role Permissions
What Users Can Access and Do
Control which features, modules, and actions each role can access across the platform.
Key Capabilities:
Module-Level Access
- Grant or restrict access to entire modules (Purchase, Sales, Finance, Inventory)
- Control visibility of sensitive business areas
- Separate operational access from financial access
Feature-Level Permissions
- Define specific actions within modules (Create, Edit, View, Delete)
- Control document operations (approve, cancel, clone)
- Manage export and print capabilities
Department-Based Roles
- Three-level hierarchy per department: L1, L2, L3
- L1: Entry-level staff and executives
- L2: Managers and supervisors
- L3: Department heads and directors
Data Access Control
- Own data only vs. department-wide vs. organization-wide
- Cross-department visibility controls
- Business unit specific permissions
How It Works:
When a user logs in, the system checks their assigned role(s) and applies the configured permissions. Users see only the menus, features, and data they're authorized to access. Unauthorized actions are blocked at the system level, ensuring data security and compliance.
Common Use Cases:
| Role | Typical Permissions | Restrictions |
|---|---|---|
| L1-Purchase | Create purchase requests, view suppliers, check inventory | Cannot create POs, cannot see pricing, no approval rights |
| L2-Sales | Create quotations and sales orders, manage customers, view inventory | Cannot see purchase data, cannot approve own transactions |
| L3-Finance | All finance operations, GST filing, view all transactions, reports | View-only on operations, cannot modify non-finance documents |
| L1-Admin | Full system access, user management, all configurations | None - highest authority level |
2. Approval Workflows
How Transactions Get Authorized
Design multi-level approval chains based on transaction value and department to ensure proper authorization before execution.
Key Capabilities:
Value-Based Routing
- Different approval levels for different transaction amounts
- Example: Up to ₹50K auto-approved, ₹50K-₹5L needs manager, above ₹5L needs director
- Unlimited value brackets to match your authorization matrix
Department-Specific Workflows
- Each department can have its own approval rules
- Purchase dept follows different chain than Sales dept
- Allows decentralized control while maintaining governance
Multi-Level Sequential Approvals
- Single approver for simple authorization
- Two-level: Manager → Department Head
- Three-level: Executive → Manager → Director
- Higher levels for higher risk transactions
Workflow Types Available
Transaction Approvals (Value-Based):
- Purchase Orders
- Sales Orders
- Purchase Requests
- Bills and Payments
- Goods Receipt Notes
- Returns and Expenses
Master Data Approvals (Department-Based):
- New Item creation
- New Supplier creation
- Bill of Material updates
How It Works:
When a user creates a document, the system checks the transaction amount and user's department. It matches these to the configured workflow rules and automatically routes the request to the appropriate approver. Approvers receive notifications in their Approvals inbox. The document proceeds only after all required approvals are obtained, creating a complete audit trail.
Real-World Example:
Purchase Order Workflow - Purchase Department
Bracket 1: ₹0 - ₹25,000
- No approval required
- Auto-approved for routine low-value purchases
- Speeds up operations
Bracket 2: ₹25,001 - ₹200,000
- Routes to L2-Purchase (Purchase Manager)
- Single-level approval
- Turnaround: 4-8 hours
Bracket 3: ₹200,001 - ₹1,000,000
- Routes to L2-Purchase → L3-Finance
- Two-level approval for budget verification
- Turnaround: 1-2 days
Bracket 4: Above ₹1,000,001
- Routes to L2-Purchase → L3-Finance → L3-Admin
- Three-level approval for high-value commitments
- Final authority review required
- Turnaround: 2-3 days
Result: Proper oversight without micromanagement. Fast approvals for routine work, careful review for significant commitments.
How They Work Together
Integrated Security Model
Step 1: Role Permissions Control Access
- User logs in → System loads their role permissions
- User can only access modules and features they're authorized for
- Cannot even see unauthorized menus or data
Step 2: User Creates Transaction
- Within permitted areas, user creates document (PO, SO, Bill, etc.)
- Enters details, adds items, attaches files
- Clicks Submit
Step 3: Approval Workflow Activates
- System checks transaction type, amount, and user's department
- Matches to configured approval workflow
- Routes to appropriate approver(s) based on rules
Step 4: Approver Reviews
- Approver sees request in their Approvals inbox (if they have permission)
- Reviews details, adds comments
- Approves or rejects
Step 5: Document Proceeds
- After all approvals obtained, document becomes active
- Can now be processed further (PO sent to vendor, SO becomes invoice, etc.)
- Complete audit trail maintained
Example:
Purchase Executive (L1-Purchase role):
- Role Permissions: Can create purchase requests and view suppliers
- Creates: Purchase request for ₹80,000
- Approval Workflow: Routes to L2-Purchase for approval
- After Approval: Executive cannot create PO (no permission), so L2-Purchase creates the PO
- PO Workflow: ₹80K PO routes to L2-Purchase for approval automatically
Key Benefits
For Organizations
Governance & Compliance
- Enforced authorization controls prevent unauthorized commitments
- Separation of duties built into system design
- Complete audit trail for regulatory compliance
- Reduced fraud risk through multi-level reviews
Operational Efficiency
- Clear approval paths eliminate confusion and delays
- Automated routing ensures no requests get lost
- Value-based thresholds balance control with speed
- Mobile approvals keep workflows moving
Flexibility & Scalability
- Department-specific rules accommodate diverse needs
- Easy to modify as business grows or changes
- Support for complex multi-entity structures
- No programming required for configuration
For Administrators
Centralized Control
- Single place to manage all access and approvals
- Visual configuration - no coding needed
- Changes take effect immediately
- Bulk role assignments for efficiency
Clear Visibility
- See who has what permissions across organization
- Understand approval flows at a glance
- Track pending approvals and bottlenecks
- Audit trail of all configuration changes
For Business Users
Clarity & Confidence
- Know exactly what you can do in the system
- Clear approval status on all documents
- Notifications when action required
- No guessing about authorization levels
Faster Approvals
- Requests automatically route to right person
- Approvers get complete information for quick decisions
- Mobile-friendly for approval on the go
- No manual follow-up needed
Getting Started with Access Control
Step 1: Understand Your Structure
Before configuring access control:
Document Your Organization
- List all departments (Finance, Purchase, Sales, Operations, etc.)
- Define reporting hierarchy within each department
- Identify who should approve what
Define Authorization Matrix
- What values need approval in each workflow?
- Who should be first approver, second, final?
- Which departments need different rules?
Map User Roles
- Which users belong to which departments?
- What level of authority (L1, L2, L3)?
- Any users with multiple roles?
Step 2: Configure Role Permissions
Priority: Set up access first
- Go to Access Control > Role Permissions
- Review default permission templates
- Customize for each role based on job function
- Start conservative, expand as needed
- Test with sample users before full rollout
Time Required: 2-3 hours for initial setup
Guide: Role Permissions Setup →
Step 3: Design Approval Workflows
After permissions configured:
- Go to Access Control > Approval Workflows
- Start with most critical workflows (Purchase Orders, Bills)
- Configure value brackets and approval chains
- Add additional workflows as needed
- Test with sample transactions
Time Required: 1-2 hours per workflow type
Guide: Approval Workflows Setup →
Step 4: Assign Users
Final step:
- Go to Subscription > Manage Users
- Assign each user to appropriate department role(s)
- Verify users see correct menus and data
- Test approval routing with real scenarios
Time Required: 30 minutes for 10-20 users
Common Scenarios
Scenario 1: Small Business (5-10 Users)
Simple Setup:
Departments:
- Admin (Owner, Office Manager)
- Operations (Everyone else)
Role Permissions:
- L3-Admin: Full access to everything
- L2-Admin: Most features except critical settings
- L1-Operations: Create transactions, view data
Approval Workflows:
- POs up to ₹50K: Auto-approved
- POs above ₹50K: L3-Admin approval
- Sales orders: No approval needed
Setup Time: 1-2 hours total
Scenario 2: Growing Business (20-50 Users)
Structured Setup:
Departments:
- Admin, Finance, Purchase, Sales, Operations
Role Permissions:
- Each department has specific module access
- L3 roles: Full department authority
- L2 roles: Manager-level access
- L1 roles: Operational access only
Approval Workflows:
- Multiple value brackets per workflow
- Department-specific approval chains
- Cross-department approvals for high values
- Finance approval on all payments
Setup Time: 4-6 hours total
Scenario 3: Multi-Location Enterprise (50+ Users)
Complex Setup:
Departments:
- 8-10 functional departments
- Same structure across all locations
- Centralized Finance, decentralized Operations
Role Permissions:
- Business unit specific permissions
- Cross-location visibility for management
- Strict data segregation for regular users
Approval Workflows:
- Location-specific workflows
- Escalation to central management for high values
- Department-specific chains with finance oversight
- Multi-level approvals (3-4 levels) for critical transactions
Setup Time: 8-12 hours for comprehensive configuration
Best Practices
Permission Management
Start Restrictive, Then Expand
- Begin with minimal permissions
- Add access as users prove need
- Easier to grant than revoke access
Review Quarterly
- Check if permissions still appropriate
- Remove access for departed employees
- Update for role changes
Document Everything
- Maintain permission matrix outside system
- Note rationale for special access grants
- Support audit and compliance reviews
Workflow Design
Balance Control with Speed
- Don't require approval for everything
- Use "no approval" for routine low-risk transactions
- Reserve multi-level for truly critical decisions
Keep Chains Short
- Maximum 3 approval levels recommended
- Each level adds 4-24 hours of delay
- More levels = more bottlenecks
Plan for Absences
- Assign multiple users to critical roles
- Consider delegation features
- Document escalation procedures
Testing & Rollout
Test Before Go-Live
- Create test users for each role
- Verify permissions work as expected
- Test approval routing with sample transactions
- Fix issues before training users
Phased Rollout
- Start with one department or workflow
- Learn and adjust based on feedback
- Gradually expand to full organization
Train Users
- Explain what they can and cannot do
- Show how to check approval status
- Provide quick reference guides
Related Sections
- Organization - Set up departments and structure
- Manage Users - Assign users to roles
- Approvals - User view of pending approvals
- Audit Logs - Track all system activities
Quick Tips
Best Practices
Configure Role Permissions before Approval Workflows - users need access before they can approve
Start with simple workflows and add complexity only when business needs justify the overhead
Document your approval matrix outside the system for quick reference and audit purposes
Review access controls quarterly to ensure they still match your organizational structure and policies
Need help? Contact support at support@bizconnekt.com