The nature of businesses has undergone a sea change in the past few years. With each passing day, businesses have become more collaborative. Hence, it is not uncommon to see more interaction happening between different departments of the organization. Along with it, the quantity of data processed has also increased immensely. Nevertheless, the entire chunk of data is not required by all teams in an organization. Different teams and members within teams generally require access to different sections of the data. For example, the data required by the Sales Manager of a company will differ from the data required by the Marketing Manager. Also in a particular team, depending on the hierarchy the data requirement will differ.
Let’s understand this better with the help of an example. The National Sales Manager of a company will need the sales data from all over the country; however, the Regional / State Sales Manager will be concerned with the Sales data for his region. To address this issue, the latest feature to be added to DataRPM’s Analytics Plug and Play Platform is Role Based Security feature.
With the addition of this feature, there are ‘Four’ access levels given on a dataset, namely ‘Expert’, ‘Pro’, ‘View’ and ‘Custom’. At any given point of time, a particular user will be assigned to any one level in one dataset. In brief, here is what Role Based Security actually is:
‘Expert’ (E) Access in Role Based Security
A user with ‘Expert’ access is the one with maximum amount of privileges on a particular dataset. This role is often assigned to people in the top management. From our example, the National Sales Manager may be assigned this role. This user is in a position to edit the dimensions of a dataset on which he has been given ‘Expert’ privileges, along with creating new reports and dashboards based on this dataset. An expert user will not be able to delete a dataset, although he has expert privileges on it. An expert user will not be able to edit or view the reports/dashboards created within the dataset not created by him, unless he has been explicitly granted edit or view access by the owner.
‘Pro’ (P) Access in Role Based Security
In the hierarchy, a user with ‘Pro’ access comes in next. Taking the example forward, this access may be assigned to the Regional Sales Manager. This user will be able to make use of the dataset to create reports and dashboards, however, he will not be able to edit or view reports or dashboards, which are not created by him unless he has been explictly granted access for the same by the owner. A ‘Pro’ user will not be able to edit the dimensions of the dataset on which he has ‘Pro’ level privileges.
‘View’ (V) Access in Role Based Security
As the names suggest, a user with ‘View’ access will only have access to view all the reports and dashboards created within the dataset for which he has been granted access to. He will not be able to create or edit reports or dashboards. He will have no access whatsoever to modify the dataset either. In line with our example, the Area Sales Manager may be given ‘View’ Role.
‘Custom’ (C) Access in Role Based Security
This user is the one, who will have different kind of privileges on different datasets. For example, on a particular dataset a user may have ‘Expert’ privileges, whereas on another dataset he will have only ‘View’ privileges. The privileges can be further customized, wherein a user may be given access to create a report, but only view a dashboard. A user with privileges to create a dashboard or report automatically gets privileges to view the dashboard or report. To explain this further, the Regional Sales Manager may be given ‘Custom’ privileges to view datasets about the National Sales. He may be given access to only create a dashboard, but have access only to view reports.
With the addition of this feature, analytics on the cloud comes with added security of the data.