Overview
With the Envoy + Oracle GTM integration, Envoy automatically checks each visitor against the denied, restricted, and sanctioned party lists configured in your Oracle Global Trade Management tenant. When a visitor is invited or signs in, Oracle GTM evaluates their information and returns a result to the visitor entry flow. You can screen all visitor types or only selected flows, and you can optionally screen the visitor's Company field in parallel with the individual.
PREREQUISITES
You must have an active Oracle GTM (Oracle Transportation & Global Trade Management Cloud) subscription with restricted-party screening enabled.
A staged integration user in Oracle GTM provisioned for the REST API using HTTP Basic Auth (not a regular SSO / UI login). SSO and OAuth are not supported by this integration.
The integration user's GTM domain prefix (e.g.
COP,ACME) — the username must be supplied in the qualifiedDOMAIN.USERNAMEform.REST ACLs granted on the screening resources:
AdhocRPS(always); plusTradeParty/PartyScreening/SanctionedScreeningif using persistent-party mode.The customer's Oracle GTM REST API host (the host root is enough — Envoy appends the REST path automatically).
Requires the Envoy Visitors plan to install, plus additional pricing, contact Envoy Sales.
How visitors experience screening
Visitors have no way of knowing they're being screened or that they've matched. If a visitor triggers a match at the kiosk, they see a screen indicating someone is reviewing their responses.
💡Tip: Customize your pending approval screen to let visitors know someone will be reviewing their information.💡
If an invite triggers a match, the invitation email is held until an admin reviews and approves it.
💡Tip: Proactively disclose screening via a disclaimer in invite emails or Envoy's data-privacy features.💡
What happens when there's a match
When a visitor returns a match, Envoy notifies the admins designated to receive alerts (via their preferred notification channels, configurable per flow). The visitor record is not approved and shows a Visitor failed screening note. Admins click Review in the sidebar to open the screening modal and view match details (match score, screening list / agency, denied-party ID, effective/expiration dates), then Approve or Deny. The entry's Approval history records who actioned it.
Enabling the Envoy + Oracle GTM integration
Step 1: Authorization
In the Envoy dashboard, go to Integrations, search for "Oracle GTM", and click Install.
Click Authorize to grant access to your Envoy visitors' data.
Enter your Username and Password.
Click Next Step to continue.
Step 2: Visitors
Select the visitor types (flows) to screen. All flows at the current location appear in the dropdown.
Confirm address collection (improves match accuracy; the field is auto-added to applicable sign-in fields if not already collected).
Select a Screening Mode:
Ad Hoc: Runs screens every guest, regardless of previous approved visits
Persistent Party: Preserves prior approvals in Oracle GTM across visits so cleared repeat guests aren't re-screened
(Optional) Enable Company screen to also screen the visitor's Company field (requires a Company sign-in field).
Click Complete Setup to finish configuration.
Screening settings
Envoy securely passes the visitor's full name, address, and (if enabled) company name to Oracle GTM. Oracle GTM fully owns the screening logic. The lists, matching rules, and thresholds are configured within your own Oracle GTM tenant. Envoy only transmits the data and displays the resulting outcome; it does not modify or influence how matches are evaluated. To reduce false positives or adjust matching rules/thresholds, you'll need to make those changes within Oracle GTM (or with Oracle support). Envoy cannot override match criteria on a customer's behalf.