Start with a small, working CRM workflow.

Account access and recovery

After registration, open the verification message sent to your email address. Use the newest valid link, choose and confirm your final password, then sign in with that password. If the message is delayed, check spam and use the verification request on the account recovery screen. Registration may remain unavailable while the sender and product terms are being approved.

Recover account access or request verification. Password-reset links are one-use and expire. A password reset does not turn off an enrolled authenticator; enter its current code when asked. Platform accounts and a lost authenticator require HAT's identity-checked support process. An administrator in one workspace cannot recover an account shared with other workspaces.

Your first workspace

1. Open Settings and confirm your company name, time zone and currency.
2. Invite a colleague from Settings. Give each person their own account, then review Access levels and the role hierarchy with a non-owner account.
3. Create one Company and one Contact with fictional sample details. Link them before importing larger lists.
4. Review the pipeline stages, create one Deal, assign its owner and add a next action. Check that another permitted colleague sees the intended records.
5. Use the dashboard setup checklist and Company Health to find incomplete records. Try a report/export with the same non-owner account.
6. Keep your acceptance sample separate from customer data. Remove test links and accounts when the onboarding check is complete.

Membership administration and module permissions are separate controls. A button hidden by the interface does not grant access; ask your owner to adjust an appropriate role when a permitted action is unavailable.

Import contacts and companies carefully

Contacts and Companies offer CSV preview/import. Start with a small sample; the current importer accepts at most 1,000 rows per request and a limited set of supported columns. Review matched fields and required names before confirming. Check the result for duplicates before repeating an import.

These CSV paths do not migrate a complete legacy CRM, Deal history, attachments or all relationships. Ask for a reviewed migration plan for those records. Keep an independent copy of the source file and reconcile imported counts and relationships before relying on the workspace.

Connect services after a controlled test

Only connect a mailbox, accounting, signing or CRM provider that your company is authorized to use. Verify the displayed company/account and environment first. Use a designated test mailbox and sandbox accounts for the initial delivery, signing and accounting checks.

HubSpot imports supported records in one direction; it is not a complete two-way synchronization. Accounting and signing statuses can require explicit refresh. Generating a signing session does not establish that a signed document returned to BuildOS. A payment-page handoff does not establish that payment was collected. Review supported behavior with HAT before including it in your operating process.

Prepare a support request

The dedicated support/privacy address and response commitments are awaiting business approval. Until supplied, use the existing HAT contact form to request a BuildOS conversation. Do not use it to send secrets or private customer files.

• Include the workspace name, affected screen, approximate time and time zone, and what you expected to happen.
• Include an error/request identifier if the application shows one. Describe whether the problem affects one user or the team.
• For access recovery, state that you need account help. Never include a password, authenticator code, verification/reset link or passkey recovery material.
• For a provider failure, retain the original operation and ask for review. Do not create a second invoice, envelope or email to work around an uncertain first result.

If you suspect unauthorized access, notify your company owner promptly, revoke affected shared links where permitted, and contact HAT for the identity-checked incident process.