Background
You can request access to apps by @-mentioning the Lumos Slack app in a channel, thread or by sending it a direct message in plain language. The Lumos Access Request Agent reads the message, builds a structured access request, and submits it after you confirm. There is no form or special syntax to learn. Requests submitted this way follow your existing approval policies and appear in Lumos under pending requests, just like requests made in the AppStore. Related Articles:When to use this
- An employee needs access to an app and is already working in Slack they message the Lumos app “I need edit access to Figma for two weeks.”
- A manager requests access for a direct report or new hire: “@Lumos get Priya access to Salesforce.”
- Your IT help channel receives frequent access requests, and you want them captured as governed Lumos requests instead of untracked messages.
Prerequisites
- The Lumos Slack app is installed in your workspace
- Apps and entitlements are configured as requestable in your AppStore catalog
How it works
-
Mention
@Lumosin a channel or send the Lumos app a direct message describing the access you need. The agent classifies your message first. If it isn’t an access request, the agent replies with a redirect and no request is created. - Answer the agent’s clarifying question if it asks one. The agent identifies the requester, target user, app, entitlement, duration, and justification from your message. If any of these are unclear, it asks one clarifying question (up to two turns).
- Review the confirmation card. You can approve, edit, abandon, or start over. Editing produces an updated card to review. Lumos never submits a request without your explicit approval on the confirmation card.
- Approve the card to submit the request. The agent replies with the request ID and a link, and the request appears in Lumos under pending requests.
Requesting for someone else
Phrase the request with the person’s name: “get Jamie access to Salesforce.” The agent resolves the target user and records both you (the requester) and the target user on the request.Error handling
- If the message isn’t an access request, the agent replies with a redirect and stops. No request is created.
- If submission to Lumos fails, the agent posts an error message in the Slack thread. You always know whether the request was submitted.
Limitations
- The agent handles access requests only. General IT questions receive a redirect reply.
Install or reconnect Lumos App to grant the new scopes
The Access Request Agent needs three Bot Token scopes that older Lumos Slack installs don’t have. Reconnecting Slack in Lumos adds them to your existing install. You don’t need to uninstall the app.| Scope | Required | Description |
|---|---|---|
| channels:history | ✅ | View messages and other content in public channels that Lumos has been added to |
| groups:history | ✅ | View messages and other content in private channels that Lumos has been added to |
| assistant:write | ✅ | Allow Lumos to act as an App Agent |
- In Lumos, open Integrations and find the Slack card.
- Click Reconnect.
- If your company is on Enterprise Grid, check Is Enterprise Grid?
- Click Connect Slack, choose your workspace, and approve the permissions Slack requests. Click Allow.
- Enterprise Grid only: approve the updated Lumos app for your org and add it to each workspace where you use it. See step 5 in Connecting Slack (Messaging).
- Test it: send the Lumos app a direct message like “I need edit access to Figma for two weeks.”
FAQ
Does this bypass approval policies?No. Requests submitted from Slack go through the same approval workflows, policies, and audit trail as requests made in the AppStore. What happens after I submit?
Lumos notifies approvers through your normal approval flow, and you can track the request from the link the agent posts in the thread.