積載

Operational delegations

An Operational Delegation is an explicit mandate allowing a named person or partner company to perform a permitted activity for the granting company. It records the recipient, activity, resource scope, validity, supporting mandate, acceptance, and revocation.

Use a delegation when a contractor must register production, contribute evidence, or carry out another authorized action on your company's records. Company membership and business roles remain the normal way to authorize your own team.

What a delegation controls

A grant applies to its selected activity and scope. Preparation, approval, and publication are different responsibilities. Permission to contribute evidence does not include approving it, and preparing a passport does not include publishing it.

The scope can identify a product, facility, catalog, batch, instance, or passport. Every restriction must match the resource being used. An accepted mandate for one batch cannot be used to change an unrelated batch.

The recipient must accept the mandate, and it must be within its validity period. Revoked or expired mandates cannot authorize further actions. A partner's role as manufacturer, facility operator, seller, or importer does not create editing rights on its own. Platform administration does not substitute for company authority or a company declaration.

Create and accept a delegation

  1. A Company Administrator of the granting company opens Logistic → Facilities → Operational delegations.
  2. Search existing mandates, then select Create new delegation.
  3. Search for either a Recipient company or a Recipient user. Select exactly one recipient.
  4. Choose the permitted Activity, validity dates, and the narrowest appropriate resource scope.
  5. Supply the Mandate reference and, when available, select a Retained document revision containing the supporting authorization.
  6. Select Grant mandate.
  7. The named user, or a Company Administrator of the recipient company, reviews the invitation and selects Accept or rejects it with a reason.

For a company recipient, its own members still need the business responsibility appropriate to the activity. Naming a partner company does not give every member all permissions.

Example

A brand asks a manufacturing partner to register production for one product during a six-month contract. The brand grants production-management authority for that product, with the contract reference and dates. The partner accepts. Its authorized production staff can carry out the delegated work; they cannot approve the brand's technical releases or publish its passports unless separate valid authority covers those actions.

Keep authority current

Review mandates when contracts, staff, responsibilities, or resources change. The granting company's administrator uses Revoke mandate when the authorization should stop. Previous records remain attributable to the actor who performed the work.

If an operation is denied, check acceptance, dates, activity, company, and all scope restrictions. For a company recipient, also check the acting user's company role. An application permission is not evidence of externally verified supervisory or regulatory authority.