IntroductionRecords & TablesStatuses and WorkflowsRead-Only Records

import { Callout } from ‘nextra/components’

Understand Read-Only Records

Goal: Understand why a record may be locked or read-only and what to check next.

Before you start

• Open the record that appears locked or read-only.

Why a record can be read-only

A record can be read-only for more than one reason:

• Your profile may not include permission to edit that type of record.
• The selected yacht may not match the record or action you expected.
• The current status may prevent editing.
• The record may be final, closed, approved, completed, or otherwise protected by its process.
• The table or page may be intended for review only.

What to check

First, confirm the selected yacht. Then check the status shown on the record. If the record includes workflow history, review the latest status change.

If the record should be editable for your role, ask your administrator to confirm your access and whether the current status allows editing.

Result

You understand the likely reason why the record is read-only and know whether to check yacht, permissions, status, or workflow history next.

Related guides

• Statuses and Workflows
• Permissions and Missing Features
• Common First Checks