Hello everybody,
It's been a while since I've made a post for y'all, and I come bearing news (obviously good news). Our team has put together new and exciting features, packed it into an update— the Cliq update for 2019.
In this post we are gonna talk about one key feature in this update—
Data Privacy.
Security and Privacy existing in Cliq:
1.
Encryption:
Your data is securely encrypted in transit and in storage, thus safe from prying hands (minds as well)!
2. T
urn off Chat History:
Users can turn off chat history for specific chats and ensure sensitive information is not stored anywhere, even on Cliq servers.
3.
Code Reviews:
Our team reviews the codes submitted by app developers to ensure that the apps hosted in our Marketplace are safe and sound!
New in line to fortify your Privacy—Consents
To manage IT asset requirements, a user say Ryan from your organization is creating a /itasset command through which all your employees can raise hardware and software requests to the IT team.
Now when your org users use the /itasset command, certain data is accessed from them, processed and executed for the command to work. To convey what data is accessed and to give permission over the usage of those data, Consents are introduced in Cliq.
Consents are
basically popups asking for permission to access the required data
when using an internal tool for the first time, i.e. bots, commands, message actions and functions .These popups contain the breakdown of apis and deluge tasks used and the data required from the user to perform that action.
In the above gif, on executing the /itasset command for first time, the consent pops up. In it there are 2 fields: Account Details and Zoho Tasks.
1.
Account Details
- When a user executes the command, their info like name and email id is collected to raise a request.
2.
Zoho Tasks
- The collected information is stored in Ryan's database and a deluge task is triggered to post the request as a card in the IT team's channel for requests.
So with these consent boxes
each user can be aware of how and what data is accessed from them.
On granting permission the user can proceed with the task. If the user feels not to allow access to the data, then they can exit the consent popup, refusing to allow access. (Refusing access will effectively stop the internal tool from performing that action.)
The consents will appear for the following tools
- Command: When a user executes a command for the first time
- Subscribed Bots: When a user sends message to the bot.
- Unsubscribed Bots: When a user subscribes to a bot.
- Message Action: On execution
- Function: On button click / form submission
To revoke a consent for any tool, click on the Integrations icon just before your profile picture, and select the internal tool from the menu. Then look for the name of the tool that you want to revoke and click on it. In the bottom left corner click on 'View Granted Permissions' and revoke the access given.
We are also bringing in Consents when installing an integration from the Marketplace, so that the admin can be aware of what data an integration will access from their organization!
So, do y'all like our latest privacy update—Consents?
And keep an eye out in this community for the next few days. I will be posting detailed breakups of more exciting updates, sure to help you organize your workforce on Cliq.
Princy.