Data that is accessed, used, and stored by the integration, and for what specific purposes.
All data is processed locally in the browser. No data is sent to or stored on external service. No external services make API requests or fetch data from Zendesk. All API requests are authenticated using the user's current Zendesk session.
Below is a description of the data that is accessed by specific apps:
Ticket Fields Importer
This app will have access to the ticket fields in your account and to the uploaded file. This data used to perform the update.
Save as Draft
A custom ticket field is created and data is stored in that ticket field. The field is created, read, and updated by the app.
The app will access the tickets where it is visible, the current comment on the ticket, and search through ticket fields to find the correct one.
This information is used to store the draft comment information in the ticket field so it can be retrieved later.
Hide Ticket Forms
The Hide Ticket Forms app will access the active tickets being viewed by the agent, including the ticket fields of that ticket. In API terms, the ticket form information is accessed through the ticket fields, and this is used to aide in hiding the ticket forms.
Disable Ticket Fields
Ticket Form and Field information of the current ticket is accessed in order to disable the correct ticket fields as per the settings.
Default Settings
Brand, Form, and Group are set on the ticket based on the app settings.
Extended Macros
All macros from the account are fetched in order to provide the extended macro functionality. Various ticket and requeester datas are read and/or updated based on the specific macros settings, including the following:
Ticket ID, tags, comment, collaborators (CCS), via, requester id, requester emails, requester phones, ticket audits, custom fields, recipient, problem ID, sharedWith, status, due date, organization, skills.
Comments
0 comments
Please sign in to leave a comment.