Organization Roles
Every user has exactly one organization role. The org role is the user's baseline — it defines who they are across the whole organization and applies to all organization-wide actions (partnerships, banking, HR, masters, audit, settings) regardless of any subproject they may also work in. Subproject roles can add to it, but never take from it. See the overview for how the two layers combine.
There are 8 organization roles.
Admin
Scope: Organization-wide; full authority.
The system owner and final authority. Has organization-wide access to all partnerships, projects, and features, plus full approval authority. This is the role that performs setup, manages users and roles, and approves the actions other roles can only request. Every organization must always have at least one active Admin.
Partner
Scope: Partnership-scoped, read-only.
Read-only ownership visibility, strictly limited to the partnerships the user belongs to. A Partner can view ownership, land, projects, sales, and financial outcomes for their partnership, but has no operational authority — they cannot create or change records.
Self-Managed Partner
Scope: Own partnership's finance and banking.
An extended partner with operational control over finance and banking for their own partnership only. They can create and manage partnership bank accounts, upload statements, and map or remap transactions — but only within their own partnership. Beyond that, they retain the read-only ownership visibility of a Partner.
Finance Manager
Scope: Execution-only finance.
A finance execution role. Processes, records, executes, and prepares financial operations across the organization. Deliberately cannot approve, cancel, or see audit data — the Finance Manager does the financial work, while approvals stay with the Admin. This separation keeps a clean segregation of duties.
Sales Head
Scope: Sales execution and supervision; project-scoped.
Sales execution authority who creates, edits, and progresses sales and supervises the sales team — but cannot approve or cancel sales. Approvals/cancellations are reserved for higher authority. The Sales Head's day-to-day work is project-scoped.
Sales Staff
Scope: Frontline sales; project-scoped.
The frontline sales executor. Handles customer interaction and drafts quotations and sales orders. Project-scoped, and cannot approve or cancel — Sales Staff prepare the work that a Sales Head or Admin progresses.
Project Manager
Scope: Project execution; no financial authority.
Project execution authority responsible for project progress tracking, unit readiness, and handover preparation. Has no approval or financial authority — the focus is operational delivery of the project, not money or sign-off.
People Manager (HR)
Scope: HR data, organization-wide; no financial execution.
Manages employees, roles, assignments, and the user lifecycle, and prepares payroll inputs. Operates organization-wide for HR data but has no financial execution authority. This is the role you give to whoever owns user onboarding and offboarding without giving them full Admin power.
Summary
| Role | Scope | Can approve / cancel? | Financial authority |
|---|---|---|---|
| Admin | Organization-wide | Yes (full) | Yes |
| Partner | Partnership (read-only) | No | No (view only) |
| Self-Managed Partner | Own partnership finance/banking | No | Own partnership only |
| Finance Manager | Finance execution | No | Execution only |
| Sales Head | Sales (project-scoped) | No | No |
| Sales Staff | Sales (project-scoped) | No | No |
| Project Manager | Project execution | No | No |
| People Manager (HR) | HR (org-wide) | N/A | No |
Sensitive-data access
Sensitive personal and financial data (PAN, Aadhaar, GSTIN, contact details, bank account numbers, and files marked sensitive) is masked by default for everyone. The ability to reveal the full values, or to download sensitive files, is granted by separate permissions:
- Admin can reveal all sensitive data and download files at every sensitivity tier.
- Finance Manager can reveal bank-account details and sensitive custom fields, and download sensitive/PCI files.
- All other roles see masked values only.
Every reveal and every sensitive-file download is recorded in the audit trail. See Data Security for the full masking, reveal, and file-tier rules.
Choosing the right org role
- Give Admin sparingly — only to people who genuinely own the system.
- Use Partner / Self-Managed Partner for stakeholders who own a share but do not run operations.
- Split sales work between Sales Head (supervises, progresses) and Sales Staff (drafts, customer contact).
- Use Project Manager for delivery, Finance Manager for money handling, and People Manager (HR) for user/HR administration.
To grant additional, subproject-scoped permissions to any of these users, layer a subproject role on top. For the exact permissions behind each role, see the RBAC matrix.