Submit requests from Slack
Users can submit requests directly from Slack if you have integrated Slack with Access Requests, configured settings for Slack, and you have at least one active request type or condition. They can manage the entire lifecycle of a request through a Slack channel. Any messages and actions within Slack are also reflected in the Access Requests web app.
-
When users submit requests using Slack, they use the chat's app session and not the Okta session. Keep this in mind when you configure global session and app sign-in policies for your org. See Considerations and best practices for integrating Slack and Microsoft Teams.
-
You can control if users can submit and approve requests in Slack. See Configure settings for Slack.
By default, all users can view requests. You can mark a submitted request as private, or you can update your team settings to mark all incoming requests for the team as private.
Users can submit requests from Slack by sending a message to the Okta bot with the resource or request type that they are looking for. Users can perform the following steps:
- Contact the Okta bot.
- Tag the
@Oktabot in a channel that includes the bot. - Use the
/accessSlack slash command in a channel that includes the bot. - Go to the Access Requests app > Messages tab.
- Tag the
- Enter the resource name or request type.
- Review the response from the bot and verify that the information is correct.
- Click Continue.
- Enter the required information.
- Click Submit to create the request. Any changes or updates to the request are immediately reflected in the Slack message.
After users interact with the Okta bot or Access Requests app within Slack once, they automatically receive a notification when an action is assigned to them or they're mentioned on a request.
Users can cancel a submitted request using the Access Requests web app if a team member or approver hasn't taken any action on it. They receive a cancellation notification based on the notification preferences that they've set up.
Access Requests also cancels a request if the requester's access to the Access Requests web app is revoked or their status in Okta changes to suspended or deactivated. A request expires if there's no activity in it for 60 days.