Änderungen an „Mautic Privacy Project wireframes“

Here are the wireframes for some of the screens that will be changed as part of the privacy project. They will all be available through a link to Penpot, an open-source prototyping tool, where you can explore all the interactive wireframes in an experience similar to Figma.

Link: https://design.penpot.app/#/view?file-id=24d9d841-759d-81bc-8008-b6e82597d264&page-id=396483cc-a14b-8039-8008-b6ef8559e95d&section=interactions&index=34&share-id=21f6dcc3-8c72-45c3-9f25-22ec758c7f2c

Because the wireframes are interactive, you can use the controls at the top of the screen to navigate through each of the flows created during the ideation process. While viewing a flow, click on the screen to quickly reveal the interactive areas. You can then click those areas to trigger a change on the screen or move forward in the flow. If these areas are not visible, check the settings available on your screen and make sure the option to show interactive areas is enabled.

These wireframes define the intended user experience, as well as the components that will be added or changed to improve it.

Design engineer: Anderson José Eccel, the UX/UI Tiger Team lead.

Flows

Onboarding

The onboarding flow will allow users to select what they need to do on the platform in three steps. First, they choose their goals. In the second step, the system presents recommended options, including tracking options and similar settings that we recommend enabling to help users achieve those goals. In the third step, users can review a selection of settings that remain disabled by default and enable them as needed.

Preference center tracking control

The Preference Centre will receive a dedicated tracking tab, allowing contacts to easily withdraw any consent they may have given to track their activity and associate it with their individual contact profile. Once a contact disables this option, the system will technically block behavioral tracking for that contact, and any cookies that can be removed will be revoked. To make this functionality reliable, the profile will identify and block events related to behavior. This means that even if a tracking cookie remains—for example, because it cannot be removed in a particular browser—the implementation will account for that scenario and ensure that the contact’s preferences are respected.

The communications tab will be redesigned to present information more clearly and in line with the platform’s current visual direction. We will also improve the way the backend processes this interface.

Audit log

On the audit log screen, a filter panel will allow users to apply different filters and review information from across the system in one place. Initially, information will be displayed in a more compact format. Users can expand an entry with a click to see all the details associated with that event in the audit log. Alert subscriptions will also provide some predefined options and may be expanded in the future to include other types of notifications as the community’s needs evolve.

Permissions

In the role settings, we will add a toggle for the timeline, allowing users to control the visibility of events in a more granular way. In the permissions area, custom fields will be presented for both contacts and companies, with the ability to extend this support to custom objects. The idea is to allow users to set custom permissions for every field, making it possible, for example, to hide personal information from certain users.

Teams

One of the most exciting areas to be implemented is teams. This feature will allow you to manage users by department and control permissions so that, for example, all users on the marketing team or the content team can access only the items created by their department. The feature was designed so that this logic can be reused in different scenarios. For example, when a Mautic instance is being implemented for a multinational organization that divides its marketing teams by country, each country could have its own team, ensuring a complete separation of resources across the platform. In practical terms, it is like having a mini-Mautic within a single instance. Although the design is simple and focused, what you can achieve with this feature is truly remarkable, and it will help many organizations make better use of Mautic.

Privacy Centre

In the Privacy Centre, we will bring together all privacy-related features in one place. We will also dedicate space to concise content explaining how the backend works and how it affects privacy policies and similar documents that organizations generally need to adopt to comply with legislation.

At this stage, the “How it works” tab in the wireframe is just a very basic placeholder, with no final content. The content to be added will depend on decisions the community has yet to make about certain features, as well as on what we learn during the project’s discovery process. For now, please treat it as a concept.

Preference center creation

Since we'll be working on Preference Centres and implementing additional controls in them, we'll also reorganize the backend so that the Preference Centre becomes a standalone entity, separate from landing pages. Treating both as the same type of entity was a workaround that helped address certain limitations in the past, but in the current state of the platform it causes more problems than it solves.

To make this change, we need to preserve at least the current level of customization. The technical approach we chose to improve the Preference Centre creation process while maintaining this customization is to introduce a separate entity called Brands. It will store basic visual identity settings that can be reused to style the Preference Centre and, as support for this is developed, other features across the platform.

Feel free to leave comments directly in this discussion.
This conversation shapes the final solution.