HelpCheck the context before changing data
- Confirm the company shown on the application or company record.
- Check your role and application visibility with your company admin.
- Clear table filters and search text that may hide the expected record.
- Refresh the relevant screen after another team member changes data.
- If the issue is public-facing, open the exact shared link in a private browser window and compare it with the company being configured.
A recruiting company’s own configuration is separate from a linked carrier’s configuration. A saved company change does not necessarily alter a form belonging to another company.
A button, tab or record is missing
| Symptom | What to check |
|---|---|
| I cannot see settings or an integration tab | Company administration actions are role-dependent. Check your company and admin role, then whether subscription access is usable. |
| I cannot find an application | Check company scope, assignment visibility, search, status and archived filters. A recruiting user does not inherit a recruiting admin’s cross-carrier access. |
| I cannot edit driver information in the staff record | The Information view is read-only. Status and assignment use their own controls; Save on this screen applies to internal custom fields. See application details. |
| A note or task has no Edit button | Creator-based edit permissions apply. Open the relevant notes and tasks guide before assuming the record is broken. |
| A user cannot be added | Check both company-admin permission and available staff seats in Billing. |
A public form does not reflect the expected setting
| Symptom | Next step |
|---|---|
| I changed Requirements but applicants can still continue | Requirements is welcome-page display copy. It does not add validation or automatically reject applicants. See form settings. |
| A required custom field is not on the public form | Custom fields are internal application fields. Their Required flag is for internal editing, not public-form questions. See custom fields. |
| A new consent is absent | Check the application company, consent type, Active flag and whether the application already has an acceptance/processed record. New consents start inactive. See consents. |
| An edited consent does not appear again to a driver | Editing a consent does not reset existing acceptance. Saved PDFs are not silently replaced. See consent changes. |
| I selected Signature but still see an introduction | The current Signature link is an alias into the application page, not a guarantee of skipping identity and form steps. See sharing formats. |
| The public history step will not continue | Check required fields, date order and uninterrupted three-year coverage. See employment and other history. |
A connection is configured but nothing arrived
- Facebook: check the connected account, selected page, form activation and field mapping. Sync Forms and Sync Leads do different jobs. Follow Facebook setup.
- Webhook: confirm the correct inbound endpoint, required authentication and paths matching the received JSON. A sample payload prepares mapping choices; it is not a substitute for a delivery. Follow inbound webhooks.
- Telegram: check that the bot is in the intended group, the connection is complete and notifications are enabled. A successful connection queues a test message. Follow Telegram setup.
- Employment verification: check the specific history item’s status and its generated employer-specific authorization file. Follow verification requests.
If an error remains, record the company, screen name, action used, approximate time and exact error text. Share the minimum information needed with your company admin or support contact. Keep API tokens, webhook secrets, connection commands and sensitive driver data out of public screenshots or support comments.