Support

Where to find help with Tagaris, what each channel is for, and what to include when you write.

Goodhall Solutions is a small company, so replies come from the people who build Tagaris. The documentation answers most questions; the channels below cover the rest.

Free tier

The documentation, the public issue tracker for bug reports and feature requests, and the status page. Beta keys for device sync and the Entra people import come from [email protected].

Team licences

Everything on the free tier, plus email support at [email protected]. Licence questions (a key that has not arrived, a licence file for an air-gapped server, moving a licence to a new server) go to the same address.

Start with the documentation

Each guide carries the troubleshooting for its own topic. The main ones:

  • Quickstart: first steps, a location, a person and your first asset.
  • Self-hosting: the install, environment reference, volumes and troubleshooting.
  • Upgrading: version tags, pinning, the steps and rolling back.
  • Backups: schedules, encryption, offsite copies, restore and moving servers.
  • Importing: CSV imports, the Snipe-IT and Halo presets, and the Entra people import.
  • Single sign-on: Microsoft Entra ID setup, role mapping and requiring single sign-on.
  • Two-factor authentication: enrolling, backup codes, the policy and recovery.
  • Device sync: pulling devices from Microsoft Intune and Jamf into the review queue.
  • API: the REST API, keys, scopes and endpoints.
  • Licensing: applying a key, air-gapped licence files, renewals and lapses.
  • Roles: SuperAdmin, Admin, Editor and Viewer, and break-glass recovery.
  • Stock: accessories, components and consumables, with low-stock alerts.
  • Reports and alerts: built-in reports, the daily digest and webhooks.

The full index is at docs.tagaris.co.uk.

The other channels

Issue tracker

Bug reports and feature requests go to the public tracker on the deployment files repository: github.com/goodhall-solutions-ltd/tagaris/issues. Search it first; the problem may already be there. Anyone with a GitHub account can open an issue, free tier included.

Email support

Team licence holders can email [email protected]. Include the details from the checklist below. Replies come from the people who build Tagaris.

Status page

status.goodhallsolutions.co.uk shows the current state of Goodhall Solutions services. Your own install is self-hosted and is not on it, but if a licence activation, the trial form or the demo is failing, check there first.

Security reports

Vulnerabilities go to [email protected], never the public tracker. Say what you found, how to reproduce it and the impact you think it has. We aim to acknowledge within 3 working days and ask for reasonable time to fix before public disclosure. See the security page.

Before you write

A report with these in it gets a useful reply first time.

  • The Tagaris version or image tag you are running, for example goodhallsolutions/tagaris:2.4.1, and the app version if the iOS app is involved.
  • How it is installed: the two-container compose setup, the bundled single container, an external PostgreSQL server, or plain docker run.
  • What you expected to happen.
  • What happened instead, with any error text copied exactly as shown.
  • The relevant lines from the container logs (docker compose logs app) from around the time of the problem.
  • No secrets. Remove BETTER_AUTH_SECRET, licence keys, passwords and client secrets from anything you paste. Environment files and backups contain them.

Most answers are already written down

The documentation covers installing, upgrading, backups, imports, sign-in and the API, each with its own troubleshooting.

Read the documentation Email support