SECURITY / CLEAR ACCESS

Give each person the access their work calls for.

Job4Site combines authenticated accounts, company-scoped Firestore records, app roles and permissions, and server-validated QuickBooks services for a small HVAC team.

COMPANY WORKSPACE CONTEXT
JT
Jordan TaylorActive team member
SIGNED IN→WORKSPACE SELECTED→APP ACCESS APPLIED
CustomersJobsProposalsInvoices
HOW ACCESS WORKS

Simple for the team.Specific about the controls.

These are the identity, data, role, and backend boundaries implemented in the current product.

01IDENTITY

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.

02BOUNDARY

Core records organized by company ID

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.

03CONTROL

Roles for everyday app access

Owners and admins can set supported app permissions for proposals, invoices, customers, products, staff, templates, and settings. Subscription management is owner-only.

04SERVICE

QuickBooks actions validated on the server

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.

ROLES + PERMISSIONS

Give each role a clear workspace—not every screen.

Company roles include owner, admin, office manager, customer service, sales, and technician. In-app proposal and invoice access can be scoped separately, with additional permissions for customers, catalogs, staff, templates, and settings.

Proposal permissionsNone, view own, edit own, or full in-app access
Invoice permissionsNone, view own, edit own, or full in-app access
Catalog controlsSeparate product and service editing permissions
Company controlsStaff, templates, settings, and owner-only subscription access
Record rulesNon-admin job edits require creator or technician assignment; proposals and invoices require creator access
DATA / 01

Core business records are organized by company.

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.

FILES / 02

Image uploads require an authenticated account.

Job photos and product, proposal, and template images require sign-in. Upload rules restrict these files to image formats under 10 MB.

INTEGRATIONS / 03

QuickBooks credentials stay off the client.

QuickBooks connection and API operations verify signed-in identity and company membership on backend services. Integration tokens are stored in server-only records.

CLEAR SECURITY INFORMATION

Documented controls. No borrowed badges.

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.

FROM CLEAR PROPOSAL TO FINAL INVOICE

Set up access around the way your HVAC team works.

Choose company roles, adjust in-app permissions, and give the office, sales team, and technicians a focused place to work.