freshtrack.com

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 &amp; 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 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 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.

- 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 &amp; 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.

This article will explain what the permissions are and how to use them.

Permissions Guide

Gateway Helpdesk

FreshTrack Cloud Client Portal

FreshTrack Website

Find answers and get help from Intercom Support and Community Experts

This site employs cookies and other technologies that we and our third party vendors use to monitor and record personal information about you and your interactions with the site (including content viewed, cursor movements, screen recordings, and chat contents) for the purposes described in our Cookie Policy. By continuing to visit our site, you agree to our {websiteTermsLink}, {privacyPolicyLink} and {cookiePolicyLink}.

This site uses cookies and similar technologies ("cookies") as strictly necessary for site operation. We and our partners also would like to set additional cookies to enable site performance analytics, functionality, advertising and social media features. See our {cookiePolicyLink} for details. You can change your cookie preferences in our Cookie Settings.

We use cookies to make our site work and also for analytics and advertising purposes. You can enable or disable optional cookies as desired. See our {cookiePolicyLink} for more details.

Advertising cookies are set by our advertising partners to collect information about your use of the site, our communications, and other online services over time and with different browsers and devices. They use this information to show you ads online that they think will interest you and measure the ads' performance. Social media cookies are set by social media platforms to enable you to share content on those platforms, and are capable of tracking information about your activity across other online services for use as described in their privacy policies.

These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.

These cookies are necessary for the website to function and cannot be switched off in our systems.

These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site.

You have the right to opt out of the sale of your personal information. See our {cookiePolicyLink} for more details about how we use your data.

Your Privacy Choices

We use cookies to enhance your experience. You can customize your cookie preferences below. See our {cookiePolicyLink} for more details.

Cookie Settings

Link, Press control-option-right-arrow to exit

Empty Help Center

Uh oh. That page doesn’t exist.

Disappointed

Neutral

Smiley

Thinking...

Searching through sources...

Analyzing...

Tickets submitted through the messenger or by a support agent in your conversation will appear here.

Module	UI view	UI edit	What it means
System	`system.view`	`system.edit`	Global system settings (roles/permissions, core config).
Reporting	`reporting.view`	`reporting.edit`	View reports
Entity	`entity.view`	`entity.edit`	Manage business entities (customers/suppliers/growers/consignees/contacts—depends on your model).
Product	`product.view`	`product.edit`	Products
Inventory	`inventory.view`	`inventory.edit`	Stock records & movements (adjustments/transfers/locations—depending on your setup).
Asset	`asset.view`	`asset.edit`	Asset register (equipment/assets/maintenance—depending on your setup).
Farming	`farming.view`	`farming.edit`	Farms/blocks/plantings/harvest/ bins-related operational data.
Activity	`activity.view`	`activity.edit`	Operational activity/workflow records (exact meaning depends on your module).
Packing	`packing.view`	`packing.edit`	Packing operations (pallets/ box / repacking operations and includes all the custom or not custom actions connected to it as well
Dispatch	`dispatch.view`	`dispatch.edit`	Dispatch operations (dispatch loads/consignments/load actions).
Distributor	`distributor.view`	`distributor.edit`	Distributor/partner records (meaning depends on how you use “Distributor”).
Form	`form.view`	`form.edit`	Use/manage forms and submissions operationally.
Printing	`printing.view`	`printing.edit`	Printers, label templates, print jobs,create a batch , manual grader, recipe, grader
HR	`hr.view`	`hr.edit`	time clock/ piece rate/ time pay/ work roles and work areas /HR operations (depends on your HR module scope).
GP	`gp.view`	`gp.edit`	Grower payment/ schedules/ details/ payments and all the actions connected to it
Compliance	`compliance.view`	`compliance.edit`	Compliance records (audits/certs/checklists—depends on your setup).

Permissions Guide

Permissions overview

Admin permissions.

API permissions.