Tenant isolation
Each organization is provisioned with its own frontend host, API host, and data. You are not browsing another customer’s records in a shared table of a consumer app.
Security
Control is a product feature, not a footer claim
Budgipal is built for organizations that cannot put payroll, bank activity, and vendor files in a loosely permissioned tool. Here is how isolation and approvals actually work.
Roles and permissions
Granular RBAC gates modules and actions. System admin and employee roles are seeded; additional roles are configured for your org. Dashboards and nav only show what a user can access.
Authentication
Username and password with JWT access and refresh. Profile, password change, and email OTP password reset are built in. Remember-me is optional on the login screen.
Approvals as control
Visual workflows encode who can approve what, including amount limits, delegation, and request-more-info. Disbursement posts after approval — not from an unchecked inbox.
AI is read-only on the books
The in-app analyst turns questions into read-only queries and document retrieval. It is designed not to mutate finance records. Access still follows the user’s permissions.
OCR with a human confirm
Extracted invoices and receipts sit in a review queue. Financial records are created after someone confirms — not from a raw model guess.
Need a deeper questionnaire for your security review? Email ops@budgipal.com.
See Budgipal on your chart of accounts
Tell us how you plan, approve, and pay today. We will walk through a branded tenant — not a generic sandbox.