Read-Only States

Read-only states let information remain visible while preventing users from editing it.

They help protect data when values should be checked, referenced, approved, imported, calculated, or controlled by another process.

When to Use Them

Use read-only states when users need to see information but should not change it directly.

For example, a field might become read-only after approval, imported data might be shown for reference, or calculated values might be displayed without allowing manual edits.

What Project Managers Should Decide

Project managers should clarify:

• which fields users may edit
• which fields should only be displayed
• when editable information should become locked
• who, if anyone, can override a read-only state
• whether read-only information needs explanatory text

Design Goal

Read-only states should make responsibility clear.

Users should understand whether a value is locked because of permissions, workflow state, source system ownership, or because the value is calculated.