Roles, Permissions, and the Audit Trail: How Instalify Keeps Your Business Data Safe

An installment business handles some of the most sensitive information a company can hold — customer NICs, financial balances, staff performance numbers, and daily cash records. Every one of those things becomes a liability the moment access to it isn't properly controlled. Instalify's security model is built around a simple principle: every user should see exactly what their role requires, nothing more, and every action anyone takes should be traceable afterward. Sessions that don't quietly do the wrong thing Authentication runs on Supabase's secure JWT-based sessions, with OTP verification available for sensitive actions. Access tokens refresh transparently in the background, and a genuinely expired session is clearly distinguished from "account not found" — so users get accurate messages instead of confusing errors. Multi-account support lets one person switch between different businesses they're associated with, each with its own securely stored refresh token, and a full sign-out properly clears every stored token so a shared device can never accidentally stay logged in as the wrong account. Real, granular role-based access Every module — customers, accounts, transactions, inventory, accounting, reports, staff — is gated behind specific permission keys, and every role is assigned exactly what it needs. A cashier can record payments without financial-edit rights on lease accounts. A recovery officer sees recovery-relevant accounts and reports without touching inventory or accounting. A branch admin manages their own branch's staff and data with zero visibility into other branches. The permissions system supports bulk apply/remove across multiple roles and modules at once, so managing a growing team stays fast instead of becoming a click-by-click chore. An extra lock on the numbers that matter most Editing a lease account's sale price, cost, down payment, or due date requires a distinct, higher-tier permission separate from basic account editing. Even a user trusted with day-to-day account status can't silently alter what a customer actually owes unless that specific trust has been explicitly granted. Proof, not just policy None of this matters if you can't verify what happened afterward — which is why every transactional action is logged: who created, edited, or deleted what, and when. Owners get a dedicated Activity Logs report to review staff actions across the whole company, rather than relying on memory or informal updates. Day-open gating adds a further safeguard, preventing new customers, accounts, or other master records from being created for a business day until that day has actually been opened — closing off backdated or out-of-sequence entries before they can happen. Delegation without losing control Together, these layers mean Instalify isn't just tracking who's logged in — it's actively enforcing who can do what, protecting the numbers that matter most, and keeping an honest, permanent record of everything that happens. That's what lets an owner actually grow their team and delegate real responsibility, without ever losing control of their own business.