Feature Requests
Ask the Permit.io team for a capability, or add your vote to a request someone else opened. This page is for developers and technical decision makers who need something Permit does not do yet.
Before you submit a request
- Confirm the capability has not already shipped. See Changelog.
- Confirm Permit is not already building it. See Roadmap.
Submit or vote on a request
The Permit.io feature requests board runs on Canny. Each post has a title, a description, a vote count, and comments. Sort the list by Trending, Top, or New, and filter it by status: Under Review, Planned, In Progress, or Complete.
- Open the Permit.io feature requests board on Canny.
- Search the board for a request that matches your need. A status filter you applied earlier hides posts in other statuses, so remove the filters before you decide that no post matches.
- Vote on the matching request, and comment with your use case. If no request matches, choose Create and describe the authorization model, deployment, or integration that needs the capability.
Your request is submitted when it appears on the board with your vote on it. Creating, voting on, and commenting on requests requires a Canny account.
Canny holds the public request backlog. Productlane holds the published roadmap, with the ideas the Permit team has put on it. The Permit team links a reviewed request to a roadmap idea, so a request that Permit accepts can appear on the Productlane roadmap as well. Post on Canny, then follow the status on whichever board shows your request.
Escalate a request that blocks you
A board post is a public request, not a support ticket. When a missing capability blocks a delivery date, email support@permit.io with your use case and the board post link, or book a call with Permit.
Related pages
- Roadmap for the ideas that are in progress or completed
- Changelog for the release date and version of a capability that already shipped
- Ask the Permit community on Slack for help with a problem you can solve today