Departments Overview
What are Departments?
Departments are functional divisions within your organization that help structure teams, control access, and manage approval workflows. Each department comes with three predefined roles (L1, L2, L3) that enable hierarchical approvals and role-based access control across the platform.
Who Uses This?
Business Owners
Structure the organization by functional divisions
Tenant Administrators
Create departments and assign users to roles
Department Heads
Manage their team members and approvals
HR Managers
Organize teams by function for better management
Key Features
Organization Structure
Functional divisions like Admin, Finance, Purchase, Sales for clear team organization
Default departments (Admin and Finance) created automatically during account setup
Unlimited departments to match your organizational structure and business needs
Role-Based Access
Three-level hierarchy (L1, L2, L3) automatically created for each department
Approval workflows mapped to department roles for systematic authorization
Permission control based on department and role assignment for data security
How It Works
Automatic Setup
- Default Creation: Admin and Finance departments created automatically during account setup
- Add Departments: Create additional departments as needed (Purchase, Sales, HR, Operations, etc.)
- Automatic Roles: System creates L1, L2, and L3 roles for each department instantly
- Assign Users: Assign team members to department roles through user management
- Configure Workflows: Set up approval workflows using department roles
Understanding Department Roles
Three-Level Role Hierarchy
Every department automatically gets three roles with increasing authority:
L1-[Department Name] (Level 1)
- Entry-level role for executives and junior team members
- Can create and submit documents for approval
- Typically first point of transaction initiation
- Example: L1-Purchase (Purchase Executive)
L2-[Department Name] (Level 2)
- Mid-level role for managers and supervisors
- Can approve transactions within defined limits
- Reviews and validates L1 submissions
- Example: L2-Finance (Finance Manager)
L3-[Department Name] (Level 3)
- Senior-level role for department heads and directors
- Final approval authority within department
- Can approve high-value transactions
- Example: L3-Sales (Sales Director)
Default Departments
| Department | Purpose | Auto-Created Roles |
|---|---|---|
| Admin | Platform administration and system configuration | L1-Admin, L2-Admin, L3-Admin |
| Finance | Financial transactions, accounting, and compliance | L1-Finance, L2-Finance, L3-Finance |
Why These Two?
- Essential for basic platform operations and financial management
- Cannot be deleted (future versions will allow disable option)
- Names cannot be changed once created
- Ensure minimum structure for access control
Common Departments
| Department | Typical Use | Common Workflows |
|---|---|---|
| Purchase | Procurement and vendor management | Purchase requisitions, PO approvals, vendor payments |
| Sales | Customer orders and revenue operations | Quotation approvals, sales order processing, credit limits |
| Operations | Production, logistics, and operations | Material requests and inventory movements |
| HR | Human resources and employee management | Leave approvals, expense claims, employee onboarding |
| Warehouse | Inventory and warehouse management | Stock transfers, goods receipts, dispatch approvals |
| Quality | Quality control and assurance | Material inspection, quality approvals, vendor audits |
Getting Started
| Task | Guide | Time Required |
|---|---|---|
| View Departments List | How to View Guide | 1 minute |
| Add New Department | How to Add Guide | 2 minutes |
| Assign Users to Roles | User Management | 5 minutes |
Approval Workflow Example
Purchase Order Approval Flow
Scenario: Purchase Executive creates a PO for ₹2,50,000
- L1-Purchase (Executive) creates the purchase order and submits for approval
- L2-Purchase (Manager) reviews - PO amount is within ₹1L limit, but exceeds, so forwards
- L3-Purchase (Head) approves - within ₹5L department limit
- Since amount exceeds ₹2L, routes to L2-Finance for financial approval
- L3-Finance (CFO) gives final approval as amount exceeds ₹1L finance threshold
- PO automatically sent to supplier after all approvals
Audit Trail: Every approval step recorded with user, role, timestamp, and comments.
Department Naming Rules
Important Constraints:
- Department names cannot be changed after creation
- Choose names carefully during setup
- Use standard functional names for clarity
- Avoid abbreviations or internal codes
- Keep names professional and descriptive
Good Names:
- Purchase, Sales, Finance, Operations, Warehouse, Quality, HR
Avoid:
- Dept1, PUR, SLS, OPS (too cryptic)
- John's Team, Mumbai Team (person or location specific)
Future Enhancement:
- Disable option will be available to deactivate unused departments without deletion
- Name editing may be enabled in future versions
Role Assignment Strategy
Recommended Hierarchy
L1 Roles: Junior staff, executives, entry-level team members
- Limited approval authority
- Create and submit documents
- Example: Purchase Executive, Sales Executive
L2 Roles: Managers, supervisors, team leads
- Mid-level approval authority
- Review and validate submissions
- Example: Purchase Manager, Finance Manager
L3 Roles: Department heads, directors, senior managers
- Highest department-level authority
- Final approvals within department
- Example: Head of Purchase, CFO, Sales Director
Impact on System Functions
Access Control
Module Access:
- Users see only modules relevant to their department
- Purchase department users access procurement features
- Sales department users access customer and order features
Data Visibility:
- Department-based data filtering in reports
- Users see transactions related to their department
- Cross-department visibility controlled by permissions
Approval Routing
Automatic Routing:
- System routes approvals based on department roles
- Budget thresholds trigger inter-department approvals
- Workflow engine uses department hierarchy for escalation
Notification:
- Role-based email and in-app notifications
- Department heads receive approval requests
- Team members notified of approval status
Related Sections
- Business Group - Parent organization setup
- Business Units - Legal entity management
- Role Permissions - Configure role-based access
- Approval Workflows - Set up approval rules
- Manage Users - Assign users to departments
Quick Tips
Best Practices
Create departments matching your actual organizational structure for easy user understanding
Use standard functional names (Finance, Purchase, Sales) rather than custom internal terms
Plan your department structure before adding users to avoid reassignment work
Assign department heads to L3 roles immediately for proper approval workflow functionality
Document your approval thresholds by department and role for team reference
Need help? Contact support at support@bizconnekt.com