Roles and Permissions

Roles

In ViewZen, a role is a predefined set of permissions assigned to a user or group of users. Roles determine what actions a user can perform within a product, application or solution. In ViewZen, the following standard roles are supported

Roles

Standard Roles

1. Owner The Owner role is the highest level of access for a user in ViewZen. This role get automatically assigned to the individual who created the account. All legal requirements have to be fulfilled by the Owner. The owner has unrestricted access to their organization account.

2. Administrator

   Users with Administrator role have full access to manage users, settings, and system configurations. Administrator has all the access as an owner except

   • The Administrator is not liable and has no legal binding.

   • An Administrator cannot create another Administrator in the organisation. Only owners can create Administrators.

   • Administrators cannot delete users and user groups not created by them.

3. Creator

   Creator is a special kind of a role in ViewZen that allows users to create resources or assets for their organization. The resources that the creator can create varies from product to product. For example, in the ViewZen Analytics application, they can create pipelines, datasets, dashboards, and more. In Appverse, creators can create applications.

4. Viewer

   Users with the “Viewer” role in ViewZen can only view the dashboards in Analytics or use the assigned applications in Appverse. They cannot create or modify any resource or asset that the creator has created. However, depending upon the permissions that they have, they can collect or modify data.

Permissions

In ViewZen, Permissions refer to the specific rights or privileges granted to a user, allowing them to perform certain actions within a ViewZen Product. Permissions determine what a user can view, modify, create, or delete based on their assigned role.

In ViewZen, Permissions are tied to Resources.

Resources

In ViewZen, resouces refer to various broader level assets that make a ViewZen Product meaningful and usable and therefore requires to be controlled.

Accounts, has the followng core resources

1. Tenant Used to manage the tenant, which refers to the organization or account.

2. Users Used for inviting users, activating and de-activiating user, managing user roles and permissions.

3. User Groups Used for creating user groups, activating and deactivating user groups, adding or removing users from groups, and managing user group permissions.

Appverse, has the following core resources

1. Forms User interfaces used for collecting input, data, and information from users for different applications created in Appverse.

2. Form Data Form data refers to the actual data collected or used in the Appverse Forms.

3. Form Allocation Form allocations are used for assigning the forms of application to user(s) and for controlling the view, edit and offline download permissions on various form data.

4. Form Library Form Library is used for giving various advanced customization options for controlling workflows, business rules, integrations etc. of an Appverse application.

ViewZen Analytics, has the following core resources

1. Connectors Used to connect and retrieve data SQL and NoSQL databases, Excel, CSV, JSON, and other file formats, Google Sheet, Excel Sheet etc.

2. Pipelines Pipelines are Automated workflows that process and transform raw data for meaningful insights.

3. Datasets Datasets are structured collections of data that can be used for analysis and visualization.

4. Dashboards Dashboards are Interactive visual representations of data, including charts, graphs, and reports.

Permissions on Resources

Permissions in ViewZen Analytics control the level of access users have on different resources, ensuring that sensitive data and system settings are properly protected while enabling users to perform their tasks effectively.

Types of Permissions:

1. Create – Grants the user the ability to create new resources, such as datasets, dashboards, reports, pipelines, or forms. For example, a user with "Create" permission can design a new dashboard or build a new pipeline.

2. Edit – Allows the user to modify existing resources. This includes updating data, modifying dashboards etc.. Editing permissions ensure that users can make necessary changes.

3. View – Provides the user with read-only access to view resources but not modify them. Users with "View" permission can view dashboards, reports, and other resources without making any changes.

4. Delete – Grants the user permission to permanently delete resources from the system. Deleting resources should typically be restricted to administrators or owners to avoid accidental loss of important data.

Permissions Based on Ownership and Sharing:

1. Created by User – Refers to the resources that are owned and created by a specific user. The user can typically have full permissions (create, edit, view, delete) on these resources. These resources are often under the user's control, and they can manage them freely.

2. Shared by User – Refers to resources that have been shared with other users. The permissions granted on these shared resources can vary depending on the sharing settings. For example:

   • View-Only Permission – A user can view but not edit or delete a resource shared by another user.

   • Edit Permission – A user can edit a resource shared by someone else if the permissions allow it.

   • Delete Permission – The user can delete the shared resource, similar to ownership.