NetLock RMMNetLock RMM Docs
IV — Administration

Zendesk

Connect NetLock RMM to Zendesk Support: alerts become tickets of the mapped organization with an internal first comment, the all-clear adds an internal note and solves the ticket, organizations can be imported as tenants.

Zendesk

Requirements

  • A Zendesk Support account. The request limits depend on the plan.
  • An OAuth client of the kind Confidential, created by an admin in the Admin Center under Apps and integrations → APIs → OAuth clients. NetLock uses the client credentials grant with the scopes tickets:read tickets:write users:read users:write organizations:read groups:read. If the client restricts its allowed scopes, they have to include these.
  • Tokens of this grant act for the admin who created the client. They stop working when that admin is deleted or loses the permission, so use a dedicated admin account.
  • As a fallback, an API token with the e-mail address of the same kind of account. Zendesk has marked API tokens as deprecated, without a date.
  • The account behind the client or the token has to be an admin, or an agent in a custom role that may manage end users. The test of the connection checks this.
  • A ticket can only be solved with an assignee, so this account has to be a member of the group the tickets are in.

The OAuth client belongs to your Zendesk account and stays there.

Setup

  1. In Settings → Integrations, open the Zendesk tile and choose Connect.
  2. Enter the Instance address, for example https://yourcompany.zendesk.com. Only addresses under zendesk.com are accepted, so host-mapped domains do not work here.
  3. Enter the OAuth client identifier and the OAuth client secret. Without a client, enter the Account e-mail address and the API token instead.
  4. Under options, choose a Group if tickets should go to one. If left empty, the rules of the account decide.
  5. Map each tenant to an organization, or import organizations as tenants. Tenants without a mapping are not included. Severities follow the priorities Low, Normal, High and Urgent unless they are mapped.
  6. Activate the connection.

What goes to the vendor

For every alert that passes the filter of the connection: a title, the severity, tenant, location and device name, the source, first and last time seen, the alert text, and a link to the web console if the public console URL is set. Check that this matches your data processing agreements before you activate the connection.

For each organization that receives tickets, NetLock also creates one end user named NetLock RMM, with the external id netlock-company-<organization id> and no e-mail address.

What happens to a ticket

  • An alert becomes a ticket of the mapped organization. The reference NetLock-Alert-<id> is stored in the external_id of the ticket, which NetLock uses to find it again.
  • A ticket belongs to an organization through its requester. The requester is the end user of that organization. Because that user has no e-mail address, triggers cannot send any e-mail, and end users need no license. No e-mail goes to the customer, but where an organization shares tickets in the help center, its users may see the subject.
  • The API user remains the submitter, and the first comment is an internal note.
  • When the alert ends, the ticket gets an internal note and is set to Solved if nobody is assigned. Zendesk cannot solve a ticket without an assignee, so the account of the connection becomes the assignee, which also appears in reports per agent.

The behaviour is set in the Settings tab, see A.14.4. NetLock never closes a ticket whose status somebody changed in the meantime, and it never deletes anything at the vendor.

Known limits

  • If required fields prevent the ticket from being solved, or the account is not in the group of the ticket, the note is added and the ticket stays open. The history shows close_refused.
  • A ticket in the status Closed cannot be changed, so an all-clear leaves it as it is.