Settings

Stored under /var/lib/ticketmagic. Nothing is written to the repository.

This lab instance is bound to 0.0.0.0. Manage credentials are not saved from this page — place JSON under /var/lib/ticketmagic over SSH (see deploy/linux/README.md). Ticket work still uses credentials already on disk.

ConnectWise Manage API

Create an API member in Manage under System, Members, API Members, then generate a key pair for it. The client ID comes from the ConnectWise developer portal.

API URL

Your site base. The /apis/3.0 suffix is added automatically.

Company ID

Public key

Private key

Client ID header

Your Manage identity

API keys authenticate as the API member, so without a member identifier every note and time entry is attributed to that member instead of you.

Member identifier

Save and test the connection to pick from a list. If the member list stays unavailable, the API member's security role lacks Inquire on Members and the identifier must be typed.

Defaults for time and scheduling

Default board

Open this board when the app starts

Time entry work type

Billing follows this work type in Manage. Service tickets always schedule as Service.

Status picker

Order of the ticket status dropdown and the board Set status menu. Names are matched on each board, so a status that does not exist there is skipped.

Hatz AI

Used by the Refine button on notes and by alert triage on the board. Ticket text contains client data, so nothing is sent until you press Refine or Triage incidents. The key stays in the local Responses settings file, not in git.

Enable Refine and alert triage

Provider

Model

Saved API key

Replace key

Key comes from Workspace › API Keys in Hatz. Save first if you just pasted a new key.

API pacing

Requests are paced with a sliding window so a busy board view stays inside Manage's published limits.

Requests per minute

Requests per hour