> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lumos.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Respond to a Request from Lumos

> You got a message from Lumos asking you to do something. Find your message below to see what it means and what to do.

Lumos asks people across your company to approve access, set up accounts, and review who has access to what. Most of these requests arrive as a direct message from the Lumos app in Slack. Your company may have given the app a different name or icon.

Find the message you got in the table below. Most requests take less than a minute.

## Find your message

| The message starts with | You got it because | What to do | Full guide |
| :- | :- | :- | :- |
| **New Access Request to** an app **for** a person | You approve access to that app, or you're the person's manager | Click **Approve** if the access looks right, or **Deny** if it doesn't. To grant a different level of access, click **Edit** to open the request in Lumos and change it there before you approve. | [Approve or Deny an Access Request](/kb/quick_start_guide/appstore-1/appstore_explainers_for_new_employees_new_to_appstore/approving-access-requests) |
| **Provisioning Required** or **New Account Requested** | You're an admin of the app, and the request was approved | Create the account or grant the access in the app itself. Then click **Confirm Provisioning** (or **Confirm Account Creation**). Click **Deny** if the person shouldn't get access. | [Confirm Provisioning for an Access Request](/kb/quick_start_guide/appstore-1/appstore_explainers_for_new_employees_new_to_appstore/confirming-provisioning-for-access-requests) |
| **Deprovisioning Required** or **Account Deprovisioning Required** | You're an admin of the app, and Lumos can't remove someone's access automatically. This happens when time-based access ends, when the person's role or other attributes change, or when a workflow such as offboarding removes their access. | Remove the access in the app itself, then click **Confirm Deprovisioning**. If the message is part of an offboarding, it shows **Mark as Done** and **Account doesn't exist** instead, like the offboarding row below. | Not needed. The steps are in the message. |
| **Access Review** and a number of accounts to review | You were assigned as a reviewer in an access review | Click the button in the message to open your review in Lumos. Decisions are made in Lumos, not in Slack. | [Complete Your Access Review as a Reviewer](/kb/quick_start_guide/access_reviews/access_reviews_for_new_to_access_reviews_employees/access-reviews-reviewer-walkthrough) |
| **Offboarding** a person | Someone is leaving, and Lumos can't remove their account from an app you manage automatically | Remove the person's access in the app. Then click **Mark as Done**. If they never had an account, click **Account doesn't exist**. | Not needed. The steps are in the message. |
| **Action Required: Do you still need access to** an app? (or **license for** an app) | You haven't used the app in a while | Click **I Still Need Access** to keep it, or **I Don't Need Access Anymore** to give it up. For a license, the buttons are **I Still Need the Advanced License** and **I Don't Need the Advanced License**. | Not needed. The steps are in the message. |
| A number of days, then **Days Inactive: Can We Remove** a person **from** an app? (or **Downgrade** their license) | You manage the app, and someone hasn't used it in that many days | Click **Remove User** (or **Downgrade User**) to take the access away, or **Keep User's Access** if they still need it. | Not needed. The steps are in the message. |
| **Your access to** an app **is expiring soon** | You requested access for a set amount of time, and most of it has passed | Click **Extend App Access** to ask for more time. This sends a new request, which goes through approval again. If you don't need more time, do nothing. | [Request Access to an App](/kb/quick_start_guide/appstore-1/appstore_explainers_for_new_employees_new_to_appstore/requesting-access-to-an-app) |

**Asked to review an access policy?** Lumos doesn't send a message for these yet. The person who wants your review sends you a link. See [Review an Access Policy as a Policy Reviewer](/kb/life_cycle_management/reviewing-an-access-policy-as-a-policy-reviewer), or [as the Policy Owner](/kb/life_cycle_management/reviewing-an-access-policy-as-the-policy-owner) if you own it.

## Before you approve

* **Not the right person to approve?** Reassign the request from the Task Center instead of denying it, so the requester doesn't have to start over. See [Reassign an Access Request](/kb/quick_start_guide/appstore-1/appstore_explainers_for_new_employees_new_to_appstore/reassigning-access-requests).
* **Need more information?** If the message invites you to reply in its thread, your reply goes to the requester. Otherwise, contact them directly.
* **Only see a Review Request button?** Your company approves requests in Lumos instead of Slack. Click **Review Request**, log in, and approve or deny the request there.
* **Got an email instead?** Some companies send requests by email or Microsoft Teams. The email links to the request in Lumos, where you approve or deny it.

## FAQ

**Someone else already approved this request. Do I still need to act?**
No. Once a request moves on, Lumos removes the buttons from your message, so there is nothing left to click.

**What happens if nobody responds?**
A request waiting for approval expires after 14 days with no activity. The requester has to submit a new one.

**I don't recognize the app or the person. What should I do?**
Don't approve it. Deny the request, or ask your IT team who should handle it.

Questions about Lumos at your company? Contact your IT team.