Passportal: document names on your service desk tickets
Create a Passportal access key, paste it into Current, and each matched company's Passportal document names appear on its service desk tickets beside IT Glue's. Current reads names only, never a document's text or a password.
On this page · 8 sections
Connect Passportal and each partner's Passportal document names appear on their service desk tickets, in the same Docs and passwords panel as IT Glue's, so the engineer finds the right runbook without searching another tool. Current reads the names only.
What it does for you
| Where in Current | What you get |
|---|---|
| Service desk tickets | The Docs and passwords panel lists the company's Passportal document names, each marked Passportal, in the same groups as IT Glue's. A name opens Passportal in a new tab. |
| Ask Current | People who can see the service desk's documentation can ask for a company's document names, and Ask Current lists Passportal's beside IT Glue's. It never sees a document's text. |
Before you start
- The Passportal card shows only where the service desk is on, because the names appear on service desk tickets.
- Connecting, matching and disconnecting Passportal are Tenant Admin actions.
Create an access key in Passportal
- 11 · Open API Key ManagementIn Passportal, open Settings, then API Key Management, and create an access key for Current with the documents API.
- 22 · Copy both valuesCopy the access key ID and the secret access key. Passportal shows the secret once, so copy it before you leave the page.
Connect it in Current
- 1Open the Passportal cardIn Current, open Settings › Integrations (Tenant Admins only), pick Passportal in the Documentation group to open its card, and press Manage.
- 2Paste the address and the keyEnter your Passportal address (the address in your browser when you use Passportal, for example https://us-clover.passportalmsp.com), the access key ID and the secret access key. Current accepts only an https address on passportalmsp.com, so the key is never sent anywhere else.
- 3Press Test connectionCurrent asks Passportal for a short-lived token and reads one entry of the document list to prove the key works, and only then stores the key, server-side. The token is used for that one request and is never stored.
Match Passportal clients to your companies
Once a day, and when you press Sync now on the card, Current reads which Passportal clients exist. If your Passportal lists its clients by name, Current matches each one to the company with the same name (lowercased, with punctuation and Inc/LLC/Ltd-style suffixes stripped) when exactly one company fits. If it does not, Current lists the client IDs your documents carry and you match each one by hand. A match or an Ignore you set is never overwritten by a later sync.
- 1Open the mapping listOn the Passportal card, press Manage. The mapping list opens on the Unmapped tab.
- 2Map each clientPress Map on a client and pick its company. Tickets for that company then find its documents.
- 3Ignore anything internalFor a client that should never map (your own office, a template), press Ignore. Unmap and Un-ignore undo either one later.
What Current reads, and what it never keeps
Each time someone opens Docs and passwords on a ticket, Current asks Passportal for that company's document list and keeps, for that one answer, each document's ID, name, type and template name. A document's description is dropped, and its body is never asked for: no request Current can send reaches a document's text, and none can create or change anything in Passportal. No document is stored in Current. What Current stores is the key (server-side, never shown again) and which Passportal client is matched to which company.
Who sees it
Engineers, dispatchers, vCIOs, project managers, service managers and tenant admins see Passportal document names on tickets they can open. Account executives, sales managers, finance and Partner Viewers do not. The check runs on Current's server for every request. Workspace admins also see Passportal's status under Settings › Service desk › Documentation (Connected, Not connected, or Failing with the reason), where Details opens its card in Integrations.
When something looks wrong
| What you see | What it means |
|---|---|
| Test connection refuses the address | Current accepts only an https address on passportalmsp.com. Copy the address from your browser while you are signed in to Passportal and paste it again. |
| Passportal rejected the API key | Passportal refused the access key. Create a new access key in Passportal under Settings, API Key Management, and reconnect it on the Passportal card. |
| A ticket says the company is not matched in Passportal yet | That company has no Passportal client mapped to it. Map it on the Passportal card's Unmapped tab, and every ticket for it finds its documents. |
| A ticket says Current could not reach Passportal | Passportal did not answer in time. Press Retry in a moment. |
| A ticket says Passportal is paused while billing is unresolved | Your workspace's billing needs attention, and Current does not read Passportal until it is resolved. |
| A ticket says nothing is written up for the company yet | Passportal answered with no documents for that client. |
| A document name opens Passportal's home page | That is expected. Passportal publishes no link to a single document, so Current opens your Passportal address and you open the document there. |
| There is no Passportal card in Integrations | The service desk is off in this workspace. Passportal's names appear only on service desk tickets. |
