Skip to Main Content
Customer Feedback

We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.

For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.

Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.

ADD FEEDBACK

Content Management

Showing 348 of 1595

Copy link text button in link dialogue

I often link to other articles by writing the link text, selecting the text, copying the URL I want to link to, and then pasting the URL into the link dialogue. At this point, I have to add the link title, and most of the time I want to use part o...
over 3 years ago in Content Management / Editing 0

Hide broken links on expired content from Link Status report

Currently, the Link Status report shows broken links that are present on expired pages. I would prefer it if broken links on expired content could be excluded from the report. This could be configurable. Jira ticket
over 3 years ago in Content Management / Technical 1 Future consideration

Add CMS login auditing

Add historical logging of CMS user logins, including IP address and date and time.This will allow admins to view and track information about possible login hacking attempts and to mitigate these issues.
over 3 years ago in Content Management / Roles and Security 0 Future consideration

Improved Workflow Approvals

As a content editor I require parallel approval workflows and the ability to define workflows where I can e.g. skip an approver if needed, providing more detail on the reason for skipping. This will improve my effectiveness as currently we rely on...
over 3 years ago in Content Management / Collaboration & Approval 0

Audit Content

As a group of content management users we have a number of needs to audit our content including the abilities to: Assign review groups of users to pages Assign a review date and frequency of review Email alerts Reminder emails Report of overdue to...
over 3 years ago in Content Management / Content Manager 0 Future consideration

Audit change for the "Visible to" Permissions

Currently, it's not possible to know who is changing permissions to the "Visible to" It's standard to be able to monitor changes made to areas that handle permissions. Could you please add this to the change log?
over 3 years ago in Content Management / Roles and Security 1

Move the EPiServer.DataAbstraction.Activities.Internal.IActivityTypeRegistry to public API

Move the EPiServer.DataAbstraction.Activities.Internal.IActivityTypeRegistry to public API as we needed it when creating custom activities to be able to register those (yes we can now, but the Internal namespace indicates to us that this could cha...
over 3 years ago in Content Management / Technical 0

More Granular Access Rights Assignment

Local editors should be able to edit some pages and without direct root (admin) access. Access rights need to dictate the following for a role which languages and site areas the role has access to and what editing rights.
over 3 years ago in Content Management / Roles and Security 1 Investigating

Archive old projects automatically

Automatically archive projects that have not been used for a certain amount of time.
over 3 years ago in Content Management / Collaboration & Approval 0 Future consideration

Support SVG

Support SVG's. E.g. https://world.episerver.com/blogs/Ben-McKernan/Dates/2015/7/supporting-svg-images/
over 3 years ago in Content Management / Technical 1 Future consideration