Configuring Role-Based Permissions for Documents
Overview
This article provides a step-by-step guide to setting up granular permissions for documents, including field-level restrictions and stage-based controls.

Step 1: Accessing the Role Permissions Manager
Navigate to: Home > Users and Permissions > Role Permissions Manager.
Select a Document Type (e.g., "Leave Application," "Sales Invoice").
Tip: Use the search bar to quickly find document types.
Step 2: Understanding Permission Components
Permissions are defined by five key elements:
Component | Description | Example |
|---|
Role | User role (e.g., Employee, HR Manager). | "HR Manager" can approve leave requests. |
Document Type | The document being controlled (e.g., Purchase Order). | Restrict access to "Salary Slips." |
Permission Level | Groups fields by sensitivity (Level 0–9). | Level 1 = Salary fields (restricted). |
Document Stage | Lifecycle stage (Creation, Submission, Cancellation). | Allow "Submit" only for Managers. |
User Permissions | Limit access to specific records (e.g., only their leave applications). | The employee sees own records. |
Step 3: Adding a New Permission Rule
Click "Add a New Rule."
Select:
Set permissions for each stage:
Step 4: Configuring Field-Level Permissions
Use Permission Levels to restrict sensitive fields:
In the document (e.g., "Sales Invoice"), assign fields to levels:
Level 0: Basic fields (e.g., Sales Employee).
Level 1: Sensitive fields (e.g., Approval Status).
In Role Permissions Manager, grant Level 1 access only to privileged roles (e.g., Sales Manager).
Example:
Sales Employee: Read/write Level 0 fields (e.g., Invoice dates).
Sales Manager: Read/write Level 1 fields (e.g., approval status).
Step 5: Restricting Document Access (User Permissions)
To limit users to specific records (e.g., only their territory’s sales orders):
Click "Set User Permissions" in the Role Permissions Manager.
Define filters (e.g., "Territory = East Region").
Real-World Use Cases
Let’s explore how sales invoice approval works in real-world scenario
1. Sales Invoice Approval
Sales User: Create invoices, but cannot submit.
Accounts Manager: Submit/cancel invoices.
Field Restriction: Level 1 = Discount % (only Managers can modify).
Troubleshooting
Related Articles
Role-Based Permissions: A Comprehensive Guide
Overview Role-Based Permissions (RBP) in iVendNext control access to documents, reports, and form fields. They’re key to maintaining security and smooth workflows. This article covers how RBP works, setup steps, and best practices. 1. Understanding ...
Understanding User Roles and Permissions
Overview User roles and permissions are key to keeping your application secure and running smoothly. They control who can access what, based on each user’s responsibilities. This article explains the basics to help you set up and manage roles in ...
Integrating User Permissions with Sharing Features
Overview iVendNext combines strong permission controls with flexible sharing options. Roles set default access, while sharing allows exceptions for collaboration. This article covers how they work together and tips for secure teamwork. Understanding ...
Managing Permissions and Web Views for DocTypes
Overview Effective permission management and web view configuration are critical for maintaining data security while enabling collaboration in iVendNext. This article provides a comprehensive approach to controlling access to your DocTypes and making ...
Role-Based Permissions and Access Control
Overview This article outlines the steps to set up and manage role-based permissions in iVendNext to control access and protect sensitive data. What Are Role-Based Permissions? Role-Based Permissions in iVendNext allow administrators to define what ...