> For the complete documentation index, see [llms.txt](https://docs.lollipop.gg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lollipop.gg/lollipop-authenticator-for-chrome/approve-or-reject-requests.md).

# Approve or reject requests

Lollipop pages can send sign-in or signing requests to the Authenticator.

Read the request carefully before approving. If you do not recognize the request, click **Reject**.

## Approval request

![Login request screen](https://3764565543-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQKjec3KUOsY9wSOPFigE%2Fuploads%2Fgit-blob-0415d5d081a8c5e91e8e6dafc67fdf75e2e6208f%2Flogin-request.png?alt=media)

The request screen shows the action being requested and gives you the choice to approve or reject it.

## Pending approval

Sometimes the Lollipop page will show a pending approval state while the Authenticator request is open.

![Pending approval screen](https://3764565543-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQKjec3KUOsY9wSOPFigE%2Fuploads%2Fgit-blob-99670da3c4a2afce4c0bf2dc4cece0b40030d9bc%2Fpending-approval.png?alt=media)

The pending screen waits for you to approve the request from the Authenticator window.

After you approve, the page should update automatically.

## Locked before approval

Some requests may require you to unlock first. Unlock with your local password, then continue with the approval flow.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lollipop.gg/lollipop-authenticator-for-chrome/approve-or-reject-requests.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
