Skip to main content

How to Add Department

Overview​

Create new departments to structure your organization by functional areas. Each department automatically gets three hierarchical roles (L1, L2, L3) for role-based access control and approval workflows.

Prerequisites​

Before adding a department:

  • User has "Create Department" permission in BizAdmin
  • Clear understanding of department's functional purpose
  • Department name decided (cannot be changed later)
  • Approval hierarchy planned for the department

Step-by-Step Guide​

Step 1: Navigate to Add Department​

  1. Login to BizAdmin portal
  2. Click Organization from the left sidebar
  3. Select Departments
  4. Click the + icon next to "Select Department" dropdown
  5. Add department popup opens

Step 2: Enter Department Name​

Add department popup displays with a single field:

Department Name (Required)

  • Enter the functional name of the department
  • Use standard, professional names
  • Keep it concise and descriptive
  • Examples: "Purchase", "Sales", "Operations", "HR", "Warehouse", "Quality"

Important Naming Guidelines:

Cannot Be Changed Later

Once you click Add, the department name is locked and cannot be edited. Choose carefully!

Good Department Names:

  • Purchase
  • Sales
  • Finance
  • Operations
  • Warehouse
  • Quality
  • HR
  • IT
  • Marketing
  • Customer Service

Avoid These:

  • Abbreviations (PUR, SLS, OPS)
  • Person names (John's Team, Mumbai Team)
  • Internal codes (Dept1, Dept2)
  • Location-specific (Delhi Office - use Business Units instead)
  • Too generic (Department A, Team 1)

Step 3: Review Auto-Generated Roles​

Before clicking Add, understand what will be created:

When you add a department named "Purchase", the system automatically creates:

  • L1-Purchase (Level 1 role)
  • L2-Purchase (Level 2 role)
  • L3-Purchase (Level 3 role)

These roles will be immediately available for:

  • User assignment
  • Permission configuration
  • Approval workflow setup
  • Access control

You don't create roles manually - they're automatic!

Step 4: Add the Department​

  1. Type the department name in the text field
  2. Double-check the spelling and naming
  3. Confirm it's the name you want (remember: cannot change later)
  4. Click outside the dropdown or press Enter
  5. The department is created instantly
  6. Popup closes automatically

No confirmation dialog - department is created immediately upon selection completion.

Step 5: Verify Department Creation​

Check the Departments List:

  1. The new department appears in the Departments column (left side)
  2. Click on the department name
  3. Roles column (right side) shows the three auto-generated roles:
    • L1-[YourDepartmentName]
    • L2-[YourDepartmentName]
    • L3-[YourDepartmentName]

Example:

If you added "Purchase", you'll see:
- L1-Purchase
- L2-Purchase  
- L3-Purchase

After Adding Department​

Next Steps​

1. Assign Users to Roles

Navigate to: Subscription > Manage Users

  • Assign team members to L1, L2, L3 roles
  • L1: Junior staff and executives
  • L2: Managers and supervisors
  • L3: Department heads and directors

2. Configure Role Permissions

Navigate to: Access Control > Role Permissions

  • Define what each role can access
  • Set module-level permissions
  • Configure feature access per role

3. Set Up Approval Workflows

Navigate to: Access Control > Approval Workflows

  • Create department-based approval rules
  • Define budget thresholds for each role
  • Set up multi-level approval chains

4. Test the Setup

  • Assign test users to roles
  • Create sample transactions
  • Verify approval routing works correctly
  • Adjust permissions as needed

Common Department Setups​

Manufacturing Company​

Typical Departments:

  • Purchase (procurement and vendor management)
  • Sales (customer orders and revenue)
  • Production (manufacturing operations)
  • Quality (QC and quality assurance)
  • Warehouse (inventory and logistics)
  • Finance (accounting and compliance)
  • Admin (administration and HR)

Trading Company​

Typical Departments:

  • Purchase (buying and imports)
  • Sales (domestic and export sales)
  • Warehouse (stock management)
  • Logistics (transportation and delivery)
  • Finance (accounts and taxation)
  • Admin (general administration)

Service Company​

Typical Departments:

  • Operations (service delivery)
  • Sales (business development)
  • Customer Service (support and relations)
  • Finance (billing and accounts)
  • HR (recruitment and training)
  • Admin (administration)

Approval Workflow Planning​

Plan Your Hierarchy Before Adding

Purchase Department Example:

L1-Purchase (Purchase Executive)

  • Create purchase requisitions
  • Submit to L2 for approval
  • Authority: Up to ₹25,000

L2-Purchase (Purchase Manager)

  • Approve PRs and POs up to ₹1,00,000
  • Review vendor quotes
  • Submit high-value POs to L3

L3-Purchase (Head of Purchase)

  • Approve POs above ₹1,00,000
  • Final department authority up to ₹5,00,000
  • Above ₹5L routes to Finance for cross-department approval

Important Limitations​

Cannot Be Changed​

Permanent Decisions:

  • Department Name: Cannot be edited after creation
  • Role Names: Auto-generated as L1, L2, L3 and cannot be changed
  • Default Departments: Admin and Finance cannot be deleted

Future Enhancements:

  • Disable option for unused departments (coming soon)
  • This will allow hiding departments without deletion
  • Name editing may be enabled in future versions

Cannot Be Deleted​

Once created, departments remain in the system permanently. Plan carefully:

  • Only create departments you'll actually use
  • Use standard functional names
  • Think long-term about organizational structure
  • Consider future growth and expansion

Best Practices​

Recommendations

Start with core functional departments (Purchase, Sales, Finance) before adding specialized ones

Use standard department names that everyone understands rather than internal terminology

Match department structure to your actual organization for easy user adoption

Document your approval hierarchy and thresholds before configuring workflows

Assign department heads to L3 roles immediately after creation for proper approval functionality

Create departments based on business functions, not locations (use Business Units for locations)

Common Scenarios​

Scenario 1: Growing Business Adds Department​

Situation: Company expanding, need to add Warehouse department.

Steps:

  1. Navigate to Departments page
  2. Click + icon next to Select Department
  3. Enter "Warehouse" as department name
  4. Verify name is correct
  5. Click outside or press Enter
  6. Warehouse department created with L1-Warehouse, L2-Warehouse, L3-Warehouse roles
  7. Go to Manage Users and assign warehouse team to roles

Result: Warehouse operations now have dedicated department structure and approval hierarchy.

Scenario 2: Setting Up Quality Control​

Situation: Need dedicated Quality department for inspection approvals.

Steps:

  1. Add "Quality" department
  2. System creates L1-Quality, L2-Quality, L3-Quality
  3. Assign QC inspectors to L1-Quality
  4. Assign QC Manager to L2-Quality
  5. Assign QC Head to L3-Quality
  6. Configure workflows: Material inspection requires L2-Quality approval

Result: Quality approvals now route through Quality department hierarchy.

Scenario 3: Creating Customer Service Department​

Situation: Growing support team needs their own department.

Steps:

  1. Add "Customer Service" department
  2. Roles created: L1-Customer Service, L2-Customer Service, L3-Customer Service
  3. Assign support executives to L1 role
  4. Assign support manager to L2 role
  5. Assign customer service head to L3 role
  6. Set permissions for viewing customer data and creating credit notes

Result: Support team has structured department with proper access controls.

Troubleshooting​

Issue 1: Cannot Find + Icon​

Symptoms: Don't see option to add department

Solutions:

  • Check you have "Create Department" permission
  • Verify you're logged into BizAdmin (not Bizconnekt App)
  • Ensure you're on Organization > Departments page
  • Look for + icon next to "Select Department" dropdown
  • Contact administrator if permission issue

Issue 2: Duplicate Department Name Error​

Symptoms: Error when trying to add department with existing name

Solutions:

  • Check Departments list for existing department with same name
  • Use slightly different name (e.g., "Purchase Operations" instead of "Purchase")
  • Cannot have two departments with identical names
  • Names are case-sensitive

Issue 3: Added Wrong Name​

Symptoms: Created department with typo or wrong name

Solutions:

  • Cannot edit or delete department name currently
  • Contact support for assistance
  • Work around by using the department as-is
  • Future disable feature will help hide unused departments
  • Be extra careful when naming new departments

Frequently Asked Questions​

Q: How many departments can I create?

A: Unlimited. Create as many as needed to match your organizational structure.

Q: Can I delete a department I created by mistake?

A: No, departments cannot be deleted currently. A disable feature is planned for future releases. Choose names carefully.

Q: Can I rename department roles from L1/L2/L3 to custom names?

A: No, the L1, L2, L3 naming is standard across the platform. This consistency simplifies approval workflows and user management.

Q: Do I need to create roles separately after adding department?

A: No, roles are automatically created when you add a department. Three roles (L1, L2, L3) are generated instantly.

Q: Can I create a department without the three-level hierarchy?

A: No, all departments follow the three-level role structure. You don't have to use all three levels, but they're created automatically.

Q: What if my organization doesn't have three levels in a department?

A: You can assign users to only the levels you need (e.g., just L1 and L3). The unused roles remain available but unassigned. This flexibility allows you to adapt the structure to your actual needs.

Q: Should I create departments based on locations?

A: No, departments are for functional divisions (Purchase, Sales, Finance). Use Business Units for location-based organization (Delhi Office, Mumbai Branch). This keeps structure clear and manageable.

Q: Can the same person have roles in multiple departments?

A: Yes, users can be assigned to roles in multiple departments. For example, a Finance Manager might have L2-Finance and also L1-Purchase roles for visibility into procurement.

Q: How soon after creating a department can I start using it?

A: Immediately. The department and its roles are available right away for user assignment, permission configuration, and workflow setup.

Q: Will creating new departments affect existing approval workflows?

A: No, existing workflows continue working as configured. New departments need their own workflow rules set up separately in Access Control > Approval Workflows.

Department Naming Checklist​

Before creating a department, verify:

  • Name is professional and descriptive
  • Name represents a functional area, not a location
  • Name is spelled correctly (cannot be changed)
  • Name is not already used by another department
  • Name is not too long or too short (3-20 characters ideal)
  • Name follows standard business terminology
  • Team members will easily understand the department's purpose
  • Name will remain relevant as company grows

Post-Creation Workflow​

Complete Setup Checklist

After adding a department, complete these steps for full functionality:

Day 1:

  • Add department
  • Assign department head to L3 role
  • Assign key team members to L1 and L2 roles

Week 1:

  • Configure basic permissions for each role in Access Control
  • Set up initial approval workflows for the department
  • Test approval flow with sample transactions

Week 2-3:

  • Refine permissions based on user feedback
  • Adjust approval thresholds if needed
  • Train team members on their roles and responsibilities
  • Document department-specific processes

Month 1:

  • Review department performance and usage
  • Optimize approval workflows based on real usage
  • Ensure all team members are properly assigned
  • Address any access or permission issues

Example: Complete Department Setup​

Setting Up Sales Department

Step 1: Create Department

  • Navigate to Departments
  • Click + icon
  • Enter "Sales"
  • Department created with L1-Sales, L2-Sales, L3-Sales

Step 2: Assign Team Members

  • 5 Sales Executives → L1-Sales
  • 2 Sales Managers → L2-Sales
  • 1 Sales Director → L3-Sales

Step 3: Configure Permissions

  • L1-Sales: Create quotations, view customers, limited pricing access
  • L2-Sales: Approve quotations up to ₹5L, manage customer credit limits
  • L3-Sales: Approve all quotations, access all pricing, customer master management

Step 4: Setup Approval Workflows

  • Quotations up to ₹2L: L2-Sales approval
  • Quotations ₹2L-₹10L: L3-Sales approval
  • Quotations above ₹10L: L3-Sales + L2-Finance approval

Step 5: Test and Refine

  • Create test quotation
  • Verify it routes to L2-Sales
  • Test high-value quotation routing
  • Adjust thresholds based on feedback

Result: Fully functional Sales department with clear hierarchy and approval flows.

Tips for Large Organizations​

If you have 10+ departments:

Use Consistent Naming:

  • All operations departments: Operations-[Function]
  • Example: Operations-Manufacturing, Operations-Logistics
  • Helps group related departments visually

Plan Hierarchy:

  • Document approval thresholds for each department
  • Create matrix showing inter-department approvals
  • Example: Purchase over ₹5L also needs L2-Finance

Stagger Implementation:

  • Don't create all departments at once
  • Add core departments first (Purchase, Sales, Finance)
  • Add supporting departments as needed
  • Allows time to refine processes

Communication:

  • Announce new departments to all users
  • Explain role structure and expectations
  • Provide training on approval processes
  • Share contact list for each department

Common Mistakes to Avoid​

Mistake 1: Creating Location-Based Departments Bad: "Delhi Office", "Mumbai Branch" Good: Use Business Units for locations, Departments for functions

Mistake 2: Using Abbreviations Bad: "PUR", "SLS", "OPS" Good: "Purchase", "Sales", "Operations"

Mistake 3: Creating Too Many Departments Initially Bad: Creating 15 departments on day one Good: Start with 4-6 core departments, add more as needed

Mistake 4: Not Planning Approval Hierarchy Bad: Creating department without defining who approves what Good: Document approval thresholds before creating workflows

Mistake 5: Person-Specific Department Names Bad: "Rajesh's Team", "John's Group" Good: "Quality Control", "Customer Service"

Mistake 6: Overly Generic Names Bad: "Department A", "Team 1", "Group 2" Good: "Warehouse", "Marketing", "IT Support"

Need help? Contact support at support@bizconnekt.com