All topics
Get started8Account, team & permissions44Units & fields70Records, views & tasks39WhatsApp & Cortex Chat68Email & social27Lead ads & distribution38Automations52Documents & quotes32Dashboards40Cortex AI18Developers & API12
Help Center·448 guidesAll topicsContact support

Add a new record

Add a record from the add form, with a quick row in the table, or from the add button in a Kanban column. You can choose several assignees, and the record may be merged into an existing one by the duplicate rule.

4 min
Before you start · for managers and agents
The add permission on the unit
  • You need: The add permission on the unit

Steps

1
Open the unit from the sidebar and press Add.
2
Fill in the fields. Required fields must be filled in before you save.
3
Choose the assignees. You can choose several people; the first is the primary assignee.
4
Attach files to the file and image fields right from the same form.
5
Save.
The record shows at the top of the list, and the assignees get an assignment notification.
6
To add quickly, use the add row in the table, or the add button at the top of a Kanban column.

Adding from a Kanban column

When you add from a specific column, the card takes that column’s value automatically. For example, adding in the “New” column sets the stage to “New”, whatever you type.

Fields that aren’t saved

Computed fields, such as calculation, rollup and serial number, are filled in by the system alone. If you send a value for them, it’s ignored and the rest is saved.

Merging with an existing record

If the unit has a duplicate rule in Unify mode, you may see the message “Merged into an existing record”. The system fills in only the empty fields of the old record, and doesn’t change its assignee.

If you don’t have permission to view the old record, you see the message without a link to it.

If something goes wrong

What you see
Why
What to do
The Add button doesn’t show
Your role denies the add permission.
“More assignees than allowed”
You chose more than 20 assignees.
Reduce them to 20 or fewer.
A merge message showed and no new record was created
The duplicate rule found a matching record.
The status value is refused
Status transition rules don’t allow starting at this stage.

A real example

Namaa Academy
The situation

The receptionist records walk-in prospects by hand.

What they did
  1. She adds the record from the “New” column in the Kanban.
  2. She chooses the responsible advisor first, then the sales supervisor as the second assignee.
The result

The advisor gets a notification straight away, and the supervisor follows up without becoming the primary assignee.

A made-up company, to show the idea. The numbers are rounded.

Good to know

Up to 20 assignees per record.
Without the assign permission, the record is saved with you as its only assignee, and the other assignees are ignored.
Merging doesn’t change the assignee. If you chose an assignee and the record was merged, a notice tells you your choice wasn’t applied.
Did this guide solve it?
If not, we’ll ask what was missing.
Open in Corteksa
Did this guide solve it?

We read every answer. To get a reply, use Contact support.