What the statuses mean
| Status | Meaning | Your next action |
|---|---|---|
| Ready | The planned operation has the required information to be attempted after approval. | Verify its destination path, recipient, and access level. |
| Needs review | The source pattern or control needs an explicit decision or manual handling. | Read the reason. Do not assume it will run with the ready entries. |
| Blocked | A required content match, identity, permission, or other prerequisite is missing. | Fix the cause, save the relevant decision, and prepare again. |
| Skipped | The plan does not create a separate grant for this entry. | Check the reason; inherited and standard site access are common examples. |
Review the actual changes
- Use All to see the overall scope, then inspect Ready, Needs review, Blocked, and Skipped.
- Compare each source and destination file/folder path. Check that the right migrated copy was matched.
- Verify the person or group and the proposed Read or Edit role.
- For an external-email decision, confirm the invitation effect shown for a new guest.
- Use search and pagination to inspect larger batches. Export access review if you need an offline record.
- After fixing mappings or exclusions, prepare again and review the latest generation before approval.
Why approval may be unavailable
A batch with no ready changes has nothing eligible to execute. When unresolved identities are the blocker, the Review step guides you through their decisions instead of offering an approval action that cannot restore anything.
Ready is a planning status, not proof that access already exists. Only the later destination verification establishes the execution result.