Skip to content

WorkatoSight Data Handling Disclosure

Last updated: 2026-06-26

WorkatoSight uses Atlassian Forge to store app configuration, Workato credentials, cached Workato metadata, and refresh state needed to render Confluence dashboards, macros, bylines, and documentation-coverage views.

CategoryExamplesPurpose
Confluence contextSite, space, page, macro, and page-link contextRender dashboards, macros, bylines, and coverage findings
ConfigurationWorkato API origin, browser host patterns, refresh preferences, timezoneConfigure each Confluence space
CredentialWorkato API credentialStored with Forge secret storage for admin-approved tests and refreshes
Cached Workato metadataProjects, Folders, Recipes, Connections, Lookup Tables, API Collections, API Endpoints, API Clients, API Keys, runtime rollupsRender cache-backed Workato context in Confluence
Operational stateCache freshness, refresh status, partial-access limits, sanitized errorsShow reliable status and support troubleshooting
Support dataSanitized screenshots, timestamps, page URLs, and ticket detailsResolve customer support requests

WorkatoSight stores app data in Atlassian Forge hosted storage. Workato credential values use Forge secret storage. Backend egress is limited to Workato hosts configured by the customer and permitted by the app manifest.

WorkatoSight redacts OAuth tokens, access tokens, refresh tokens, private keys, signing keys, passphrases, bearer material, API keys, credentials, passwords, and token-bearing URL query values before data reaches cache, logs, UI, screenshots, or support evidence.

Customers control which spaces are configured, which Workato credential is used, which refresh preferences are enabled, and which Confluence pages contain WorkatoSight macros or Workato links.

Do not send Workato credentials or token-bearing URLs to Flowdence support. If a credential is exposed, rotate it in Workato and update WorkatoSight Configuration.