Submitting a Feature or Enhancement Request using Okta Ideas
Last Updated:
Okta Ideas lets administrators submit feedback, vote on existing ideas, and track request status in one place. Related feedback appears as unified ideas so Product Managers can prioritize high-impact enhancements that align with customer needs. Status updates and notifications help administrators monitor idea progress after submission.
Review the following video for more details.
Applies To
- Okta Identity Engine (OIE)
- Okta Ideas
- Feature requests
- Idea voting
- Request tracking
How Does Okta Ideas Organize Feature Requests?
Okta Ideas groups related feedback into unified ideas based on common themes and use cases. The final title or wording of an idea might look different from the original submission, but the idea retains the original intent and desired outcome.
This approach helps Product Managers review duplicate requests together, prioritize high-impact enhancements, and keep feedback organized throughout the product evaluation lifecycle.
How Can an Administrator Submit Feedback in Okta Ideas?
Submit feedback from the Okta Support Center, choose Community and Okta Ideas, complete Submit Feedback, select the relevant product area, and submit the request.
- Sign in to the Okta Support Center.
- Choose Community from the dropdown menu.
- Select Okta Ideas.
- Select Submit Feedback.
- Fill out the required details.
- Clearly explain the business use case, what the missing feature prevents, and the financial or operational impact.
- Review any related ideas that the portal suggests during drafting.
- Select the relevant product area.
- Select Submit.
How Can an Administrator Vote on an Idea?
Vote from the Okta Support Center after searching for similar feedback, then select Must Have, Nice to Have, or Not Interested on the existing idea.
- Sign in to the Okta Support Center.
- Choose Community from the dropdown menu.
- Select Okta Ideas.
- Search for similar feedback.
- If the idea exists, select Must Have, Nice to Have, or Not Interested.
NOTE: Voting registers support and automatically subscribes the voter to updates about that specific idea.
Who Can Use Okta Ideas?
The following groups can participate in Okta Ideas:
- Okta customers and partners can submit, vote on, and comment on ideas after signing in to the Okta Support Center with Multi-Factor Authentication (MFA) enabled.
- Federal and GovCloud customers can participate by registering for a free Okta Digital Experience Account. Refer to Create an Okta Support Center Account for details.
What Happens After Feedback Submission?
Feedback goes to the Community and Product Operations teams for review. Those teams combine duplicates and surface key ideas to Product Managers.
Votes show community demand, but Product Managers also evaluate technical feasibility and strategic alignment when they prioritize features. Okta sends automated email updates when submitted or tracked ideas progress.
What Do Okta Ideas Statuses Mean?
The Status field shows where a request stands in the product evaluation lifecycle.
| Status | Definition and Stage |
|---|---|
| Community Review | The idea is published and visible to the Community for voting, commenting, and initial prioritization while the team reviews it for clarity and duplicates. |
| Accepted to Backlog | The product team reviewed the idea, confirmed alignment with product strategy and direction, and added it to the development backlog for future consideration. |
| On the Roadmap | The idea is prioritized and currently in the discovery, design, or active build phase. Plans remain subject to change and do not guarantee delivery or a specific timeline. |
| Now Available | The feature is delivered. |
| Not at This Time | The request is declined or archived because it does not align with the current product vision or did not gather sufficient community engagement, though future planning cycles can re-evaluate it. |
What Practices Help an Idea Gain Priority?
The following practices help administrators present stronger feedback and avoid duplicate submissions:
- Search first to avoid splitting community votes across duplicate submissions.
- Rank top ideas by using Okta Ideas prioritization tools.
- Focus on the business problem and impact instead of only a specific user interface design or workaround.
Why Does an Idea Stay in Community Review for a Long Time?
Ideas stay in Community Review while they gather votes and feedback. Clear business impact and a specific use case help the review process because Product Managers can evaluate the request against customer demand and product priorities more effectively.
What Happens to Previously Submitted Feedback?
Previously Submitted Feedback Appears as Unified Ideas
Product enhancements requests look slightly different in the new Okta Ideas portal. Once a collection of feedback is converged into an idea, it will appear in the portal. Contributors will be notified when their feedback becomes a unified idea, as well as when it progresses through the Ideas lifecycle.
If feedback you submitted cannot be found in the portal, rest assured that it is not lost.
Our team is actively reviewing the backlog. Over the next few weeks, the Okta team will continue evaluating past submissions, link feedback to existing community ideas or create new ones.
Finally, to keep Okta Ideas focused and actionable, past submissions are regularly audited. Older requests or ideas that no longer fit the upcoming roadmap may have been archived. If an archived idea is still vital to your team, feel free to submit feedback with updated details on your current use case.
How Can the Okta Ideas Team be Contacted?
Send questions or feedback about the Okta Ideas program or the Okta Ideas portal to Community@okta.com.
