Understanding user permissions
In a nutshell
User permissions let you define how different users can access a report's data and how the sharing of this data with fellow users can be enabled. This provides granular control to users on a role-based access control (RBAC). User permission is defined by three attributes: Permissions, Roles, and Data Sharing.
Availability
- User Permissions can be accessed in all plans of Creator.
- Only the super admin, admins, and developers can create and manage User Permissions.
1. Overview
User Permissions is a way of establishing granular control over the access of data in your applications by users. These user permissions allow you to restrict your users to a particular set of data, thereby also creating a secure platform in which the data is shared and worked with only where it is necessary. If used efficiently, User Permissions will let you control the whole organization's access of data in a systemized manner.
A user is a person who can access your application. Under the User Permissions page, the following can be accessed:
- Permissions - Set up certain pre-made or customized permissions that determine a user's access to a report's records
- Roles - Define different roles for the people in the organization
- Data Sharing - Determine how the data stored in the application can be shared between these users/roles
1.1 See how it works
We have detailed videos of the following features for your better understanding:
1.2 Use case
Say you've created an Employee Management app for your organization. Two departments, HR and Admin, work with this application. Each department has a department head, two managers under each head with three juniors each.
- The HR team members are given a permission set where they can access and edit the records of an Add Employee form. The Admin team members are given a permission set where they can view and edit the Request Accessories form.
- Roles are assigned to the above people, thereby providing them with a place in the organization's hierarchy. When role hierarchy is enabled, the department head will be able to view the records added by all their subordinates while vice versa is not possible.
- A data sharing rule is defined which enables a user from the HR team to share records added by them in the Add Employee form, to the two managers and their subordinates in the Admin team. Now, the Admin team can cross-check the employee's details before providing the employee with the company's accessories.
1.3 Navigation guide
In the Edit mode of the application, User Permissions is situated under the Permissions section of the Settings page.
1.4 Permissions in user permissions
Permissions are a set of rules that govern the accessibility of the application's data for users. Read and Write are the two predefined permissions.
- Read permission enables the user to view all the data stored in the application.
- Write permission enables the user to edit all the data stored in the application.
You can also create custom permissions based on your requirements by clicking on the Add Permission button. Learn more
For example, in an Order Management application, the customer and the delivery executive will have access to different components. The customer will be given permission only to view the records of their Personal Order History. The delivery executive similarly will be given permission to view the records of their past deliveries.
1.5 Roles in user permissions
Roles help you:
- Create an organizational hierarchy and define clear positions for the people/teams working in your organization
- Group individuals working in your application, making it easier to share data with a cluster of users assigned to the same role
Role hierarchy, when enabled, lets you choose whose records a user can see with the appropriate permission sets. Learn more
For example, say you have a Quality & Assurance team consisting of seven employees in your company, for which you create a role. All seven employees will be grouped together under this role when they are added as users in your application. The records added by these users will be accessible by their peers according to their permission sets. However, the cannot view added records by superiors when role hierarchy is enabled for that particular form.
1.6 Data sharing in user permissions
You can define rules that help you share data with individual users or with peers, management, and subordinates based on their roles. Choose between Read Only and Read/Write based on the requirements. Learn more
For example, consider role hierarchy has been enabled for a Task Management application. A new project trainee cannot see the records of their immediate superior while the latter can monitor the trainee's training tasks. In the event of the trainee being confirmed, it is decided that they work with the superior on their tasks. Therefore, a data sharing rule is drafted to allow the trainee to view the task records of the superior.
2. Points to note
- Refer below for the detailed Points to Note sections':
- Permission sets can be defined for your application only in the paid plans of Creator. See our pricing page.
- Roles can be added to your application only in the paid plans of Creator. See our pricing page.
3. Related topics
What's next
Previous
What's next
Previous
Access your files securely from anywhere
Zoho CRM Training Programs
Learn how to use the best tools for sales force automation and better customer engagement from Zoho's implementation specialists.
Zoho DataPrep Personalized Demo
If you'd like a personalized walk-through of our data preparation tool, please request a demo and we'll be happy to show you how to get the best out of Zoho DataPrep.
- Zoho Workerly Home
- Forums
- Connect With Us:
- Zoho Recruit Home
- Forums
- Connect With Us:
New to Zoho Writer?
Create. Review. Publish.
New to Zoho CRM Plus?
Deliver unforgettable customer experiences
New to Zoho CRM Plus?
Deliver unforgettable customer experiences
New to Zoho Marketing Plus?
Everything you need to run your marketing
New to Zoho Marketing Plus?
Everything you need to run your marketing
You are currently viewing the help pages of Qntrl’s earlier version. Click here to view our latest version—Qntrl 3.0's help articles.
New to Zoho Survey?
Zoho Sheet Resources
Zoho Forms Resources
New to Zoho Sign?
Zoho Sign Resources
Sign, Paperless!
New to Zoho TeamInbox?
Zoho TeamInbox Resources
New to Zoho ZeptoMail?
Design. Discuss. Deliver.
New to Zoho Workerly?
New to Zoho Recruit?
New to Zoho CRM?
New to Zoho Projects?
New to Zoho Sprints?
New to Zoho Assist?
New to Bigin?
Related Articles
Understanding permissions
In a nutshell Permissions define how users can access the records of an application. Creator provides two default permissions (Read and Write) and allows you to create custom permissions by specifically giving access to view, edit, or delete ...Understanding users
This help page is for users in Creator 6. If you are in the older version (Creator 5), click here. Know your Creator version. 1. What does this page cover? Learn about users who can be added to your organization and how they can access the ...Understanding forms
In a nutshell Forms are used to enter data, and are a core part of an application. The data gets stored in Creator which can be viewed as Reports. A form is made up of fields (for various data inputs) and buttons (to submit/update/reset) and can be ...Creating and managing permissions
What does this page cover? Learn to create permission sets that determine the actions a user can perform when they have access to the data of an application. Availability Permissions is accessible in all plans of Creator. Addition of new permission ...Understanding portals
This help page is for users in Creator 6. If you are in the older version (Creator 5), click here. Know your Creator version. A Portal is a great way for an organization to allow its external users to log in to their dedicated internal system and ...
New to Zoho LandingPage?
Zoho LandingPage Resources