TheGridAccess should depend on who you are and which business you belong to—not just which buttons you can see.
Last updated: 16 October 2026
TheGrid is in development. These are the controls implemented in our current development system, not a promise that every security scenario has been independently verified.
Owner, manager and employee roles have different permissions. Database restrictions protect sensitive records even when someone tries to access them outside the visible menu.
Employees are restricted from direct access to customer records and core business finance tables. Authorised owner/manager access is also subject to existing plan rules.
Access rules use business membership and ownership to separate workspaces. Being signed in does not, by itself, give an account permission to another business.
Targeted tests have confirmed that a test employee could not read unrelated business records and an existing invoice. Other record types still need broader test coverage.
Banking details are saved separately in an owner-only private table. Shared business and profile records have database checks that prevent banking details being stored in their legacy banking fields.
This preserves the everyday business information employees need without making private payment information part of that shared record.
Employee clock-in, break and clock-out actions use server time and the saved staff pay rate. The phone does not choose the recorded hours or pay for those actions.
Direct employee timesheet inserts, edits and deletions are restricted. Authorised managers retain their existing correction permissions; a business should still review its timesheets.
Personal checklists are restricted to their author within a business. Calendar entries can be private, manager-visible or shared with selected staff, using database audience rules.
Staff shift access is tied to the signed-in employee’s linked staff record. Display preferences do not grant extra permissions.
Selected automatic notification and clock-out functions are restricted from direct calls by ordinary signed-in or signed-out app users.
Trusted database triggers and scheduled jobs retain the permissions needed to perform their intended work. Normal staff-question notifications and clock actions have been tested after the changes.
Recent checks covered selected employee read restrictions, cross-business access, banking storage protections, role checks and internal-function permissions. The clock-action update was also tested in an isolated database with synthetic records, followed by an app workflow check.
These checks are not an independent penetration test or a guarantee of complete security. An empty table is not counted as proof that its access rules work. Write permissions, storage, exports, account recovery and less common workflows require continuing review.
Two-factor authentication, a full external security audit and guaranteed notification delivery are not claimed as available or completed by this page. No online service can promise zero risk.
Role changes are restricted to the business owner. Staff-record edits, including pay rates, require owner/manager permission. Employee clock actions calculate time and pay in the database rather than accepting those amounts from the phone. These controls do not replace regular management review.
No. Personalisation changes the layout of your account. Database access rules are responsible for enforcing permissions; hiding a page or card is not a security boundary.
No. TheGrid is still being developed, and the tests described here cover specific controls and scenarios. We will keep reviewing additional data types, permissions and workflows. This page will be updated as that work progresses.
Use a strong, unique password, protect the email account used for sign-in and recovery, and never share passwords or verification codes. Review team membership when someone changes roles or leaves. Contact us if you notice unexpected activity.
Use the contact details on our website to report a suspected security issue. Include a short description and the affected feature, but do not send passwords, verification codes, bank details or other people’s private records.