Entities are a way to map your database tables to meaningful abstractions that are easy to understand for the non-technical users in your company.

It's a way to store the domain logic of your database so that it can be easily used later to analyze the data.

Here's a detailed video about Entities, and how to configure and use them in the InsightFlow:

Here's a quick example: let's say you have an "order" table that stores orders placed by users on your e-commerce website, and you like to allow managers and non-technical people to analyze its data.

This table might have 20, 30, or even 50 different fields, but most of them are not relevant to your users, and they shouldn't even interact with them.

Also, maybe you have a field called "type", where the value "20" represents an order placed by your company, and it shouldn't be included when analyzing order data.

Usually, all your colleagues would have to know these details to ignore those orders.

Here's where the Entities are useful - by configuring some entities on InsightBase, you specify different parameters, that you no longer have to think about when analyzing the data.

The Entities also allow you to place some restrictions to make data analysis easier for your teammates, like which fields should be visible, and in what kind of analysis.

Read the following sections in order to get a better understanding of the Entities, and how they're working: How to create an Entity