> For the complete documentation index, see [llms.txt](https://docs.notionapps.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.notionapps.com/frequently-asked-questions/automation-where-do-approval-requests-appear.md).

# Automation: Where do approval requests appear?

## Automation: Where do approval requests appear?

### Automation: Where do approval requests appear?

#### Automation: Where do approval requests appear?

Approval requests should appear on the native screen that was selected as the workflow destination. In the builder, use the actual screen names: **Decision** for a reviewer decision, **Work Queue** for team-owned approval lists, and **Workflow Status** for requester progress.

The Decision screen is required when the reviewer must approve, reject, or request changes. The Work Queue only answers, "What needs my attention?" The Decision screen answers, "What decision am I making now?"

If you are building the approval from scratch, create the screens in this order:

1. Create the requester data or form screen.
2. Create or generate the approval workflow.
3. Add a **Work Queue** Automation screen for the reviewer inbox.
4. Add a **Decision** Automation screen for approve, reject, and request-changes actions. Do not skip this screen.
5. Bind both screens to the same approval workflow.
6. Make the Work Queue and Decision screens visible to reviewer roles.
7. Hide reviewer-only screens from requesters unless the app intentionally allows requesters to see them.
8. Submit a test request as the requester.
9. Open the Work Queue as the reviewer.
10. Open the request and decide it on the Decision screen.

![Decision screen type.](https://firebasestorage.googleapis.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5ZqDXcVVffWUqEIZVhmn%2Fuploads%2FaqLbH5XFz43EB7jYCpbk%2Fautomation-screen-decision-builder-20260705.png?alt=media\&token=70e8a8ee-525e-4d63-bda7-f39a8b99b6c9)

*Decision screen type.*

**What to check**

* The workflow destination is Decision or Work Queue.
* The Work Queue screen was actually added to the app when reviewers need an inbox.
* The Decision screen was actually added to the app when reviewers need approve/reject/request-changes buttons.
* Both screens are bound to the same approval workflow.
* The reviewer role can access that screen.
* The reviewer role can access the source record.
* The screen is not filtered in a way that hides the item.
* The request was submitted through the real user action.

Read Decision and Queue Troubleshooting if the item is missing.