View Basics

In our platform, a View functions like a customizable data slice, allowing you to create tailored representations of an entity. Views let you define specific subsets of an entity's properties and control access through authorization settings.

A View provides a customized version of an entity where you can select which properties to display and set access permissions for different user roles or groups. This enables you to manage how data is presented and who can access it based on their roles or other criteria.

Key Components of a View

• Properties: Choose which properties of the entity to include in the View. For example, you could create a View that shows all the properties of an Employee entity, such as EmployeeName, EmployeeEmail, and EmployeeSalary.

• Authorization: Define access controls to determine who can view the data. For instance, one View may include all properties but restrict access to managers, while another View might exclude sensitive information like salary and be accessible to all users.

Example: Consider an Employee entity with the following properties:

• EmployeeName

• EmployeeEmail

• EmployeeSalary

You can create:

• View 1: Includes all properties (EmployeeName, EmployeeEmail, EmployeeSalary) and is accessible only to managers.

• View 2: Excludes EmployeeSalary and is accessible to all users.

By creating different Views, you can effectively control data visibility and ensure that users only see information relevant to their roles or needs.