Tip #34: Hide sensitive fields with field-level security in Qntrl's cards

With Cards in Qntrl, you can create tasks wherein an individual user or team can refer information about the task and ensure everyone with access to the card is well-informed about the card details. However, it can certainly be possible that not all card details need to be accessible to all users in the organization.

To ensure that the sensitive and private details are not shared with all user profiles (who have access to the card), you can restrict the level of access for users in your organization. Fields can be moderated on what the user can access, read, and edit based on the profile.

Who can do this?

Any user with access to Settings in their Qntrl account will be able to perform modifications in the Profile tab.

Tip!

To provide Settings permission to a profile, you can do as shown in the screenshot. Navigate to a specific profile and enable the Settings permission in order to allow the users of that profile to access Settings in their Qntrl account.

Who cannot view the fields?

The users in profiles for which the fields are hidden cannot view the fields. However, note that the profile with Admin privileges will be able to view all the fields in all forms.

How to provide field-level permission?

Field-level permissions can be given in two ways inside Qntrl.

Provide profile-based permissions throughout the organization.

In this case, if fields are hidden for 'Staff' profile, all the users associated with this profile will not be able to view fields like 'Medical bills to be claimed', 'Email Id', 'Vendor Details' throughout cards of all orchestrations.

Provide orchestration-based permission only to cards of specific orchestrations.

In this case, if field is hidden for 'Staff' profile, all the users associated with this profile will not be able to view field 'Medical bills to be claimed' only in 'Reimbursement Form' orchestration.

Which fields can be secured with 'Hide' permission?

Only custom fields can be secured with 'Hide' permission. Default fields cannot be hidden and will be visible to users throughout the organization. However, read/edit permissions are subjective to the default fields in cards.

You can provide field-level permissions to:

Restrict users from editing specific data entered only during a signup or onboarding process.

Hide specific custom fields in the order process workflow like ‘Invoice amount’, ’Social security number’, etc.

Provide read-only access to ‘Staff’ profile while collecting information during signup that only an admin can change.

Provide read-only access to ‘Hiring managers’ for Position and Candidate fields.

Hide minimum and maximum pay from standard employees and interviewers in the recruitment workflow.

If you haven’t already tried these options, before you start, enable the right permissions for each profile and specify the kind of permissions you want for users with each profile, and save your settings. This article specifically deals with ‘Hide’ permission. You can similarly use the field-level permissions for ‘Read/Write’ and ‘Read Only’ permissions.

Let us know how this feature is helpful in your organization. Visit our help center to get detailed insights into Qntrl and onboard faster.

Zoho Desk Resources

Desk Community Learning Series
Digest
Functions
Meetups
Kbase
Resources
Glossary
Desk Marketplace
MVP Corner
Word of the Day

Topic Participants
Sanchita Padhi

Sticky Posts
Tip #21: Increase user engagement using dynamic email content and attachments in Orchestly
Businesses often send out bulk emails like weekly newsletters, monthly event updates, promotional emails, surveys, beta access emails, product reviews, seasonal greetings, and so on. Even as the gist of these emails remain constant for all recipients, personalizations capture the audience’s attention and help brands connect with them. Orchestly’s email templates allows you to draft and send dynamic emails with personalized content and attachments to internal and external users. Email templates
Qntrl's 2023 year in review
This year has been all about analyzing our customer feedback and building a resilient and solution-driven product from it. As a result of this work, we're happy to announce that a whole new version of Qntrl is getting ready for release soon. This new
Tip #61: 5 different ways to create Cards in Qntrl
Qntrl supports an array of features that covers everything required for business orchestration, from process automation to business advancement. Cards, being the elemental feature of Qntrl, record all the details of a particular task from the beginning
Tip #17: Stay informed of significant business impact using Orchestly
With remote working becoming the new norm, leaders across sectors need to stay updated of their business performance in the market to aid business decisions. Instead of awaiting virtual meetings from sales and finance heads to put forth the business status, organization leaders can themselves dig into the system to keep an eye on their revenue generating customers or set up notifications to monitor major updates. Orchestly recognizes such requirements and provides adaptable solutions for all business
Onboard faster with Orchestly's Tutorials
We are actively rolling out new learning materials to assist our customers onboard at ease and automate their processes effortlessly. On that front, we recently launched Tutorials for Orchestly. Tutorial is a step-by-step guide to help users familiarize the concepts of Orchestly and automate simple processes right from scratch. We’ve documented 3 such business processes viz. Order Manufacturing, Product Implementation, and Change Management. We're looking forward to document more customer-centric