Search Knowledge Base Articles

Roles, Permissions & Branch-Style Operations

Purpose

This article explains how user roles and permissions work in the Thulo Logistics Module and how logistics companies can operate multiple cities or offices (branch-style operations) using staff permissions.

This is a core reference article for Admins setting up teams and access control.

Who This Is For

  • Admins (primary audience)

  • Operations Managers

  • Staff Leads responsible for permissions

User Roles in the Logistics Module

The Logistics Module supports the following user roles:

Admin

Admins have full control over the Logistics Module.

Admins can:

  • Configure all logistics settings

  • Manage users and permissions

  • View all logistics data (global visibility)

  • Monitor operations, billing, and tracking

Staff

Staff are operational users who perform daily logistics tasks.

Staff typically:

  • Create locker packages and shipments

  • Approve pickups

  • Process deliveries

  • Update tracking statuses

Staff access depends entirely on assigned permissions.

Agent

Agents are operational users similar to staff, often representing:

  • Partner offices

  • External agencies

  • Remote operational units

Agents use the same permission model as staff, with more limited access in most cases.

Driver

Drivers are delivery-focused users.

Drivers can:

  • View assigned deliveries

  • Update delivery status

  • Submit proof of delivery

Drivers cannot:

  • Create or edit packages or shipments

  • Access pricing, invoices, or settings

Customer

Customers interact with the Logistics Module through the customer portal.

Customers can:

  • Create recipients

  • Submit pre-alerts

  • Track shipments

  • View invoices and payments

Customers cannot access internal logistics operations.

Permission Model Explained

Permissions in the Logistics Module are module-specific and action-based.

Common permission types include:

  • View

  • Create

  • Edit

  • Delete

Permissions are applied separately to logistics components such as:

  • Pre-Alerts

  • Locker Packages

  • Pickups

  • Consolidations

  • Shipments

  • Reports and dashboards

“Own” vs “Global” Data Visibility

A key concept in the Logistics Module is data visibility.

View (Own)

  • Users can see only:

    • Records they created, or

    • Records assigned to them

  • Used to limit operational scope

View (Global)

  • Users can see all logistics records within the tenant

  • Typically assigned to Admins and supervisors

This visibility model is essential for controlling access without duplicating data.

Branch-Style Operations (Important Concept)

The Logistics Module does not have a native “branch” or “office” entity.

Instead, branch-style operations are implemented using staff roles and permissions.

How This Works in Practice

  • Each city, warehouse, or office uses dedicated staff or agent accounts

  • Staff are assigned:

    • Only required permissions

    • “View (Own)” visibility where appropriate

  • Admins retain “View (Global)” access

This allows:

  • Multiple operational locations

  • Centralized pricing and configuration

  • Controlled data visibility

Recommended Permission Patterns

Head Office / Super Admin

  • Full permissions

  • View (Global)

  • Manages settings, users, and pricing

City / Branch Staff

  • Create and process packages and shipments

  • View (Own) data only

  • No access to admin settings

Agents / Partners

  • Limited operational permissions

  • Restricted visibility

  • No access to billing or pricing configuration

Drivers

  • View assigned deliveries only

  • Update delivery status and proof of delivery

  • No access to other logistics data

What Permissions Do NOT Do

To avoid misunderstanding:

Permissions do not:

  • Create hard data isolation between branches

  • Separate invoices or pricing by branch

  • Duplicate logistics settings per location

All logistics settings remain tenant-wide.

Key Things Admins Should Remember

  • Permissions control actions and visibility, not system structure

  • Incorrect permission setup can block operations

  • Branch-style operations rely on discipline and role clarity

  • Review permissions regularly as teams grow

Where to Go Next

  • To understand the overall system:
    Logistics Module – Overview & Concepts

  • To configure the system:
    Admin Configuration – Logistics Settings

  • To understand daily operations:
    Staff / Agent Operational Workflows

Did you find this article useful?

Related Articles