Skip to main content
Connect Pumble with an API key from the workspace’s API add-on to sync workspace members with their roles and status (bots excluded), channels and user groups, and run access reviews. Read-only. Data feeds into your Access accounts and Inventory pages.
Read-only access. DSALTA only reads data from this integration. It never creates, modifies, or deletes anything in your environment, and every remediation step is performed by your team directly in the third-party product.
What you’ll see. The Access page lists the members of the one Pumble workspace the API key was generated in, with their name (or their email address when Pumble carries no name), email, and their Pumble role in the role column (Owner, Admin, Guest, or Member for a regular user or when no role is reported). Pumble’s built-in bot and add-on bots — including any row with no email address or an @pumble.app address — are left out, as is any row whose status reads as an invitation. A member Pumble reports as activated is shown as Active; any other status is shown as Inactive. Pumble reports no join date, so each row is stamped with the date of the sync. Pumble reports no per-user MFA state, so the MFA column is blank (shown as a dash).
DSALTA collects this integration’s data when you connect it — you can refresh it at any time with Sync from integrations on the Integrations page. The compliance checks below re-run once a day at 02:00 America/New_York.

​
What DSALTA reads

DSALTA reads the workspace member list — names, emails, roles and status — which appears on your Access page; and your Pumble channels (type, whether it is the main channel, archived or hidden, its member count and description) and user groups (member count), which appear on your Inventory page. Direct-message and self conversations are not inventory and are skipped. Channels and user groups are read best-effort after the member list; user groups appear once you have created one. Messages, reactions and scheduled messages are never read.It calls these endpoints of Pumble’s API add-on on pumble-api-keys.addons.marketplace.cake.com:
  • /myInfo
  • /listUsers
  • /listChannels
  • /listUserGroups
Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Pumble environment.

​
Troubleshooting

The key is invalid or was deleted — Pumble answers Invalid key — or the user list returned no human member. Generate a key through the workspace’s API add-on (+ Add apps → API → Install, then API → Add API key) and connect again.
A key is bound to the workspace it was generated in, and DSALTA syncs that workspace — it cannot tell which workspace you meant. If the user who generated the key belongs to several workspaces, generate the key while inside the right one, then disconnect and connect again. Note that disconnecting permanently deletes the data already collected from Pumble.
Channels and user groups are read best-effort after the member list: a failure on either call leaves that part of the Inventory page empty without failing the sync, and a workspace with no user groups has none to list. Click Sync from integrations on the Integrations page to retry.
Open Integrations in the DSALTA sidebar, stay on the Connected tab, and click Manage on the integration’s card. Open the Status tab: it shows either Connected and working properly or Connection issues detected.Use the Status tab, not Overview — Overview always reports Connected regardless of the real state.
On an integration-powered check, Failed normally means DSALTA was blocked rather than that you are non-compliant. Open the test, go to Source Data, and read the result code: 403 is a missing permission, 428 is a setting DSALTA still needs, 500 is a failure on DSALTA’s side.A real compliance gap shows 207 and leaves the test looking Completed. See Understanding Test Results.
Compliance checks re-run once a day at 02:00 America/New_York. To refresh sooner, open Integrations → Connected and click Sync from integrations at the top right — it refreshes every connected integration at once.
There is no Reconnect, Repair or Refresh Token button. The only repair available is to disconnect and connect again.
Disconnecting is destructive and cannot be undone. DSALTA removes the access records, inventory, vulnerabilities, code changes, incidents and device records collected from this integration, and deletes the test results tied to the connection. Export anything you still need as audit evidence first — see Integration errors.
That is expected. Configure scope is read-only — it shows what DSALTA is permitted to read, and has no Save action. To change what DSALTA can see, change the permissions on the credential in the third-party product, then disconnect and connect again.