Feature Requests

Allow the account owner to restrict collaborator access in a way which allows they to prevent collaborators from seeing any content in some workspaces. Example: Access workspace 1 but not workspace 2

Add functionality to support building Auto Webinar or Evergreen Webinars.

Please allow us to hide on the main Dashboard and Orders page the revenue we are making from any collaborator of our choosing. Most roles don't need to be able to see this information.

Hide anything in a Collaborators dashboard that is not connected to there access permission so that they can not see it, there is no need for them to be able to see other sections that they do not have access to, instead of allowing them to see it but not edit it, remove it completely from their dashboard when they login in so that they can only see what is relevant to them.

My use case is that I will be using CF to collect very private customer information, I'd like those things to be on file, but I don't want collaborators (like funnel builders) to see it. This include raw CC payment information. a "CUSTOM" permission system would be appreciated. Create a custom user type name and allow us to check/uncheck permissions such as view contact information, edit contact information, etc etc.

If you have multiple Domains defined then URLs belonging to the Site seem to appear in all domains' sitemaps, even if they don't exist on that domain. This makes the sitemap.xml invalid and it won't be accepted by e.g. Google Search Console. Example: Your Workspace has two domains configured: A.com and B.com . If the Site is configured to live on A.com then the Blog home page (which apparently can't be disabled or removed from the sitemap - I've filed a separate feature request for that) at A.com/blog will appear in both A.com/sitemap.xml and B.com/sitemap.xml . This entry of A.com/blog is invalid in a B.com/sitemap.xml as the sitemap must only contain URLs from its own domain. This seems like a small but fundamental bug in how the sitemaps are generated, and is disappointing given that CF2.0 was meant to be "great for SEO". (Support ticket #3611389 has details of the specific case encountered on our account)

"Like" buttons for blog articles that visitors can hit to show their appreciation for the content.

Create a tool to allow users to upload blog posts so new posts can be created in bulk.

Add a built in contact field for a contacts birthday similar to those for name, address, ect.

Change the ClickFunnels subdomain a team is hosted on ex: change.myclickfunnels.com