Corteza Admin Manual

To create a new user click on "New" button on top right corner above the User list.

Fulfill the Basic information and hit submit. You can set a user a password to log in (but he’ll need to confirm his email after the first attempt to log in). Alternatively, a user can request a "Forgotten password" on login screen and set a password on his own.

To edit a user click on an "Edit" icon on the right side of the users list.

In this screen you can:

To create a new role click on "New" button on top right corner above the Roles list.

Fulfill the Basic information and hit submit. Once a role is created, you can start assigning members to it.

To edit a role click on an "Edit" icon on the right side of the roles list.

In this screen you can:

To create a new role click on "New" button on top right corner above the Applications list.

Set an application name and mark it as enabled so it becomes visible in the list of applications. In the next step you can add an URL to the favicon and logo and assign application URL.

You can add any Namespace as a separated application. Additionally, you can add as an application all external websites and web applications that don’t have iFrame access denied.

To edit an application click on an "Edit" icon on the right side of the applications list.

In this screen you can:

In this section you can set:

Email templates used for authentication purposes are the following:

We recommend using Codepen or similar browser-based tools to preview the layout of the template before changing the template.

To enable Google authentication you need to create a client ID:

To enable Facebook authentication you need to create Facebook app to receive Client key and Secret:

To enable Github authentication you need to register Github application to get unique Client ID and Client Secret:

To enable LinkedIn authentication you need crete a LinkedIn application:

In this section you can select:

In this section you can set a maximum file upload size (default is 10 MB) and file type whitelist for Low Code pages and records.

In this section you can select:

In this section you can select:

Each user can be a member of multiple roles. We suggest having "modular" approach, so creating multiple smaller roles (i.e. Messaging admin, CRM admin) and then stacking them to cover all the parts of the system where a user needs access.

Admin can create unlimited amount of roles. Permissions system in the Admin Panel is a playground, where you bring each role on the table, adjust the permissions and save it. More details in the following chapters.

The overall flow of verifications if a role has access to perform an operation on a resource is the following:

Permissions in the Admin Panel are general and can be overridden per individual application/namespace/etc. For a better overview, we suggest you first set permissions on this level and then go lower on the hierarchy.

Inherit value always checks the setting in the layer above. For example: if an individual application has access permissions set to "Inherit", it will use the permission set for All applications (default: "Deny"). Explicit "Allow" or "Deny" always override the Inherit value.

In practice, that means that check verifies if any of given roles has permission to perform an operation over a resource

In this section you control overall access settings and usage of Admin Panel.

You can set permissions to:

Any access you grant in this section can be overridden per individual element.

In this section you can control who can access Low Code, who can manage settings and who can create namespaces.

Please note that permissions are fine-grained, meaning if you allow users to access namespaces, they still need explicit allowance to read pages, modules and fields.

In this section you can control which role can:

Any access you grant in this section can be overridden per individual namespace.

In this section you define which roles can:

Any access you grant in this section can be overridden per individual module.

Here you can control permissions for main Low Code elements:

Any access you grant in this section can be overridden per individual element.

In this section, you can control who can access Messaging app, manage Messaging settings and who can create public/private/direct channels.

We recommend this permissions to be allowed to Administrators and Messaging Admins only.

In this section, you have full control over which role can to the following:

If a user doesn’t have explicit allowance to delete any channel, but they can create a public channel, they we’ll still be capable of deleting this channel as they’re the owner of it.

A module is like a table in a database. A simple namespace typically has a few modules, while bigger namespaces have many more. Corteza CRM, for example, has over 35. The number of modules an namespace can have is unlimited.

A new namespace does not have any modules. You can create one by using the form on top or by importing an existing module from a different namespace using an export file. You can import and export individual modules or all modules at the same time.

When you create a module, best practice is to give it a descriptive name without spaces and using capital letters on different words, e.g., Lead, Account, or CaseUpdate.

Each module consists of a set of fields that define what data you want to store and in what format.

You can add new fields to a module by using the Add new field button. This adds a new row with the following fields:

At the end of the row, you can find a Delete button (to remove a field) and a Permission button (to set read permissions and update field permissions per role).

You can select from the following field types. The wrench icon beside the field type provides further options for each case.

The Record block is the most important block for a Record page. You can select the block’s layout and the fields you want to show. For example, a Contact record page would need to show: Name, Email, Phone, and Address. Select those fields, hit Save and close, and the block will be added.

When you view a record, the values of these fields are shown as strings, and when you add or edit a record, these fields turn into form-input fields.

To show a list of related records you need to select the Record list block with prefilter.

The Prefilter records field allows simplified SQL "Where" conditions, and variables like ${recordID}, ${ownerID}, and ${userID} are evaluated (when available). If you are editing a "company" record, and you want to show all the employees in that company, you would need to fill in: ${recordID} = companyId (companyId would need to be a field of the Record type inside the Employee module in this example).

You can also Presort records field by inserting for example createdAt DESC. This shows the list of record by creation date. This field supports simplified SQL Order by condition syntax.

You can also select to hide or show the New record button and Search box, and you can define the number of records shown. A best practice is to adjust this number to the size of the block.

To save the block and add it to the page, hit Save and close. Now the second block has been added to the page.

Other block types are:

After adding blocks to pages you can resize and position them to create the layout you want.

Corteza Low-Code is responsive by default, so the blocks will resize and reposition automatically on devices with small screens.

Record triggers can be created on any module that is available for this namespace. You can find record triggers under automation script’s Record triggers tab.

Scheduled triggers are executed at a specified time or in an interval. They are mainly used for periodic tasks, such as batch record updates, aggregation, updating records based on an external source, …​ You can find scheduled triggers under automation script’s Scheduled tab.

Corteza CRM has an extensive set of automation scripts that can be used as examples. Some of them are: