Permissions Guide

Permissions are module-based.
Each module (for example, Dispatch Loads, Packing, Human Resources, etc.) has its own set of permissions such as View, Edit, or Admin.

Module permissions apply to the whole module.
If a user has Dispatch Load – View & Edit, they can view and edit all dispatch loads in the system.

For example, if a user only needs to see the dispatch loads assigned to them and must not access the Pricing tab or other advanced Dispatch Load functions, it’s better to use the Distribution module instead.
In that case, their permissions should be configured like this:

If you want to restrict what they can see to a specific farm or a specific consignee, click Filter here and add all the restrictions you need.

You cannot restrict permissions to only part of a module (for example, “edit dispatch loads but don’t allow wasting boxes”). There is no record-level or partial permission inside a module.

Obviously, if a user is packing and needs to print, they will also need access to the Printing module — especially if they need to start a batch or change any labels.

Admin permissions.
“Admin” permissions give full control for the administration Area. For example, Human Resources Admin gives access to all HR-related settings like piece rate or work roles.

API permissions.
API permissions are only used when there is an external connection or when you are creating an API integration to read data from FreshTrack. They are not needed for normal day-to-day use inside the application.