Okta Access Request Support For Custom Domains And Email Templates
Last Updated:
Overview
Okta Access Requests supports authenticating against a custom domain, but it does not currently support custom email templates. The overall URL for Access Requests remains <tenantname>.at.okta.com, and all notification links point to this URL. As an alternative, Okta Workflows can be used to generate custom emails when request tickets are created or resolved.
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Okta Identity Governance
- Okta Access Requests
Solution
How are custom emails generated for Okta Access Requests?
Configure Okta Workflows to trigger upon request creation or resolution, retrieve additional request details via an Application Programming Interface (API) call, and send a customized email through a supported platform.
- Utilize the Okta Workflows Access Request Created or Access Request Resolved cards to generate emails when request tickets are created or resolved. Configure the Access Request Resolved card in Okta Workflows to trigger the flow and output the request details.
- Make an API request back to Okta to gather further information about the request, as the created and resolved cards only provide general information.
- Compose an email template and send an email with an email action card using platforms such as Gmail or Office 365 once the pertinent information is obtained. Construct a flow that triggers upon request resolution, reads the request details via an API call, and sends a formatted email using a connector such as Gmail.
Okta Workflows can also be extended to include creating tickets in third-party systems, such as an IT Service Management (ITSM) tool, or updating an online spreadsheet.
NOTE: Email notifications are configurable by the end user only. To avoid receiving emails directly from Access Request, the end user must access the Access Request console, navigate to the View Profile page, select Edit Profile, choose Preferences, and deactivate email notifications.
