Process Hub · Lifecycle stages and record actions

Configure stage field access and who may work

Set capture/edit rules before submission and at each lifecycle stage.

On this page

Before you start

  • Have lifecycle states and global field rules configured. Identify the fields and repeated sections each role should edit at each stage.

Worked access matrix

On smaller screens, scroll the table sideways to see all columns.

StageIntake fieldsQuality findingResolution notes
Before submissionEditableHiddenHidden
NewEditable when globally allowedRead-onlyRead-only
Quality reviewRead-onlyEditable when globally allowedRead-only
ResolutionRead-onlyRead-onlyEditable when globally allowed
ClosedRead-onlyRead-onlyRead-only

Follow these steps

Screenshots use fictional training data. Names, dates and amounts are examples. Select an image to view it at full size.

  1. Open Business lifecycle and record actions and review Before submission. Set the field and collection access needed while adding or saving a draft.
  2. For each submitted state, choose work access: Anyone with process access or Assigned user or role claimant. Confirm the corresponding assignment/handoff exists.
  3. Set individual fields to Inherit global behaviour, Hidden, Read-only or Editable when globally allowed. Use bulk controls only after reviewing their effect on every field.
  4. For repeated sections review add/delete/duplicate/reorder capabilities. Stage access is intersected with the global section capabilities.
    Quality review access panel with stage work access and per-field Read-only or Editable settings.View full size ↗
    In this example, Quality finding is editable during Quality review while the case details remain read-only. Resolve the separate lifecycle validation warning before publishing.
  5. Save, publish and deploy. Test an unclaimed role task, its claimant, another member of the role and a user with process access but no ownership.
  6. Move the same record through every state. Confirm prior evidence remains readable as intended and later-stage required fields become editable when needed.

Test as the actual worker

Use a member account with the intended role, not only the builder’s account. Claim the Quality task and verify that an unassigned care user cannot edit its review evidence.

What you should see

The intended person can edit the appropriate values at each stage while global protections continue to apply.

If something goes wrong

Editable when globally allowed still gives a read-only field

Global read-only/hidden rules, calculated fields and provider-protected values win over a stage’s permissive setting.

Hiding a field was expected to delete or secure its value

Hidden changes presentation. It does not erase stored data or replace process/record access controls.

An administrator cannot bypass a missing required value

An ownership override does not bypass field protection, validation or profile boundaries. Correct the configuration or supply valid evidence.

Need a hand?

Contact your organisation’s Emplyr administrator using your usual internal support channel.

How to ask for help