Skip to main content

Tendering Permissions

Written by Alvys Admin

👥 Primary Audience: Admins , Partner Admins, Operation Managers, Data Entry, Dispatchers

The Tendering Permissions category in Alvys controls access to EDI (Electronic Data Interchange) tendering functionality, the automated process by which shippers send load offers (tenders) to carriers and brokers. Users with these permissions can accept, reject, or update tenders. This category includes two (2) permissions that govern who can participate in the tender workflow by viewing and acting on the Tender Board, as well as who can share EDI data externally.

Tendering is a specialized function in freight logistics. Unlike load creation, which is usually done manually, tendering relies on electronic messaging standards, primarily EDI 204 and 990, to exchange load information between trading partners’ systems. Not all Alvys users interact with tenders; this functionality is mainly relevant to users whose companies have active EDI integrations with shippers or other trading partners.

⚠️ Tendering functionality requires EDI integrations between your company and your trading partners. If your company does not use EDI, these permissions will have no practical effect even if granted.

Where to Manage Tendering Permissions

⚠️ To modify these permissions, the logged-in user, preferably an administrator, must possess the “Set Permission permission located within the Management category. Without “Set Permission”, a user can view the user profile or form but cannot adjust any permissions. For additional information regarding the “Set Permission, please refer to the Management & Privacy Permissions article.

Customer Management Permissions are configured at the individual user level within the User Management interface. To adjust these settings:

  1. Select your username located in the bottom left corner.

  2. Navigate to the Company Profile and select the Users tab.

    Notion Image
    Notion Image
  3. Choose an existing user to Edit or select the Add User button to create a new profile.

    Notion Image
    Notion Image
  4. Scroll to the Permissions section and locate the Tendering category.

  5. Identify the two (2) individual checkboxes corresponding to the Tendering permissions detailed in this article: Participate In Tender and EDI Share

Notion Image

Participate In Tender

The Participate In Tender permission allows a user to access the Tender Board page, where they can view, accept, reject, and manage incoming EDI tenders from shippers and trading partners. Without this permission, the Tender Board is not accessible. Responding to inbound tenders requires specialized knowledge, including lane pricing, equipment availability, and the company’s capacity to fulfill the tendered loads. Limiting access to the Tender Board ensures that only qualified personnel handle load offers, protecting the company’s commitments and revenue. For more information on participating in tendering, see the help center article.

Notion Image

Users with the Participate In Tender permission can accept or reject tenders, view tender details, and review EDI history. When accepting a tender, each stop must be linked to a company. If the required company does not yet exist in the system, the user can create it inline. This action triggers a company creation permission check: the user must have Create Customer permission for brokers or customers, or Create Company permission for non-customer entities such as shippers or terminals, depending on the type of company being created.

Notion Image

⚠️ EDI integration required: Inbound tenders come from trading partners via EDI. Without valid and active EDI integrations, no tenders will appear on the Tender Board.

By default, this authorization is extended to the Support, Partner Admin, Admin, Operation Manager, and Data Entry roles. Conversely, this specific permission is not assigned by default to the Dispatcher, Biller, Sales Agent, Office Admin, Safety, or Driver roles.

Data Entry is the only non-admin role that receives Participate In Tender by default. This may seem unusual, but Data Entry users often handle EDI tender intake and load creation from incoming tenders as part of their data processing workflow.

Best Practices: Grant the Participate In Tender permission to users responsible for handling incoming load offers from EDI trading partners. In companies that use EDI tenders extensively, also consider granting this permission to Dispatchers in addition to Data Entry staff, so they can respond to tenders in real time based on available capacity and operational knowledge.

EDI Share

The EDI Share permission allows a user to share load visibility data externally with EDI trading partners. This includes status updates, tracking information, appointment times, and other operational details. Without this permission, users cannot perform outbound EDI sharing.

Without EDI Share, teams must manually receive load information from shippers by email, phone, or customer portal and re-enter it into Alvys. For large shippers sending dozens or hundreds of loads weekly, this manual process is slow, error-prone, and unsustainable. Granting EDI Share automates this step and positions your company as a preferred carrier or broker for shippers who require EDI capability.

⚠️ External sharing requires configured EDI integrations with trading partners.

To share EDI updates for a load in Alvys:

  1. Open an EDI load in the system.

  2. On the Load Details page, scroll to the Trips / Stops section, where pickup and delivery stops are listed.

  3. Expand a stop and click into an individual stop, either pickup or delivery.

  4. The Share EDI Update button will appear on the stop card. Note that even if the stop is in the correct status (Arrived, Picked up, or Empty), the button will only appear if the EDI integration is properly configured to allow updates for that load.

Notion Image

By default, this authorization is conferred upon the Support, Partner Admin, Admin, and Operation Manager roles. Conversely, this specific permission is not assigned by default to the Dispatcher, Biller, Sales Agent, Data Entry, Office Admin, Safety, or Driver roles.

Best Practice: Grant EDI Share to users responsible for managing EDI relationships and controlling the sharing of load visibility data with trading partners. If your company automates EDI visibility sharing, this permission is typically only needed for manual overrides or to initiate updates in exceptional cases.

Frequently Asked Questions (FAQs)

Q: Do these permissions work if my company does not use EDI? A: No. Tendering is entirely EDI-based. Without active EDI integrations with your shippers or trading partners, these permissions will have no functional effect in the system.

Q: Why does the Data Entry role receive Participate In Tender by default while Dispatchers do not? A: In many workflows, Data Entry staff are responsible for the initial intake and conversion of EDI tenders into active loads. Dispatchers usually manage the loads after they have been accepted, though they can be granted this permission manually if they need to make capacity-based decisions.

Q: What specific actions can a user take on the Tender Board? A: Users with the Participate In Tender permission can view tender details, review EDI history, and either accept or reject incoming load offers.

Q: Does the Tender Board update automatically when a new offer arrives? A: Yes. The Tender Board uses a real-time connection to the shipper hub. New tenders and updates to existing ones will appear instantly on the board without requiring a page refresh.

Q: What is the purpose of the EDI Share permission? A: EDI Share allows a user to send outbound status updates to trading partners, such as arrived/departed notifications, appointment confirmations, and location tracking. This automates the visibility process for large shippers.

Q: Can a user access the Tender Board without the Participate In Tender permission? A: No. Access to the Tender Board is strictly guarded. Without this permission, the route is blocked, and the user will be unable to navigate to the page.

Q: Why is EDI Share not assigned to Data Entry by default? A: Data Entry typically handles the "intake" of loads. EDI Share is an operational function used to send updates as a load progresses, a task usually handled by Dispatchers or Operations Managers who monitor real-time shipment status.

Q: How do I share an EDI update for a specific stop? A: With the EDI Share permission, navigate to the Trips/Stops section of an EDI load, expand the specific stop, and click the Share EDI Update button. This button only appears if the EDI integration is properly configured for that load.

Q: Is manual load creation the same as Create Tender? A: No. Manual load creation is an internal process within Alvys. Create Tender sends a formal, electronic EDI 204 message to an external trading partner’s system, creating a legal and operational commitment.

Next Steps

⏭️ Proceed to the Additional Load Permissions article to understand how to manage supplementary permissions that support load creation, pricing, and management. This includes permissions for Load Templates and Load Rate History.

Return to Collection

Did this answer your question?