Fixes #386 - Edited object/attribute permissions

locale/admin-docs.pot

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Zammad Admin Documentation pre-release\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2023-11-02 14:55+0100\n"
+"POT-Creation-Date: 2023-11-03 10:17+0100\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <[email protected]>\n"
@@ -439,7 +439,7 @@ msgstr ""
 #: ../channels/email/accounts/account-setup.rst:262
 #: ../channels/email/accounts/email-notification.rst:30
 #: ../settings/security/third-party/microsoft.rst:72
-#: ../system/objects/permissions.rst:53
+#: ../system/objects/permissions.rst:54
 #: ../system/sessions.rst:23
 msgid "User"
 msgstr ""
@@ -1736,7 +1736,7 @@ msgstr ""
 #: ../channels/email/filters.rst:43
 #: ../channels/email/filters.rst:43
 #: ../system/integrations/checkmk/admin-panel-reference.rst:15
-#: ../system/objects/permissions.rst:55
+#: ../system/objects/permissions.rst:56
 msgid "Group"
 msgstr ""
 
@@ -8645,7 +8645,7 @@ msgstr ""
 
 #: ../manage/time-accounting.rst:203
 #: ../settings/branding.rst:13
-#: ../system/objects/permissions.rst:54
+#: ../system/objects/permissions.rst:55
 msgid "Organization"
 msgstr ""
 
@@ -17786,27 +17786,27 @@ msgid "This field allows using :ref:`URL fields (Link Templates) <link-templates
 msgstr ""
 
 #: ../system/objects/permissions.rst:2
-msgid "Object permissions"
+msgid "Attribute permissions"
 msgstr ""
 
 #: ../system/objects/permissions.rst:7
-msgid "Some of the possible permission and screen options for objects."
+msgid "Some of the possible permissions and screen options for object attributes."
 msgstr ""
 
 #: ../system/objects/permissions.rst:9
-msgid "Whenever needed you can restrict access to objects based on the :ref:`user permission <permission-guide>` (``admin``, ``ticket.agent`` & ``ticket.customer``)."
+msgid "Whenever needed you can restrict access to attributes based on the :ref:`user permission <permission-guide>` (``admin``, ``ticket.agent`` & ``ticket.customer``)."
 msgstr ""
 
 #: ../system/objects/permissions.rst:13
-msgid "**🤓 Below is not set in stone 🤓**"
+msgid "**🤓 This is not the only possibility to restrict access**"
 msgstr ""
 
 #: ../system/objects/permissions.rst:15
-msgid "You can always adjust below settings with :doc:`/system/core-workflows`. This also allows role based restriction. 👀"
+msgid "You can always adjust below settings with :doc:`/system/core-workflows`. This also allows role based restriction."
 msgstr ""
 
 #: ../system/objects/permissions.rst:20
-msgid "In some situations, Zammad internally overrules below screen, requirement and permission settings. This is because at some points you can't set fields which would mean we couldn't create the ticket."
+msgid "In some situations, Zammad internally overrules your chosen settings for screen, requirement and permission. This affects situations where a field can't be set which would be required for the ticket creation."
 msgstr ""
 
 #: ../system/objects/permissions.rst:24
@@ -17846,67 +17846,67 @@ msgid "About screens"
 msgstr ""
 
 #: ../system/objects/permissions.rst:37
-msgid "Zammad cares about the screen you're going to use the object in."
+msgid "Zammad differentiates between several screens where object attributes can be used."
 msgstr ""
 
-#: ../system/objects/permissions.rst:40
+#: ../system/objects/permissions.rst:41
 msgid "create"
 msgstr ""
 
-#: ../system/objects/permissions.rst:40
+#: ../system/objects/permissions.rst:41
 msgid "Every time you use a creation dialogue for not yet existing data."
 msgstr ""
 
-#: ../system/objects/permissions.rst:44
+#: ../system/objects/permissions.rst:45
 msgid "edit"
 msgstr ""
 
-#: ../system/objects/permissions.rst:43
+#: ../system/objects/permissions.rst:44
 msgid "Every time you're editing existing data - viewing existing tickets counts as edit screen."
 msgstr ""
 
