Feature Requests

When new members join, especially through domain auto-join, billing happens automatically but without much context. Admins often only see the changes later on their invoice, which can be confusing. We’re considering: More details on invoices Show member names or emails next to seat changes so it’s clear who joined or left. Simple billing notifications Send a short regular email listing recent member changes and how billing was affected. Basic activity log in the app A lightweight list of recent member changes with billing info. Upfront billing warnings Add a simple message when adding a member or when domain join is active, to make it clear that this will increase seat count and cost.

Detect when a website is behind basic authentication (like .htaccess). Prompt the user to add their login details directly in Marker.io . --- Use Case Some users report not being able to capture screenshots of their site. One main reason: the site is behind basic authentication. Right now, they often don’t realize they need to set up credentials in Marker.io . With an automatic prompt, users can quickly enter their details and avoid broken or incomplete screenshots. --- Reference Current instructions: Basic Authentication setup guide

We’re exploring the idea of letting teams collect feedback by email. Feature Overview Each project could have its own unique email address. When someone sends an email to that address, it could create a new issue in the project. We’re also looking at ways to include useful email details (like attachments or subject lines) to give enough context without extra steps. Use Cases Not everyone wants to use widgets or log into a new tool to share feedback. Some people just prefer email. This idea would make it easy for them to send their thoughts while keeping everything organized in one place. Internal Feedback Teammates who don’t have the widget (e.g., QA, account managers, execs) could simply email the project address. Example: A tester spots a bug on their tablet, sends an email, and the issue appears in the project. Client & External Feedback Agencies could forward client emails directly to the project address instead of retyping them. Or, they could share the project email address with clients , so they can send their feedback straight in. Example: A client’s support agent forwards a checkout bug email to the project address, and it shows up in the backlog. Why This Could Be Useful Keeps all website feedback in one place. No learning curve. Just send an email. Less copy-pasting and manual ticket creation. Works for teammates, clients, and external tools. We’d Love Your Thoughts Please comment below with how you’d use something like this, any specific needs, or examples from your workflow. The more context we have, the better we can deliver it.

Feature Overview Allow teams to embed Marker.io on sites that use a strict Content Security Policy (CSP) without requiring unsafe-inline in style-src . This would make it possible to use Marker.io while keeping strong security rules in place. Use Case Some customers use strict CSP to meet security standards. Right now, Marker.io requires unsafe-inline for styles, which blocks these teams from using the embed. Nonce or hash-based alternatives aren’t supported at the moment.

Flexibility in Changing Widget Destinations Allow users to change the connection of their existing Marker.io widget to different project management tools or to different projects within the same tool. This feature aims to provide greater flexibility and ease in managing project transitions. Current Limitation At present, once a Marker.io project is created, it cannot be switched to a different integration or a different project within the same tool without creating a new Marker.io project. https://help.marker.io/en/articles/6868805-how-do-i-change-the-endpoint-of-a-project

Right now, some users need to log into Marker.io to see the widget on a website. We want to remove this requirement and let teams decide exactly who gets access. How It Could Work Teams could choose who sees the widget, without requiring a Marker.io login. Options might include: Everyone Only internal team members Only logged-in users on the website Only people with a special invite link Only visitors from a specific country or region Only on certain pages etc

Currently there are extensions for Google Chrome, Firefox, and Edge. We would like to see an extension created for Apple's Safari browser.

Enable the ability to create and manage custom statuses for feedback in Marker.io . Allow users to map these custom statuses to statuses in connected tools (e.g., Jira, ClickUp, GitHub). Use Case Greater Flexibility : Users can better match their workflows by defining custom statuses (e.g., "In Progress," "Pending Client Response," "In Review"). Better Visibility : Clients and team members can see more detailed task progress directly in Marker.io . Workflow Mapping : Sync multiple statuses from external tools like Jira to Marker.io for status updates (e.g., map Jira statuses like "In QA" or "Ready for Staging" to Marker.io custom statuses). Guest Collaboration : Allow guests to see more granular task statuses, keeping them informed about ongoing progress. Benefits Improved Communication : Teams and clients can understand the status of a task at a glance, ensuring everyone stays on the same page. Better Tracking : Project managers can easily distinguish between tasks needing attention versus those waiting on client input or external factors. Integration Compatibility : By supporting status mapping with integrations, teams can align Marker.io with their existing workflows.

Feature Overview Provide more detailed and flexible analytics across multiple projects, allowing users to gain a deeper understanding of their data. Use Case Track key metrics such as the most active reporters across all projects. View total open issues across the entire project base. Analyze average first response time and resolution time. Allow for more flexible time period adjustments for reports. Enable users to export analytics for further use. Page loads of each marker.io project/wiget Benefits Break down issues based on: Issue type Country Browser Screen size Team Date created This would give users a clearer view of their overall project data and help them make more informed decisions based on these insights.

Collecting votes here for a potential Marker.io integration with: https://www.kantata.com/