Skip to main content

Ideas portal FAQ

Find, vote on and share ideas for Freshworks products. Here is how it works and what happens next.

1. Idea stages and what they mean

Every idea has a status. It shows where the idea is today.

How does an idea move from submitted to delivered?
  1. Submitted
  2. Under review
  3. Planned
  4. In development
  5. Delivered

Not every idea makes it to the end. Some stay open for votes as Future consideration. Others are Closed.

You get an email each time the status of an idea you posted, voted on or subscribed to changes.

What does each status mean?
Submitted
We received the idea. It is open for votes and comments.
Under review
Product is looking at the idea.
Planned
The idea is on the roadmap. We have not started building it yet.
In development
Our teams are building it. We expect to release it within 12 months.
Delivered
The idea is live in the product.
Future consideration
We are not planning it now, but it stays open. Votes help us see if demand grows.
Closed
We are not taking this idea forward. See "Why was my idea closed?" below.
Does Planned mean a release date?

No. Planned means the idea is on the roadmap. Timing can change as priorities change. We update the status when work starts and when the idea ships.

2. The basics: from your idea to our answer

Six questions most people ask before they post.

What is an idea?

An idea is a request for a feature or improvement that is not in the product today.

Something broken? That is a bug. Please contact Support so they can help you.

Should I search before I post?

Yes. If a similar idea exists, vote and comment on it instead of adding a new one. Duplicate ideas split the votes, so no single idea shows how many people want it.

How do I submit an idea?
  1. Search. Choose Submit an idea and type a title. Similar ideas appear. Vote on one if it matches.
  2. Describe. Tell us the task you are trying to do and what gets in your way today.
  3. Add context. Pick the product area and tell us how much this affects your team. Add a screenshot if it helps.
  4. Submit. Your idea shows as Submitted.
How will I hear back?

You get an email when the status of your idea changes. To follow an idea you did not post, subscribe to it.

Why was my idea closed?

An idea can be closed for one of these reasons:

  • Merged. A similar idea exists. Your votes move to it.
  • Bug. It is something to fix, not a new request. Contact Support for help.
  • Retired. It no longer fits the product.
  • Already available. The product can do this today.
  • Not planned. We have no plans to build it.

Closed ideas stay searchable, so you can still read the comments.

3. Find ideas and share your thoughts

The quickest way to make an impact is to back an idea that already exists.

How do I find an existing idea?
  • Use the search bar on the Ideas page. Try two or three keywords.
  • Filter by product, so you only see ideas for the product you use.
  • Filter by status to see what is Planned or In development.
  • Sort by votes to see the most requested ideas first.
How do I vote on an idea?

Open the idea and select the vote button. Voting shows us which ideas matter to you. You need to be signed in to vote.

How do I add a comment?

Open the idea and add your comment. The most useful comments say:

  • What you are trying to do.
  • What stops you today.
  • How you work around it, if you do.

"I agree" helps less than a short example from your own work.

How do I follow an idea?

Select Subscribe on the idea. You get an email when the status changes or when someone replies.

I could not find my idea. What now?

Submit a new one. Use a clear title and describe the problem, not only the solution. Then we can see what you need, even if there is more than one way to solve it.

Have a bug or a question about how a feature works? Contact Support instead.

Ideas Status Pipeline

Filter by idea status

Filter by product

8947 Ideas

gkurconApprentice

LDAP authenticationClosed

Hello,We just started our Freshservice trial this weekend and are impressed with what we've seen so far-but I see some room for improvement for authentication.  While the single sign on option for Active Directory is a nice touch, I would suggest an option to use LDAP authentication.  Essentially your customers would enter an IP for their AD server, a username and password with read-only rights to AD, the appropriate search base information etc.  Once this is in place requesters can sign in from anywhere, not dependent on being able to access the internal IIS server running the AD script. In reality you could use both of these methods together-enable a check box on the sign in page to use single sign on when you are within the corporate network-just like the feature for VMware web client.  When you're not on the corporate network the requester can just enter their email address (or domain user ID and AD password).I realize you can achieve similar results by making the IIS server available publicly either through port forwarding or putting it in a DMZ, but if you implement my suggestion as mentioned above and supply a range of IP's for your servers that are making the LDAP requests, the customer can easily open up the necessary ports on their firewall and specify the allowed IP ranges for those ports.  Seems like a more secure option in my opinion...I'm more than happy to be educated to the contrary.  We currently do this with our SaaS vendor for email security/spam filtering.  The end users just sign in with their email address and use their windows password..from anywhere.  It works quite well.

quentinApprentice

Security IssuesClosed

The longer I use the product the more concerns I have. 1) My portal configuration is set up so that users can't register for access from the portal. However, that doesn't matter if the user sends in an email because the user is registered as an activated contact when the email comes in. This allows the user in question to use the recover password function on the portal to effectively create a login on the portal. This bypasses the activation email and the security setting on the portal.2) If a contact changes roles at a company and is no longer authorized access to the portal, the only recourse is to delete the contact. There is no disable access capability on a per contact basis.3) Emails to the support@yourcompany.com email address from new contacts by default send out an activation email to the customer. Admins must disable that email notification. Even then that doesn't stop a user from access the portal though. The user in question can do a password recovery and get access to the portal.What I would like to see is better control over who has access to the portal. Just because someone sends in an email does not make them an authorized user for the portal. There needs to be a configurable option for portal access. A way of doing this is with a checkbox in the contact details that says "Allow Access to Portal" and a slider in the portal settings, "Allow all contacts access to the portal" that acts as a global setting. If the slider in the portal settings is set to yes then the checkbox is grayed out as an option in the contact details. It's a relatively straightforward solution but not the only one. I'd really like this addressed before my next annual renewal. If not I'll have to start looking for a different solution provider that does give me the level of security and control I need.

This ideas board reflects customer feedback and our current thinking, and is provided for informational purposes only. Roadmap decisions, including AI-related capabilities, are influenced by many inputs beyond customer votes, such as technical feasibility, security, compliance, and market conditions. They are subject to change without notice. Idea status labels (such as “Under Review” or “Planned”) do not constitute a commitment, promise, or legal obligation to deliver any feature, functionality, or timeline, and are not part of any agreement with Freshworks. Development and release of any product or feature remain at Freshworks’ sole discretion.