Create and edit records

You need write access to the entity and its relevant fields. Viewer access permits inspection rather than mutation; project read-only restrictions can also block writes.

Create or edit

1. Select an entity and choose Create, or open an existing record’s edit action.
2. Fill in the fields shown in the drawer. Use group tabs when the schema divides a long form into sections; All fields shows the combined form where configured.
3. Resolve validation messages next to the affected fields. Validation rules come from the schema, and their messages are generated from the field’s label (“Name is required”, “Stock must be at least 0”), so the wording matches what you see in the form.
4. Choose Save. Reopen the record or reload the list to confirm persistence.

An unchanged record can have a disabled Save button. A read-only field is not editable simply because other fields are writable. Hidden and read-only fields, field groups, and the sidebar’s menu groups and icons are part of the schema; ask the agent to change them, or see conditional fields and field groups for the code options.

Leave safely

Save intended edits before closing, changing scope, or navigating away. Read any unsaved-change prompt rather than assuming navigation saved the form. Creating or editing a related record may open another drawer with its own save action.

Delete

Review the record identity and the effect described by the delete confirmation. For bulk deletion, inspect the selection count. Test deletion workflows only with disposable tutorial records until you understand their relationship consequences. Disconnecting a relationship is not the same as deleting its target.

For blocked writes, check project lifecycle, memberships, and the error message rather than retrying repeatedly.