How can we help? 👋

How Do I Customize My Components?

How do I understand the blueprint to customize database properties, templates, and views to fit my needs better?

Have clarity on how each component works to unlock additional utility from your system.

Love our systems and want to understand how it works? We’ve broken down all of the parts that make up each component so that everyone has the ability to deconstruct, re-create, and extend their components as they wish. We present this information in a Blueprint.


You can find these blueprints by searching the component name inside the search bar in this academy, near the top of the page. We organize the blueprints as follows:



Each component is made up of databases, which is where the data is stored. Every entry in the database represents a new item of this component. In each blueprint, we list out all the databases that make up the primary function of the component.


Database Properties

For each database, we take advantage of properties to enhance our data definition - so that we can understand more about each entry. We’ll detail the purposes for each property, so you can make good decisions on whether or not each property fits your use case and where modifications may be necessary.


We use properties extensively within our templates, and we have a few standard properties that you will see in most, if not all of our databases.

Property Name
To differentiate the different type of data you will be storing in this database, if varies.
To display important information that the database user needs at a glance
> Connection
A separator to partition out the relations in the database.
> Information
A separator to partition out the properties that are information only (no data entry).
> Calculations
A separator to partition out the necessary formulas to calculate important insights.

Database Templates

There will always be common use-cases for each entry. Thus, we have created templates to help you easily auto-fill properties and data into the page to fit your needs. We will typically have one for every single type of data that is stored. Depending on your own use cases, you may need to add more definition to existing templates, or create new ones altogether.


Each template will include 3 sections that fulfill the purpose of the template. There will be a table of contents to help you navigate quickly to the section every time you open the page.


Each section comes with descriptions on how to effectively use each section as well as a link to the tutorial that will be most helpful for you.

Example section inside the New Area database template in Areas Of Competence.
Example section inside the New Area database template in Areas Of Competence.

Inside the blueprint for each component, template information will be presented as such:

Template Name
Template Purpose
Database Properties
Database Page Section 1
Database Page Section 2
Database Page Section 3
What is the name of this template?
What is the use-case of this template?
Which properties will be auto-filled for you?
What can you do in this section?
What can you do in this section?
What can you do in this section?

Database Views

How the data can be presented for common use cases. We created common synced views that originate from the component page and are placed on different dashboards. Depending on your own use cases, you may want to modify the filtering, sorting, properties shown, or type of the view. Whenever you create a new view, we highly recommend you add it into your components so you can have one source of truth for common views that you like.


The original database will also have a few basic views that will enable you to make use of your database without a dashboard. However, we highly recommend you check out the views that are created for various dashboards - as they will be fine-tuned to fulfill a specific function.


Our naming convention for useful views will always be:

[Database(s)] Purpose

eg. [Areas Of Competence] In Focus / Areas / Values At A Glance

Did this answer your question?