Connector permissions and privacy
Review provider permissions, use the narrowest suitable account, and remove access when it is no longer needed.
Connector access is granted through the external service. The provider’s authorization screen is the best place to see the permissions requested for that connection.
Use the least access that works
Choose an account intended for the task, limit the data scope when the provider offers that choice, and avoid personal or production accounts for testing. Never paste passwords, access tokens, or secret keys into Kuse content.
Separate reading from external actions
Reading records and changing them have different risks. Make Workflow instructions explicit about whether Kuse may only read data or may also create, send, update, or delete something in the service.
Review access over time
Revisit connected accounts when people change roles, a Workflow is retired, or a service reports an authorization issue. Disconnect access that is no longer needed and check the provider’s own account security page when you need to revoke it there as well.
Protect customer-facing examples
Screenshots and recordings must use demo accounts and fictional data. Hide account names, email addresses, organization names, tokens, and any customer content before publishing documentation media.