Adding & Editing Records

Nothing in this app saves behind your back. Edits collect where you can see them, you save when you are ready, and if someone else changed the same record first, you decide what happens. This page shows the whole editing flow.

Opening a record

Click any row in a list to open the record's detail page. The page is built from panels (widgets) — contact details, phones and emails, notes, activity, and whatever extra panels the record's roles bring along (see Roles & Extension Fields).

Adding a record

1. Click + Add contact on a list. A small create window opens on top of the list.
2. Fill in the fields. Required fields are marked; validation messages appear next to the field if something is off.
3. Click Save. The new record opens, or is selected back into the field you came from if you started from a dropdown's "+ Add new".

New contacts are automatically placed in the space's default group if you did not pick one — every contact always belongs to at least one group.

Editing a record

1. On the record page, click Edit. The button only appears if you are allowed to edit at least one panel.
2. Edit fields across any panels you can change. Panels you cannot edit stay read-only even in edit mode.
3. Each panel with unsaved changes gets a badge, and the Save / Cancel bar stays pinned at the top.
4. Click Save.

Each panel saves separately, and the page reports the outcome honestly: "2 saved · 1 failed" means exactly that. A failed panel keeps your changes, stays in edit mode, and shows its error inline — the other panels' saves are already safely stored. Fix the problem and save again.

The edit cart

Inline edits — changing cells directly in a list, and forms that use cart mode — collect in an edit cart instead of saving one by one. Think of it as a shopping cart for changes:

• Every entry shows the field, the old value and the new value, so you can review before saving.
• Remove an entry to revert that change. Clear all empties the cart (with a confirmation).
• Save all, or tick some entries and Save selected — the rest stays in the cart for later.
• Group the entries by row or by column to review them the way you think.
• The cart badge shows the pending count wherever you are.

When someone else changed the record first (conflicts)

If a record changed on the server between the moment you loaded it and the moment you saved, the save stops and a conflict dialog opens. It shows, for each field you changed: your change, the current server value, and your original. You choose:

1. Reload — discard your changes and take the server's version.
2. Force save — overwrite with your version. This needs the conflict-resolve permission and is recorded in the audit log.
3. Merge manually — go field by field and pick which value to keep, then save the merged result.

If you do not have the conflict-resolve permission, the force option becomes Request override, with two paths:

• Manager override — a colleague who does have the permission enters their own credentials right there, and the save is applied under their name.
• Send for approval — the save is parked and the people who can approve it are notified. The entry waits in your cart marked "Awaiting approval" until they decide.

Extra confirmation on sensitive actions

Deleting records and certain other sensitive saves ask you to re-enter your password once before proceeding. Even if several panels need it in the same save, you are asked exactly once.

Related pages

• Working with Lists — inline editing and bulk edits feed the same cart.
• Contacts — what all the panels on a contact page mean.