Look for an existing request first
The feedback boards let you browse feature requests and approved bug reports. You can read public requests without signing in. Sign in with your Glean account when you want to submit a request or vote.
Before adding an idea, look through the relevant board for something similar. If a request already describes the change you want, add your vote rather than creating a duplicate. You can remove your vote later if your preference changes.
Each request has its own page with the description and current status. That gives you a place to return to without having to remember where it appeared in the list.
Explain what the change would help you do
- Choose the board that fits your idea or report.
- Write a short title that describes one specific change.
- Explain the situation you run into and what you would like to be able to do.
- Review the wording for private information, then submit.
A concrete example helps: explain the part of your everyday practice that feels difficult, rather than only naming a button you want. Keep unrelated ideas in separate requests so each can be reviewed clearly.
New requests wait for review before appearing publicly. While a request is still eligible for changes before acceptance, you can edit or delete your own submission. Once accepted, those controls are locked. Contact support if an accepted request needs a correction.
Public wording and private diagnostics are separate
An approved request’s title and description are public. This also applies to bug reports accepted onto the public board. Leave out account details, private prayers, messages, screenshots containing sensitive content, and anything you would not want another visitor to read.
When you report a bug from the iPhone app, diagnostic information—such as app version, build, device model, and iOS version—is sent separately to private support. Those automatically attached diagnostics do not become part of the public request. Review the form’s disclosure before sending.
A signed-out message sent privately to the team is not automatically an account-linked public request. If you need help with your own account rather than a product change, use email support or available private support chat.
Follow progress without checking every day
A request may move through statuses such as planned, in progress, or shipped. Approval means it has been accepted onto the board; it does not promise a release date. Votes help show interest, but they do not guarantee a particular implementation or schedule.
In Glean’s notification settings, you can choose alerts for approval, progress, and shipping of your own requests, and progress or shipping of requests you upvoted. Push alerts also require iPhone notification permission. Muting them does not remove updates from the notification bell.
In the app, open Settings → Feedback & ideas to browse requests, or Suggest a feature to write one. You can also return to the website boards from a browser to read a request’s current status.