Do I need to finish setup before I can use the app?
You can sign in and look around right away, but HighSlack works best after setup is complete. Add your district, gear type, and at least one permit before you start logging real deliveries.
Short answers for the questions users ask most often about setup, sync, scan, crew workflows, billing, and support.
You can sign in and look around right away, but HighSlack works best after setup is complete. Add your district, gear type, and at least one permit before you start logging real deliveries.
Yes. You can sign in on multiple devices with the same account. Server-backed data is shared across those devices after sync completes.
That is intentional. Disabled accounts now show a specific disabled-account message so users do not waste time retrying the same credentials.
Yes. Use Forgot password on the sign-in page. HighSlack emails a reset link that expires after 1 hour.
Yes, but the experience depends on where you are using it. Mobile supports real offline entry and queued sync. Web currently supports browser-side offline queueing on /tickets/create.
Open /tickets/create while online at least once, then keep using that page if the connection drops. Entries saved there stay in that browser until signal returns and the page can sync them.
Reconnect, leave the page or app open briefly, and let HighSlack sync. On the web delivery form, you can also click Sync Pending.
Browser offline queue data is local to that browser profile. It is not shared until it syncs to the server.
Yes. If browser storage is cleared before sync finishes, queued entries can be lost. The mobile app is still the better choice for heavy offline field use.
Permits are managed from Settings. Older permit routes redirect there.
Yes. HighSlack has an offline or client-side scan flow and, when configured, an enhanced server-side scan flow.
Retake the photo in better light, fill the frame with the ticket, and try offline scan first. If enhanced scan is unavailable on the server, HighSlack now returns a clear fallback error instead of crashing.
Yes. Use the season import flow from Deliveries, or the Audit tool if you are reconciling processor statements against deliveries already in the app.
Usually it is an unsupported processor layout, poor scan quality, or a malformed or image-only PDF. Repeated failures with the same file should be treated as a parser support issue.
Each crew member gets a unique tokenized onboarding link. They use it to submit personal details and sign the contract.
Open the crew member record and reset the token to generate a fresh onboarding link.
Yes, when ENCRYPTION_KEY is configured correctly. That key is required for SSN-related workflows and tax form handling.
Yes. There are crew 1099 and tax-form flows in the app, but they still depend on complete payer info, crew legal details, and correct year and share data.
Captain is the main self-serve paid tier.
Fleet is currently positioned as a higher-touch contact or support plan for larger operations. It is not yet a full in-app organizations or teams collaboration model.
Send the account email, platform, feature or page, time of failure, online or offline status, screenshot or error text, and any landing number, district, or year tied to the issue.