Permissions and Data Access

Dingdang can use supported actions through connected Apps. What it can read or change depends on the connector’s available actions, the connected account’s permissions, and team settings.

Check the connection

Open Connections and use the account intended for the task. Review the requested access during authorization. Connecting one account does not imply access to every workspace, folder, channel, or record in that service.

Adding Dingdang to team chat and authorizing a business App are separate steps. If a task needs CRM records or documents, connect the service that owns those records.

Define the task’s scope

For a read-only task, specify the source, date range, fields, and expected output. Ask for source links or record references so you can check the result.

For changes, also specify the destination and affected records. Ask Dingdang to prepare a draft when you want to review the proposed changes first. Before requesting publication, sending, or deletion, check the recipients, content, and scope.

Do not paste account passwords or raw access tokens into a task message. Use the connection flow for account authorization.

When access is incomplete

Check whether the correct account is connected, whether it has access to the relevant records, and whether the App supports the required action. A supported App does not imply that every feature of that service is available through Dingdang.

For help, provide the App name and a description of the failure to support. Avoid including passwords, tokens, or unrelated private records. See the privacy policy for the published privacy terms.