Data Migration to Zoho: How to Move from Legacy Systems Without Losing Data
How to migrate data from spreadsheets, Tally, Salesforce, or legacy ERPs to Zoho without losing…
NetSuite’s role-based access system gives each user access to exactly what they need. Sales reps see their deals and customer records. Warehouse staff see inventory and fulfilment. The CFO sees everything. For Indian mid-market companies with 20 to 200 users across departments, getting roles and permissions right is critical for data security and operational efficiency.

Every NetSuite user is assigned one or more roles. A role defines which modules, records, reports, and actions the user can access. NetSuite ships with 20+ standard roles (Administrator, Sales Manager, Accountant, Warehouse Manager, etc.) that cover most common configurations.
| Role | Access |
|---|---|
| Sales Rep | Own leads, contacts, opportunities, quotes |
| Sales Manager | All sales data, team pipeline, forecasts |
| Accountant | GL, AP, AR, bank reconciliation, reports |
| A/P Clerk | Vendor bills, payments, PO matching |
| Warehouse | Inventory, fulfilment, receiving, transfers |
| Executive | Dashboards, KPIs, all reports (read-only) |
| Administrator | Full access including configuration |
Go to Setup > Users/Roles > Manage Roles > New. A custom role is a permission set you build from scratch. For each transaction type, set permission to None, View, Create, Edit, or Full. For example, a “Purchase Coordinator” role might have Create and Edit on Purchase Orders but View-only on Vendor Bills.

Beyond role permissions, restrict record access by department, subsidiary, or location. A salesperson in the West India team sees only customers and deals in the West India subsidiary. A warehouse manager in the Mumbai location sees only Mumbai inventory. Configure these restrictions in the role settings under Audience.
For audit compliance, ensure no single user can both create a vendor bill and approve its payment. NetSuite supports segregation of duties by assigning different roles for creation and approval. The person who enters a vendor bill should not be the same person who releases the payment.
Our team builds systems that actually work. No fluff, just honest architecture and clean implementation.