Support

When the workflow needs a hand, start here.

Track is designed for internal teams. Use your organization’s approved support channel for account, extension, data, or deployment issues, and include enough context for the administrator to reproduce the problem.

Account access

For login failures, password resets, or role changes, contact an authorized Track administrator. Do not share passwords or tokens in a support message.

Extension issues

Include the extension name, browser version, page URL, approximate time, and the visible error message. Remove personal data before sharing screenshots.

Data or workflow issues

Include the client, project, target, and action that failed. A short reproduction path is more useful than a general description.

Before reporting an issue

Confirm that you are using the current internal extension package.
Refresh the Admin workspace and sign in again if the page is stale.
Record the exact route, target, or user record involved.
Do not send passwords, bearer tokens, database credentials, or private candidate data.

What a useful report contains

Describe what you expected, what actually happened, the steps that led to it, and whether the issue affects one user or the whole team. If the problem is time-sensitive, state the operating impact without including confidential profile information.