Feature Requests

Right now when I create a video walkthrough for clients, I invite a separate personal email as a guest. I have to use an alias with Gmail so that when I log in I only see their site. It would be nice if, as the admin, I could just switch into a different view and see what my guest would see, without all the other sites, instead of using multiple aliases/hacks to see what a new guest sees.

I would like to have a dedicated user activity dashboard in Marker.io that shows active and inactive users, as well as their last active dates. This feature would help me track user activity more effectively across the account, rather than just at the project level.

Allow users to send all Marker.io emails (invitations, notifications, feedback, etc.) from their own custom domain . Give admins the option to remove all Marker.io branding from outgoing emails, including logos, footers, and text. Let project owners choose whether emails come from the admin’s or a team member’s address , instead of “ no-reply@marker.io ”. Use Case Some clients don’t recognize emails from Marker.io and delete or ignore them. Emails sent from “@ marker.io ” often land in spam or junk folders . Sending messages from a familiar domain (e.g., the client’s own company) would help improve trust and deliverability . Goal Make it possible to fully whitelabel email communication so users can maintain brand consistency and ensure clients receive important notifications.

As a developer, I would like to use the Marker.io MCP server to allows AI agents (like Claude) to directly access and analyze bug reports and issue data. The MCP server should provide AI agents with: Core issue data: Read access to issue titles, descriptions, and screenshots from reported bugs Technical context: Access to console logs, network requests, browser info, and other diagnostic data captured during bug reporting Conversation threads: Ability to read the full conversation history and additional context added by team members on each issue This would enable AI agents to help with providing debugging suggestions, identify patterns across issues, and assist in writing fixes - all with full context from the original bug reports. Use cases: Automated bug analysis and categorization AI-assisted debugging with full technical context Pattern recognition across multiple issues Generating fix suggestions based on error logs and screenshots

Allow users to manage multiple Marker.io accounts using the same email address. Feature Overview Enable a single email address to be associated with multiple Marker.io accounts. Provide a simple way for users to switch between accounts (e.g., a dropdown menu or similar UI element). Use Case Large teams often work with external agencies or vendors, who may already use their own Marker.io accounts. Internal teams may also want to maintain separate Marker.io accounts for internal projects and external collaborations. Currently, Marker.io does not allow the same email address to be used across multiple accounts, causing potential confusion and making it harder to collaborate. Teams rely on aliases to work around limitations. Benefits Simplifies collaboration between internal teams and external agencies. Reduces confusion when managing projects across multiple accounts. Removes the need for workaround solutions, such as email aliases. See here for advice on using email aliases as a workaround for now: https://help.marker.io/en/articles/8370234-can-i-have-two-marker-io-accounts-with-the-same-email-address

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.

We are considering the following feature: the ability for teams to choose where their data is stored instead of everything being hosted only in the EU. Feature Overview Let organizations pick their preferred hosting region (e.g. US, Canada, APAC, EU). Option to set this at the workspace or organization level. Show clearly where data is stored so teams know. Use Case Some companies must keep data in a certain country because of local rules. Clients ask for data to stay in their own region.

Let workspace admins create and manage user groups (like Dev Team, Designers, or Marketing) that can be added to or removed from projects all at once. --- Feature Overview Let admins create custom user groups within the workspace. Assign or remove entire groups from projects instead of managing one person at a time. Groups could be things like: "Developers", "QA", "Designers", or any custom name. Members of a group would get the same project access as the group. Changes to group membership would automatically update project access. --- Use Case Right now, people with lots of projects or large teams have to manually add or remove users one by one. This gets frustrating and time-consuming, especially when managing multiple internal teams. Being able to turn access on or off for a whole group would save time and reduce mistakes.

Allow users to group projects into folders or categories, such as by client or site type. Provide a way to view and manage grouped projects in a single dashboard. Include an option to search across grouped projects for specific issues or modules. Use Case Teams managing multiple projects for the same client (e.g., multi-site builds) want to view all related projects together. Users need a quick way to track similar issues (e.g., "header bugs") across several projects without switching between individual dashboards. Agencies working with multiple clients can organize projects by client or priority. Benefits Save time by allowing users to focus on related projects and issues all at once. Make it easier to track recurring issues across similar projects, helping teams address them faster. Improve visibility for teams and managers by grouping related projects together. This feature would be especially helpful for agencies or teams managing many websites or projects with similar structures.

As a user, I'd like to delete all the old data before a certain date (2023 for example) from my workspace. One of the other goal is data decarbonisation. Teams are trying to delete anything that it is no longer needed but that is still stored somewhere and therefore consuming energy and polluting the environment.