From 3b599e82372e29aecc8a24619d692e1ad2266985 Mon Sep 17 00:00:00 2001 From: "promptless[bot]" Date: Fri, 1 May 2026 06:59:45 +0000 Subject: [PATCH 1/5] Document dedicated Notes permissions Add documentation for the new lead:notes permission model introduced in Mautic 8.x: - Add Notes permission category to managing_roles.rst with explanation of fine-grained note access control - Expand Notes section in manage_contacts.rst with note ownership visibility and permissions --- docs/contacts/manage_contacts.rst | 20 +++++++++++++++++++- docs/users_roles/managing_roles.rst | 25 ++++++++++++++++++++++--- 2 files changed, 41 insertions(+), 4 deletions(-) diff --git a/docs/contacts/manage_contacts.rst b/docs/contacts/manage_contacts.rst index 5722b59b9..ca8c098ca 100644 --- a/docs/contacts/manage_contacts.rst +++ b/docs/contacts/manage_contacts.rst @@ -289,10 +289,28 @@ To export the change log: | +.. _notes: + Notes ===== -It's possible to use Mautic as a basic Customer Relationship Management system (CRM). You or your teammates can write notes for a specific Contact. It's possible to mark a note with a specific purpose; General, Email, Call, Meeting. It's also possible to define a date of a meeting or a call. +You can use Mautic as a basic Customer Relationship Management system (CRM). You or your teammates can write notes for a specific Contact. Mark a note with a specific purpose: General, Email, Call, or Meeting. You can also define a date for a meeting or a call. + +Note permissions +---------------- + +Mautic has dedicated permissions for notes, separate from Contact permissions. This allows administrators to control who can create, view, edit, and delete notes independently of Contact access. + +The edit and delete buttons for notes appear based on your Notes permissions and note ownership: + +* **Edit own** - You can edit notes you created, regardless of which User owns the Contact. +* **Edit others** - You can edit notes created by other Users. +* **Delete own** - You can delete notes you created. +* **Delete others** - You can delete notes created by other Users. + +For example, if you have ``Edit own`` Notes permission, you can edit your own notes on any Contact you can view - even Contacts owned by other Users. However, you can't edit notes that other Users created unless you also have ``Edit others`` permission. + +See :doc:`/users_roles/managing_roles` for details on configuring Notes permissions. Social ====== diff --git a/docs/users_roles/managing_roles.rst b/docs/users_roles/managing_roles.rst index f763c0ee3..93fe8d038 100644 --- a/docs/users_roles/managing_roles.rst +++ b/docs/users_roles/managing_roles.rst @@ -136,10 +136,29 @@ There are additional permissions for specific features: .. vale on -.. note:: +Contact permissions +~~~~~~~~~~~~~~~~~~~ + +The Contact Permissions section includes several permission categories: + +* **Contacts - User has access to** - determines which Contact records a User can view, edit, create, and delete. + +* **Notes - User has access to** - determines which notes attached to Contacts a User can access. This is separate from Contact permissions, giving you fine-grained control over note management. For example, a User might view all Contacts but only edit their own notes on those Contacts. + +* **Segments - User has access to** - determines which Segments a User can access. + +* **Custom Fields - User has access to** - determines whether a User can manage Custom Fields. + +* **Import - User has access to** - determines whether a User can import Contacts. + +.. note:: + + Notes permissions determine which notes a User can view, edit, and delete based on note ownership - not Contact ownership. A User with ``Edit own`` Notes permission can edit notes they created, even on Contacts owned by other Users. See :ref:`notes` for more details. + +.. note:: + + User permissions restrict their view of dashboard widgets, resulting in them only seeing widgets for items or feature bundles they have permission to see. - User permissions restrict their view of dashboard widgets, resulting in them only seeing widgets for items or feature bundles they have permission to see. - For example, if a User's Role doesn't have Asset permissions, they can't create or view widgets on the dashboard for Asset data. You can also create :xref:`Roles using the API`. \ No newline at end of file From ba3724159ccedc781cfce6b8d728e66478d30f86 Mon Sep 17 00:00:00 2001 From: "promptless[bot]" Date: Fri, 15 May 2026 13:14:07 +0000 Subject: [PATCH 2/5] Address reviewer feedback on notes permissions docs Apply all six reviewer suggestions: - Use dashes for CRM abbreviation and add "such as" - Lowercase "notes permissions" consistently throughout - Add vale off/on around Contact Permissions section --- docs/contacts/manage_contacts.rst | 8 ++++---- docs/users_roles/managing_roles.rst | 6 +++++- 2 files changed, 9 insertions(+), 5 deletions(-) diff --git a/docs/contacts/manage_contacts.rst b/docs/contacts/manage_contacts.rst index ca8c098ca..3bbc41b53 100644 --- a/docs/contacts/manage_contacts.rst +++ b/docs/contacts/manage_contacts.rst @@ -294,23 +294,23 @@ To export the change log: Notes ===== -You can use Mautic as a basic Customer Relationship Management system (CRM). You or your teammates can write notes for a specific Contact. Mark a note with a specific purpose: General, Email, Call, or Meeting. You can also define a date for a meeting or a call. +You can use Mautic as a basic Customer Relationship Management - CRM - system. You or your teammates can write notes for a specific Contact. Mark a note with a specific purpose, such as General, Email, Call, or Meeting. You can also define a date for a meeting or a call. Note permissions ---------------- Mautic has dedicated permissions for notes, separate from Contact permissions. This allows administrators to control who can create, view, edit, and delete notes independently of Contact access. -The edit and delete buttons for notes appear based on your Notes permissions and note ownership: +The edit and delete buttons for notes appear based on your notes permissions and note ownership: * **Edit own** - You can edit notes you created, regardless of which User owns the Contact. * **Edit others** - You can edit notes created by other Users. * **Delete own** - You can delete notes you created. * **Delete others** - You can delete notes created by other Users. -For example, if you have ``Edit own`` Notes permission, you can edit your own notes on any Contact you can view - even Contacts owned by other Users. However, you can't edit notes that other Users created unless you also have ``Edit others`` permission. +For example, if you have ``Edit own`` notes permission, you can edit your own notes on any Contact you can view - even Contacts owned by other Users. However, you can't edit notes that other Users created unless you also have ``Edit others`` permission. -See :doc:`/users_roles/managing_roles` for details on configuring Notes permissions. +See :doc:`/users_roles/managing_roles` for details on configuring notes permissions. Social ====== diff --git a/docs/users_roles/managing_roles.rst b/docs/users_roles/managing_roles.rst index 93fe8d038..2dbdedf55 100644 --- a/docs/users_roles/managing_roles.rst +++ b/docs/users_roles/managing_roles.rst @@ -139,8 +139,12 @@ There are additional permissions for specific features: Contact permissions ~~~~~~~~~~~~~~~~~~~ +.. vale off + The Contact Permissions section includes several permission categories: +.. vale on + * **Contacts - User has access to** - determines which Contact records a User can view, edit, create, and delete. * **Notes - User has access to** - determines which notes attached to Contacts a User can access. This is separate from Contact permissions, giving you fine-grained control over note management. For example, a User might view all Contacts but only edit their own notes on those Contacts. @@ -153,7 +157,7 @@ The Contact Permissions section includes several permission categories: .. note:: - Notes permissions determine which notes a User can view, edit, and delete based on note ownership - not Contact ownership. A User with ``Edit own`` Notes permission can edit notes they created, even on Contacts owned by other Users. See :ref:`notes` for more details. + Notes permissions determine which notes a User can view, edit, and delete based on note ownership - not Contact ownership. A User with ``Edit own`` notes permission can edit notes they created, even on Contacts owned by other Users. See :ref:`notes` for more details. .. note:: From b52e1064c92fe6dfd3b94246a13262d95362bec7 Mon Sep 17 00:00:00 2001 From: "promptless[bot]" Date: Mon, 18 May 2026 17:46:19 +0000 Subject: [PATCH 3/5] Capitalize Notes as Mautic feature name Address reviewer feedback to consistently capitalize "Notes" and "Note" throughout the documentation since they refer to a Mautic feature. --- docs/contacts/manage_contacts.rst | 18 +++++++++--------- docs/users_roles/managing_roles.rst | 4 ++-- 2 files changed, 11 insertions(+), 11 deletions(-) diff --git a/docs/contacts/manage_contacts.rst b/docs/contacts/manage_contacts.rst index 3bbc41b53..7cdb4befb 100644 --- a/docs/contacts/manage_contacts.rst +++ b/docs/contacts/manage_contacts.rst @@ -294,23 +294,23 @@ To export the change log: Notes ===== -You can use Mautic as a basic Customer Relationship Management - CRM - system. You or your teammates can write notes for a specific Contact. Mark a note with a specific purpose, such as General, Email, Call, or Meeting. You can also define a date for a meeting or a call. +You can use Mautic as a basic Customer Relationship Management - CRM - system. You or your teammates can write Notes for a specific Contact. Mark a Note with a specific purpose, such as General, Email, Call, or Meeting. You can also define a date for a meeting or a call. Note permissions ---------------- -Mautic has dedicated permissions for notes, separate from Contact permissions. This allows administrators to control who can create, view, edit, and delete notes independently of Contact access. +Mautic has dedicated permissions for Notes, separate from Contact permissions. This allows administrators to control who can create, view, edit, and delete Notes independently of Contact access. -The edit and delete buttons for notes appear based on your notes permissions and note ownership: +The edit and delete buttons for Notes appear based on your Notes permissions and Note ownership: -* **Edit own** - You can edit notes you created, regardless of which User owns the Contact. -* **Edit others** - You can edit notes created by other Users. -* **Delete own** - You can delete notes you created. -* **Delete others** - You can delete notes created by other Users. +* **Edit own** - You can edit Notes you created, regardless of which User owns the Contact. +* **Edit others** - You can edit Notes created by other Users. +* **Delete own** - You can delete Notes you created. +* **Delete others** - You can delete Notes created by other Users. -For example, if you have ``Edit own`` notes permission, you can edit your own notes on any Contact you can view - even Contacts owned by other Users. However, you can't edit notes that other Users created unless you also have ``Edit others`` permission. +For example, if you have ``Edit own`` Notes permission, you can edit your own Notes on any Contact you can view - even Contacts owned by other Users. However, you can't edit Notes that other Users created unless you also have ``Edit others`` permission. -See :doc:`/users_roles/managing_roles` for details on configuring notes permissions. +See :doc:`/users_roles/managing_roles` for details on configuring Notes permissions. Social ====== diff --git a/docs/users_roles/managing_roles.rst b/docs/users_roles/managing_roles.rst index 2dbdedf55..1ebb1bf9f 100644 --- a/docs/users_roles/managing_roles.rst +++ b/docs/users_roles/managing_roles.rst @@ -147,7 +147,7 @@ The Contact Permissions section includes several permission categories: * **Contacts - User has access to** - determines which Contact records a User can view, edit, create, and delete. -* **Notes - User has access to** - determines which notes attached to Contacts a User can access. This is separate from Contact permissions, giving you fine-grained control over note management. For example, a User might view all Contacts but only edit their own notes on those Contacts. +* **Notes - User has access to** - determines which Notes attached to Contacts a User can access. This is separate from Contact permissions, giving you fine-grained control over note management. For example, a User might view all Contacts but only edit their own Notes on those Contacts. * **Segments - User has access to** - determines which Segments a User can access. @@ -157,7 +157,7 @@ The Contact Permissions section includes several permission categories: .. note:: - Notes permissions determine which notes a User can view, edit, and delete based on note ownership - not Contact ownership. A User with ``Edit own`` notes permission can edit notes they created, even on Contacts owned by other Users. See :ref:`notes` for more details. + Notes permissions determine which Notes a User can view, edit, and delete based on Note ownership - not Contact ownership. A User with ``Edit own`` Notes permission can edit Notes they created, even on Contacts owned by other Users. See :ref:`Notes` for more details. .. note:: From 4924093c0d195be844cfe1c5b6922e6c8a8dd6c8 Mon Sep 17 00:00:00 2001 From: "promptless[bot]" Date: Tue, 26 May 2026 14:29:10 +0000 Subject: [PATCH 4/5] Address reviewer feedback on Notes permissions docs - Change reference from "Notes permissions" to generic "permissions" in manage_contacts.rst since there is no specific Notes permissions section in managing_roles.rst - Combine back-to-back note admonitions into a single note with an unordered list using bold permission types for better readability --- docs/contacts/manage_contacts.rst | 2 +- docs/users_roles/managing_roles.rst | 8 +++----- 2 files changed, 4 insertions(+), 6 deletions(-) diff --git a/docs/contacts/manage_contacts.rst b/docs/contacts/manage_contacts.rst index 7cdb4befb..47fdb0f7a 100644 --- a/docs/contacts/manage_contacts.rst +++ b/docs/contacts/manage_contacts.rst @@ -310,7 +310,7 @@ The edit and delete buttons for Notes appear based on your Notes permissions and For example, if you have ``Edit own`` Notes permission, you can edit your own Notes on any Contact you can view - even Contacts owned by other Users. However, you can't edit Notes that other Users created unless you also have ``Edit others`` permission. -See :doc:`/users_roles/managing_roles` for details on configuring Notes permissions. +See :doc:`/users_roles/managing_roles` for details on configuring permissions. Social ====== diff --git a/docs/users_roles/managing_roles.rst b/docs/users_roles/managing_roles.rst index 1ebb1bf9f..8a3d96965 100644 --- a/docs/users_roles/managing_roles.rst +++ b/docs/users_roles/managing_roles.rst @@ -157,12 +157,10 @@ The Contact Permissions section includes several permission categories: .. note:: - Notes permissions determine which Notes a User can view, edit, and delete based on Note ownership - not Contact ownership. A User with ``Edit own`` Notes permission can edit Notes they created, even on Contacts owned by other Users. See :ref:`Notes` for more details. + * **Notes permissions** determine which Notes a User can view, edit, and delete based on Note ownership - not Contact ownership. A User with ``Edit own`` Notes permission can edit Notes they created, even on Contacts owned by other Users. See :ref:`Notes` for more details. -.. note:: - - User permissions restrict their view of dashboard widgets, resulting in them only seeing widgets for items or feature bundles they have permission to see. + * **User permissions** restrict their view of dashboard widgets, resulting in them only seeing widgets for items or feature bundles they have permission to see. - For example, if a User's Role doesn't have Asset permissions, they can't create or view widgets on the dashboard for Asset data. + For example, if a User's Role doesn't have Asset permissions, they can't create or view widgets on the dashboard for Asset data. You can also create :xref:`Roles using the API`. \ No newline at end of file From 2e2a0c40a666bc8e6e3d8d2a2734e1b8189b35b2 Mon Sep 17 00:00:00 2001 From: "promptless[bot]" Date: Fri, 17 Jul 2026 12:33:33 +0000 Subject: [PATCH 5/5] Document Notes permission upgrade backfill for existing Roles --- docs/users_roles/managing_roles.rst | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/users_roles/managing_roles.rst b/docs/users_roles/managing_roles.rst index 8a3d96965..f3cd06864 100644 --- a/docs/users_roles/managing_roles.rst +++ b/docs/users_roles/managing_roles.rst @@ -163,4 +163,8 @@ The Contact Permissions section includes several permission categories: For example, if a User's Role doesn't have Asset permissions, they can't create or view widgets on the dashboard for Asset data. +.. note:: + + When you upgrade from an earlier version, Mautic grants each non-administrator Role the same Notes access it already had for Contacts. Existing Roles keep working as before, so anyone who could view or edit a Contact's Notes still can. From there, you can refine each Role's Notes permissions independently of its Contact permissions. + You can also create :xref:`Roles using the API`. \ No newline at end of file