WorkatoSight Provider Specific Terms Addendum
Last updated: 2026-06-26
This addendum supplements the Flowdence terms for WorkatoSight for Confluence.
Workato access
Section titled “Workato access”Customers configure the Workato API origin, permitted Workato browser hosts, and Workato credential used by WorkatoSight. Customers are responsible for ensuring that the credential is authorized for the Workato metadata they want to document in Confluence.
Credential handling
Section titled “Credential handling”Workato credentials are stored with Atlassian Forge secret storage. Flowdence support will not ask customers to provide Workato credentials through tickets, chat, email, screenshots, or page content.
Cached metadata
Section titled “Cached metadata”WorkatoSight caches selected Workato metadata so Confluence pages remain stable and readable. Cached metadata can include Projects, Folders, Recipes, Connections, Lookup Tables, API Collections, API Endpoints, API Clients, API Keys, runtime rollups, and related freshness state. Secret-like fields are redacted before cache, logs, UI, screenshots, or support evidence.
Customer-controlled upstream systems
Section titled “Customer-controlled upstream systems”The customer’s Workato tenant is a customer-controlled upstream system. Customer choices about Workato region, tenant configuration, content, users, and credentials are outside Flowdence control.
DPA role model
Section titled “DPA role model”For customer End-User Data processed through WorkatoSight, the customer is controller and Flowdence is processor. Flowdence is an independent controller for limited business-operational data such as support, billing, security, and abuse-prevention records.
Data deletion assistance
Section titled “Data deletion assistance”Customers can uninstall the app or contact Flowdence Support for help removing WorkatoSight configuration, credential references, cached metadata, or support records.
Contact
Section titled “Contact”Flowdence Support: https://flowdence.io/support