Viewing trades
Trade visibility is scoped by role and company context. Company and project users see trades for their company scope. System Admin users can filter by company. Desk users select an accessible company and view active trades.
Role-specific list behaviour
System Admin users can use the company filter and can export for a selected company.
Company and project users load trades from their company scope.
Desk users must choose a company and the list requests active trades only.
Desk users do not open the trade detail page from the Trades list.
Creating and importing trades
The New Trade and Import Trades actions are shown only when the user has trade create permission. The server also checks that the target company exists, is active, and can be managed by the user.
Create checks
A company id must be supplied.
The company must exist.
The company must be active.
The user must be allowed to manage trades for that company.
At least one trade must be submitted.
If the company has a mandatory trade tag, at least one valid trade tag must be submitted.
Updating trades
Saving changes from the trade Overview tab requires trade edit permission in the UI. The server also validates company access through the trade management permission check.
Update checks
The trade must exist.
The trade's company must exist and be active.
The user must be allowed to manage trades for the company.
Submitted tags must belong to the same company and use the trade resource type.
If the company has a mandatory trade tag, the update cannot clear all trade tags.
Company Admin access
Company Admin users can manage trades only when they administer the company. If a Company Admin is not listed as an admin for the company, trade management is rejected.
Desk access
Desk users use a company selector on the Trades page and load active trades only. For export, the server confirms the desk has supplier access to the selected company.
System Admin access
System Admin users can view trades outside a single company context and can choose a company when exporting. They still need to provide a valid company for company-scoped operations such as export.
Export access
Export Trades is shown when the user has trade export permission and the list has data. System Admin users select the company to export. Company and project users export from their current entity scope.
Export checks
A company id is required for export.
The company must exist.
Company Admin users must have company membership for the selected company.
Desk users must have supplier access to the selected company.
Users without permission to view unrelated company trades are rejected.
Inactive companies
Trades cannot be created, imported, or updated for inactive companies. The API returns a validation error when the company is deactivated.
Permissions vs setup issues
A missing action is usually a permission issue. A visible action that fails after submission is usually a company, validation, duplicate, or access-scope issue. Use the error message and the user's company context to separate the two.
For agencies: what you can and cannot do
Trade management is a hiring-company responsibility, so agency access to trades is read-and-export only.
You select an accessible hiring company and view its active trades; creating, editing, and importing trades are not agency actions.
You can export trades for a company only where your agency has supplier access to that company.
Rate visibility within trades still depends on your agency's rate access settings.
If you need a new or changed trade, request it from the hiring company, since they manage the trade catalogue.