Roles and permissions
Each user in Cargo-Planner is assigned a single role that determines their level of access. Roles are hierarchical — each role includes all the permissions of the roles below it.
Roles
The roles from lowest to highest level of access:
- Planner (default) - Can create, view, edit and delete load lists. This is the base role assigned to all new users.
- Editor - Everything the Planner can do, plus the ability to create and modify equipment, cargo libraries, presets and projects.
- Developer - Everything the Editor can do, plus access to API tokens and webhook management for integrations.
- Administrator - Everything the Developer can do, plus user management, company details and subscription management.
Feature permissions
Users with the Planner role can optionally be granted individual feature permissions. This allows you to give a Planner access to specific editing capabilities without promoting them to a full Editor role. The available feature permissions are:
| Permission | Allows |
|---|
| Cargo Editor | Create and modify cargo library items |
| Equipment Editor | Create and modify equipment |
| Project Editor | Create and modify projects |
| Preset Editor | Create and modify load presets |
| Company Editor | Modify company details |
Feature permissions are only relevant for the Planner role. Users with the Editor role or above already have all these capabilities as part of their role.
Additional properties
Isolated
Isolated is a property that can be enabled on any user regardless of their role. An isolated user:
- Can only see load lists they have created themselves
- Cannot see load lists or projects created by other users in the organization
- Has their load lists automatically placed in a project named after their username
Other non-isolated users in the organization can see load lists created by isolated users. This makes isolated mode useful for external users (e.g., customers or partners) who should be able to plan their own shipments, while internal staff can still view and manage those plans.
An isolated user cannot be an Administrator.
Permission matrix
The tables below show what each role can do:
Loadlist operations
| Task | Planner | Editor | Developer | Administrator |
|---|
| View | Yes | Yes | Yes | Yes |
| Create | Yes | Yes | Yes | Yes |
| Edit | Yes | Yes | Yes | Yes |
| Delete | Yes | Yes | Yes | Yes |
Project operations
| Task | Planner | Editor | Developer | Administrator |
|---|
| View | Yes | Yes | Yes | Yes |
| Create | No | Yes | Yes | Yes |
| Edit | No | Yes | Yes | Yes |
| Delete | No | Yes | Yes | Yes |
Equipment library operations
| Task | Planner | Editor | Developer | Administrator |
|---|
| View | Yes | Yes | Yes | Yes |
| Create | No | Yes | Yes | Yes |
| Edit | No | Yes | Yes | Yes |
| Delete | No | Yes | Yes | Yes |
Cargo library operations
| Task | Planner | Editor | Developer | Administrator |
|---|
| View | Yes | Yes | Yes | Yes |
| Create | No | Yes | Yes | Yes |
| Edit | No | Yes | Yes | Yes |
| Delete | No | Yes | Yes | Yes |
API Token management
| Task | Planner | Editor | Developer | Administrator |
|---|
| View | No | No | Yes | Yes |
| Create | No | No | Yes | Yes |
| Edit | No | No | Yes | Yes |
| Delete | No | No | Yes | Yes |
Webhooks management
| Task | Planner | Editor | Developer | Administrator |
|---|
| View | No | No | Yes | Yes |
| Create | No | No | Yes | Yes |
| Edit | No | No | Yes | Yes |
| Delete | No | No | Yes | Yes |
User management
| Task | Planner | Editor | Developer | Administrator |
|---|
| View | No | No | No | Yes |
| Create | No | No | No | Yes |
| Edit | No | No | No | Yes |
| Delete | No | No | No | Yes |
Subscription management
| Task | Planner | Editor | Developer | Administrator |
|---|
| View | No | No | No | Yes |
| Manage | No | No | No | Yes |