Security control
Authenticated access
Private fieldGRID workflows require signed-in access, with account state checked before operational data is shown.
Security
fieldGRID uses Firebase services together with authenticated access, company membership checks, application integrity controls and database/file rules. Security is a continuing operating responsibility—not a badge or an unsupported promise.
Implemented foundations
The exact controls available to your organisation depend on the deployed product configuration and your account setup.
Private fieldGRID workflows require signed-in access, with account state checked before operational data is shown.
Company records are scoped through membership and company identifiers rather than a shared public workspace.
Sensitive manager actions use role and explicit membership checks to limit access to authorised users.
Firestore and Cloud Storage rules form part of the data-access boundary alongside application checks.
Firebase App Check is integrated to help distinguish approved application traffic from unauthorised clients.
Security-sensitive APIs and manager workflows are designed to verify identity and company access before acting.
Shared responsibility
Technology controls work best alongside clear company ownership and access practices.
Remove access promptly when roles or employment change.
Limit elevated responsibilities to people who need them for their work.
Use strong account practices and managed devices appropriate to your organisation’s risk.
Discuss security, privacy and procurement requirements before rollout so the fit is understood.
Send us your requirements and we’ll respond with the facts available for the current fieldGRID deployment.