-#: ../system/objects/permissions.rst:55
+#: ../system/objects/permissions.rst:56
 msgid "view"
 msgstr ""
 
-#: ../system/objects/permissions.rst:47
+#: ../system/objects/permissions.rst:48
 msgid "Affects view screens of existing data like e.g. user profiles."
 msgstr ""
 
-#: ../system/objects/permissions.rst:51
+#: ../system/objects/permissions.rst:52
 msgid "This setting is available for the following object contexts:"
 msgstr ""
 
-#: ../system/objects/permissions.rst:58
+#: ../system/objects/permissions.rst:59
 msgid "invite_customer & invite_agent"
 msgstr ""
 
-#: ../system/objects/permissions.rst:58
+#: ../system/objects/permissions.rst:59
 msgid "Shown when using the invitation dialogue from \"First Steps\" in the dashboard."
 msgstr ""
 
-#: ../system/objects/permissions.rst:61
+#: ../system/objects/permissions.rst:62
 msgid "About screen options"
 msgstr ""
 
-#: ../system/objects/permissions.rst:63
+#: ../system/objects/permissions.rst:64
 msgid "Now that we know the different possible situations, let's talk about available options."
 msgstr ""
 
-#: ../system/objects/permissions.rst:67
+#: ../system/objects/permissions.rst:68
 msgid "shown"
 msgstr ""
 
-#: ../system/objects/permissions.rst:67
-msgid "Show or hide a field."
+#: ../system/objects/permissions.rst:68
+msgid "Show (checked) or hide (unchecked) a field."
 msgstr ""
 
-#: ../system/objects/permissions.rst:70
+#: ../system/objects/permissions.rst:71
 msgid "required"
 msgstr ""
 
-#: ../system/objects/permissions.rst:70
-msgid "Set a field to mandatory. Forces users (via UI and API) to populate the field."
+#: ../system/objects/permissions.rst:71
+msgid "Set a field to mandatory (checked). Forces users (via UI and API) to populate the field."
 msgstr ""
 
 #: ../system/objects/types.rst:2

system/objects/permissions.rst

@@ -1,25 +1,25 @@
-Object permissions
-******************
+Attribute permissions
+*********************
 
 .. figure:: /images/system/objects/permission-and-screen-overview.png
    :align: center
 
-   Some of the possible permission and screen options for objects.
+   Some of the possible permissions and screen options for object attributes.
 
-Whenever needed you can restrict access to objects based on the 
+Whenever needed you can restrict access to attributes based on the
 :ref:`user permission <permission-guide>`
 (``admin``, ``ticket.agent`` & ``ticket.customer``).
 
-.. tip:: **🤓 Below is not set in stone 🤓**
+.. tip:: **🤓 This is not the only possibility to restrict access**
 
    You can always adjust below settings with :doc:`/system/core-workflows`.
-   This also allows role based restriction. 👀
+   This also allows role based restriction.
 
 .. note::
-   
-   In some situations, Zammad internally overrules below screen, requirement and
-   permission settings. This is because at some points you can't set fields
-   which would mean we couldn't create the ticket.
+
+   In some situations, Zammad internally overrules your chosen settings for
+   screen, requirement and permission. This affects situations where a field
+   can't be set which would be required for the ticket creation.
 
    This currently affects:
 
@@ -34,7 +34,8 @@ Whenever needed you can restrict access to objects based on the
 About screens
 -------------
 
-Zammad cares about the screen you're going to use the object in.
+Zammad differentiates between several screens where object attributes can be
+used.
 
 create
    Every time you use a creation dialogue for not yet existing data.
@@ -60,12 +61,12 @@ invite_customer & invite_agent
 About screen options
 --------------------
 
-Now that we know the different possible situations,
-let's talk about available options.
+Now that we know the different possible situations, let's talk about available
+options.
 
 shown
-   Show or hide a field.
+   Show (checked) or hide (unchecked) a field.
 
 required
-   Set a field to mandatory. Forces users (via UI and API)
+   Set a field to mandatory (checked). Forces users (via UI and API)
    to populate the field.