Sign-in through Firebase Authentication
Job4Site uses Firebase Authentication for account access. The signed-in user's profile supplies the company and role context used by the app.
Job4Site combines authenticated accounts, company-scoped Firestore records, app roles and permissions, and server-validated QuickBooks services for a small HVAC team.
These are the identity, data, role, and backend boundaries implemented in the current product.
Job4Site uses Firebase Authentication for account access. The signed-in user's profile supplies the company and role context used by the app.
Customers, equipment, jobs, proposals, invoices, staff, and templates are organized under a company ID. The app reads that ID from the signed-in user's profile to select the matching workspace.
Owners and admins can set supported app permissions for proposals, invoices, customers, products, staff, templates, and settings. Subscription management is owner-only.
QuickBooks connection and API requests run through backend services that verify the signed-in user and company before acting. Integration tokens stay in server-only records.
Customers, equipment, jobs, proposals, invoices, staff, services, products, and templates are organized under a company ID. Firestore rules compare that ID with the signed-in user's profile and add record-level checks for core work.
Job photos and product, proposal, and template images require sign-in. Upload rules restrict these files to image formats under 10 MB.
QuickBooks connection and API operations verify signed-in identity and company membership on backend services. Integration tokens are stored in server-only records.
This page describes safeguards implemented in the current product; it does not imply a certification that has not been independently verified. Confirm any certification your business requires before adopting the service.
Choose company roles, adjust in-app permissions, and give the office, sales team, and technicians a focused place to work.