Field-Level Permissions in iVendNext: Mastering Perm Levels
Overview
Not all fields in a document should be visible—or editable—by every user. With Field-Level Permissions and Perm Levels in iVendNext, you can:
Hide sensitive fields (e.g., salary, cost prices).
Make fields read-only for certain roles (e.g., prevent sales staff from editing payment terms).
Group fields by security tiers (e.g., "Level 1: Basic, Level 2: Financial").
1. Key Concepts
What Are Perm Levels?
Permission Levels (0-9): Numeric groups assigned to fields. By default, all fields are Level 0.
No Hierarchy: Level 3 isn’t "higher" than Level 1—they’re just tags for grouping.
Role-Based Control: Each role can be granted Read/Write access to specific levels.
Example:
Level 0: Basic fields (e.g., Customer Name).
Level 2: Financial fields (e.g., Item Rate, Discount).
2. Step-by-Step Setup
Step 1: Assign Perm Levels to Fields
Go to Customize Form (Home > Developer > Customize).
Select the DocType (e.g., "Sales Invoice Item").
Expand the target field (e.g., "Item Rate") and set its Perm Level (e.g., "2").
Save.
Step 2: Configure Role Permissions
Open Role Permissions Manager (Home > Users and Permissions).
Select the Document Type and Role (e.g., "Sales User").
Add a rule for the Perm Level (e.g., Level 2 = "Read Only").
Result:
Sales Users see the Item Rate but cannot edit it.
Accounts Managers (with Write access to Level 2) can modify it.
3. Real-World Examples
Example 1: Restricting Salary Data
Goal: Hide salary fields from non-HR roles.
Set Perm Level 3 for "Basic Salary" in the Employee DocType.
In Role Permissions Manager:
Grant HR Manager: Read/Write for Level 3.
Deny all other roles.
Example 2: Read-Only Pricing
Goal: Let sales teams view—but not change—item rates.
Set Perm Level 2 for "Rate" in Sales Order Item.
Assign Sales User: Read (no Write) for Level 2.
4. Pro Tips
Bulk Apply Perm Levels:
Change a section’s Perm Level to affect all fields within it.
Combine with User Permissions:
Restrict both field access (Perm Levels) and record access (e.g., by Territory).
Audit with Reports:
Use "Permitted Documents for User" to verify field visibility.
5. Troubleshooting
Here’s a quick look at some common issues you might run into.
Field not hiding?
Check:
Perm Level is assigned to the correct DocType.
Role Permissions explicitly deny the level.
Unexpected edits?
Ensure Write access isn’t granted to unintended roles.
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 ...Managing User Roles and Permissions
Overview Roles and permissions in iVendNext control what users can view, edit, and manage, ensuring secure access. This article explains how to: ✔ Create and assign roles ✔ Configure granular permissions ✔ Restrict document access (e.g., "Only If ...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 ...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 ...