Skip to main content

Credentials

Written by Product Management

This article is auto-synced from its in-app version in Tai.

Company admins only. This page is part of Settings, visible to users with the Company Admin role.

Bring your organization's own account with an external provider so your agents call that provider under your company's identity instead of a shared default. You enter each provider's credentials once, in Settings → Credentials, and every connector that uses that provider picks them up — today, the Passolution connectors.

The Credentials settings page, listing four provider cards — Passolution Travel Regulations API, marked "Nezasa default", above Passolution In-Destination Travel Events, TripBuilder APIs, and TripBuilder Data Warehouse, each marked "Built-in"

When you'd use this

Add your own Passolution access token when your organization has its own Passolution subscription and you want lookups to run against your account rather than the included default. Until you add one, an included Nezasa-provided default token may apply automatically, so the connectors keep working either way.

Steps

  1. In the Workbench sidebar, open Settings, then Credentials.

  2. Find the Passolution card. The status line shows which credential is in use — your organization's own token, or the Nezasa-provided default.

  3. In your own Passolution account, go to Account → API Access and click Create New to generate an access token.

  4. Paste the token into the Access token field and click Save.

  5. The token is verified with Passolution immediately — a brief "Testing the connection…" state shows while it checks. If Passolution rejects it, nothing is saved, and you can correct and retry.

  6. Once saved, the card shows Verified with the time of the last check.

Re-testing a saved credential

Click Test on the card to re-check a token you already saved — for example, after rotating it in your provider account. The card updates to show whether the provider still accepts it, without you re-entering the token.

Removing your credentials

Click Remove on the card to delete your organization's token. The connectors then fall back to the Nezasa-provided default, if one is available for your company.

Connecting an OAuth 2.0 provider

Some providers don't hand out a token to paste. Instead they give you a client ID and secret and ask a person to sign in and approve access. A connector built for such a provider shows a Connect button on its credential card.

  1. Ask the provider to register the redirect URL shown on the card (it ends in /oauth/callback) for your client.

  2. Enter the Client ID, Client secret, Authorization URL and Token URL from the provider, plus any Scopes they require, and click Save.

  3. Click Connect. You are sent to the provider to sign in and approve access, then returned to the Workbench.

  4. The card shows Connected, with who connected it and when. Tokens are renewed automatically from then on.

Most providers work with the defaults. If yours documents otherwise, three optional settings adjust the flow:

  • Client authentication: how the client ID and secret reach the token URL. basic (default) sends them as an HTTP Basic Authorization header; body sends them as client_id and client_secret in the request body.

  • Token request encoding: form (default) sends the token request as application/x-www-form-urlencoded; json sends it as application/json.

  • Extra authorization parameters: additional query parameters for the authorize URL, written as a query string, for example audience=api&prompt=consent. The Workbench sets client_id, response_type, redirect_uri, state and scope itself, so these can't be overridden here.

If the provider withdraws access, the card shows Access revoked. If the provider issues no renewable token and the current one runs out, the card shows Expired. Either way, company admins receive one email. Click Reconnect to approve access again. Saving new client settings disconnects the account until you connect again.

Tips and limits

  • One credential per provider covers every connector that uses that provider, so you don't set it up per connector. An OAuth 2.0 connection belongs to the connector that declares it, so connect each such connector on its own card.

  • If you don't see Credentials under Settings, ask a company admin — the page is theirs to manage.

  • Your token is stored encrypted and is never displayed again after you save it — check it in your Passolution account if you need to see it again.

Related

Related Articles
Did this answer your question?