[MOV] general: renames "odoo_basics" into "users" + split content

This commit is part of a larger work to improve the documentation's
structure. The toctree structure used to add levels to create categories
and make the structure visually more understandable.
With the new version of the documentation, plenty of these categories
are now redundant.

Since other docs were moved away from the section "basics" with previous
commits, this category is renamed "users settings"
This commit:
- renames "basics" into "users settings"
- moves the content from "odoo_basics/users" to "users"
  - it moves the content about "access rights" to a child doc

task-2535899

content/applications/general.rst

@@ -6,7 +6,7 @@ General
 
 .. toctree::
 
-    general/odoo_basics
+    general/users
     general/export_import_data
     general/multi_companies
     general/auth

content/applications/general/multi_companies.rst

@@ -50,7 +50,7 @@ company only. To do so, on their forms, choose between:
 Employees' access
 =================
 
-Once companies are created, manage your employees' :doc:`Access Rights <odoo_basics/users>`
+Once companies are created, manage your employees' :doc:`Access Rights <users/access_rights>`
 for *Multi Companies*.
 
 .. image:: multi_companies/access_rights_multi_companies.png

content/applications/general/odoo_basics.rst

@@ -1,9 +0,0 @@
-======
-Basics
-======
-
-.. toctree::
-   :titlesonly:
-
-   odoo_basics/choose_language
-   odoo_basics/users

content/applications/general/users.rst

@@ -1,12 +1,24 @@
-=======================
-Users and Access Rights
-=======================
+:show-content:
+
+==============
+Users settings
+==============
+
+.. toctree::
+   :titlesonly:
+
+   users/language
+   users/access_rights
 
 Odoo defines a *user* as someone who has access to a database to perform daily tasks. You can add as
 many users as you need and, in order to restrict the type of information each user can access, rules
 can be applied. Users and access rights can be added and changed at any point.
 
-.. _general/odoo_basics/add_individual_user:
+.. seealso::
+   - :doc:`users/language`
+   - :doc:`users/access_rights`
+
+.. _users/add-individual:
 
 Add individual users
 ====================
@@ -19,11 +31,11 @@ Go to :menuselection:`Settings --> Manage Users` and click on *Create*.
    :alt: View of the settings page emphasizing the manage users field in Odoo
 
 | Fill in the form with the needed information. Under the tab
-  :ref:`Access Rights <general/odoo_basics/users/access_rights>` choose the group within
-  each application the user can have access to.
+  :doc:`Access Rights <users/access_rights>` choose the group within each application the user can
+  have access to.
 | The list of applications shown is based on the applications installed on the database.
 
-.. image:: media/new_user.png
+.. image:: users/new_user.png
    :align: center
    :alt: View of a user’s form emphasizing the access rights tab in Odoo
 
@@ -115,74 +127,7 @@ Enter a new password and confirm by clicking on *Change Password*.
 Click on *Change Password* one more time. You are then redirected to an Odoo login page where you
 can reaccess your database using your new password.
 
-.. _general/odoo_basics/users/access_rights:
-
-Access Rights in detail
-=======================
-
-Activate the :ref:`developer mode  <developer-mode>`, then go to :menuselection:`Settings --> Users
-& Companies --> Groups`.
-
-Groups
-------
-
-| When choosing the groups the user can have access under
-  :ref:`Access Rights <general/odoo_basics/add_individual_user>`, details of the rules and
-  inheritances of that group are not shown, so this is when the menu *Groups* comes along. *Groups*
-  are created to define rules to models within an application.
-| Under *Users*, have a list of the current ones. The ones with administrative rights are shown
-  in black.
-
-.. image:: users/groups-users.png
-   :align: center
-   :alt: View of a group’s form emphasizing the tab users in Odoo
-
-*Inherited* means that users added to this application group are automatically added to the
-following ones. In the example below, users who have access to the group *Administrator* of *Sales*
-also have access to *Website/Restricted Editor* and *Sales/User: All Documents*.
-
-.. image:: users/groups-inherited.png
-   :align: center
-   :height: 330
-   :alt: View of a group’s form emphasizing the tab inherited in Odoo
-
-.. important::
-   Remember to always test the settings being changed in order to ensure that they are being applied
-   to the needed and right users.
-
-The *Menus* tab is where you define which menus (models) the user can have access to.
-
-.. image:: users/groups-menus.png
-   :align: center
-   :height: 330
-   :alt: View of a group’s form emphasizing the tab menus in Odoo
-
-*Access Rights* rules are the first level of rights. The field is composed of the object name, which
-is the technical name given to a model. For each model, enable the following options as appropriate:
-
-- *Read*: the values of that object can be only seen by the user.
-- *Write*: the values of that object can be edited by the user.
-- *Create*: values for that object can be created by the user.
-- *Delete*: the values of that object can be deleted by the user.
-
-.. image:: users/groups-access-rights.png
-   :align: center
-   :alt: View of a group’s form emphasizing the tab access rights in Odoo
-
-| As a second layer of editing and visibility rules, *Record Rules* can be formed. They overwrite,
-  or refine, the *Access Rights*.
-| A record rule is written using a *Domain*. Domains are conditions used to filter or searching
-  data. Therefore, a domain expression is a list of conditions. For each rule, choose among the
-  following options: *Read*, *Write*, *Create* and *Delete* values.
-
-.. image:: users/groups-record-rules.png
-   :align: center
-   :alt: View of a group’s form emphasizing the tab record rules in Odoo
-
-.. important::
-   Making changes in access rights can have a big impact on the database. For this reason, we
-   recommend you to contact your Odoo Business Analyst or our Support Team, unless you have
-   knowledge about Domains in Odoo.
+.. _users/multi-companies:
 
 Multi Companies
 ===============
@@ -201,5 +146,5 @@ the user can have access.
    :alt: View of a user’s form emphasizing the multi companies field in Odoo
 
 .. seealso::
-   - :doc:`../multi_companies`
-   - :doc:`../../general`
+   - :doc:`multi_companies`
+   - :doc:`../general`

content/applications/general/users/access_rights.rst

@@ -0,0 +1,67 @@
+=============
+Access Rights
+=============
+
+Activate the :ref:`developer mode <developer-mode>`, then go to :menuselection:`Settings --> Users &
+Companies --> Groups`.
+
+Groups
+======
+
+| When choosing the groups the user can have access under
+  :ref:`Access Rights <users/add-individual>`, details of the rules and inheritances of that group
+  are not shown, so this is when the menu *Groups* comes along. *Groups* are created to define rules
+  to models within an application.
+| Under *Users*, have a list of the current ones. The ones with administrative rights are shown
+  in black.
+
+.. image:: access_rights/groups-users.png
+   :align: center
+   :alt: View of a group’s form emphasizing the tab users in Odoo
+
+*Inherited* means that users added to this application group are automatically added to the
+following ones. In the example below, users who have access to the group *Administrator* of *Sales*
+also have access to *Website/Restricted Editor* and *Sales/User: All Documents*.
+
+.. image:: access_rights/groups-inherited.png
+   :align: center
+   :height: 330
+   :alt: View of a group’s form emphasizing the tab inherited in Odoo
+
+.. important::
+   Remember to always test the settings being changed in order to ensure that they are being applied
+   to the needed and right users.
+
+The *Menus* tab is where you define which menus (models) the user can have access to.
+
+.. image:: access_rights/groups-menus.png
+   :align: center
+   :height: 330
+   :alt: View of a group’s form emphasizing the tab menus in Odoo
+
+*Access Rights* rules are the first level of rights. The field is composed of the object name, which
+is the technical name given to a model. For each model, enable the following options as appropriate:
+
+- *Read*: the values of that object can be only seen by the user.
+- *Write*: the values of that object can be edited by the user.
+- *Create*: values for that object can be created by the user.
+- *Delete*: the values of that object can be deleted by the user.
+
+.. image:: access_rights/groups-access-rights.png
+   :align: center
+   :alt: View of a group’s form emphasizing the tab access rights in Odoo
+
+| As a second layer of editing and visibility rules, *Record Rules* can be formed. They overwrite,
+  or refine, the *Access Rights*.
+| A record rule is written using a *Domain*. Domains are conditions used to filter or searching
+  data. Therefore, a domain expression is a list of conditions. For each rule, choose among the
+  following options: *Read*, *Write*, *Create* and *Delete* values.
+
+.. image:: access_rights/groups-record-rules.png
+   :align: center
+   :alt: View of a group’s form emphasizing the tab record rules in Odoo
+
+.. important::
+   Making changes in access rights can have a big impact on the database. For this reason, we
+   recommend you to contact your Odoo Business Analyst or our Support Team, unless you have
+   knowledge about Domains in Odoo.

content/applications/general/users/language.rst

@@ -1,6 +1,6 @@
-================================
-Manage Odoo in your own language
-================================
+===============
+Change language
+===============
 
 Odoo provides you with the option to manage Odoo in different languages,
 and each user can use Odoo in his own language .
@@ -15,7 +15,7 @@ From the general dashboard click on the **Settings** app; on the top
 left of the page select :menuselection:`Translations --> Load a Translation`,
 select a language to install and click on **LOAD.**
 
-.. image:: media/choose_language01.png
+.. image:: language/choose_language01.png
     :align: center
 
 .. note::
@@ -30,13 +30,13 @@ You can change the language to the installed language by going to the
 drop-down menu at the top right side of the screen, choose
 **Preferences**.
 
-.. image:: media/choose_language02.png
+.. image:: language/choose_language02.png
     :align: center
 
 Then change the Language setting to your installed language and click
 **SAVE.**
 
-.. image:: media/choose_language03.png
+.. image:: language/choose_language03.png
     :align: center
 
 Open a new menu to view the changes.
@@ -54,7 +54,7 @@ user and click on **Edit** in the top left corner. Under Preferences you
 can change the Language to any previously installed language and click
 **SAVE.**
 
-.. image:: media/choose_language04.png
+.. image:: language/choose_language04.png
     :align: center
 
 .. seealso::

content/applications/productivity/studio/how_to/reports.rst

@@ -34,10 +34,10 @@ them. Fields with related objects have their directives shown on *Field Expressi
 | Under **Visible if**, define the rule(s) to set visibility conditions to fields.
 | Example: if choosing to display a product image, you could set a visibility rule to only display
   the ones that are *set* in the product form, avoiding having a plain icon when they are not set.
-| **Visible for** is used to set which :doc:`groups </applications/general/odoo_basics/users>`
-  can have access to specific elements in the report. **Limit visibility to groups**, under
-  *Report*, sets the visibility of the report to specifics groups, meaning that users belonging to
-  other groups do not see the same final document.
+| **Visible for** is used to set which :doc:`groups </applications/general/users>` can have access
+  to specific elements in the report. **Limit visibility to groups**, under *Report*, sets the
+  visibility of the report to specifics groups, meaning that users belonging to other groups do not
+  see the same final document.
 
 .. image:: media/reports/limit_visibility.png
    :align: center

content/applications/services/helpdesk/overview/getting_started.rst

@@ -61,4 +61,4 @@ or use the stage.
    :alt: View of a team’s kanban view in Odoo Helpdesk
 
 .. seealso::
-   - :doc:`/applications/general/odoo_basics/users`
+   - :doc:`/applications/general/users`

redirects.txt

@@ -208,5 +208,7 @@ content/applications/general/odoo_basics/export-data.rst applications/general/ex
 applications/settings/users_and_features.rst applications/general.rst                                     # settings/users_and_features -> general
 applications/general/mobile.rst applications/general.rst                                                  # general/mobile -> general
 applications/general/developer_mode/activate.rst applications/general.rst                                 # developer_mode/activate -> general
+applications/general/odoo_basics/users.rst applications/general/users.rst                                 # odoo_basics/users -> users
+applications/general/odoo_basics/choose_language.rst  applications/general/users/language.rst             # odoo_basics/choose_language -> users/language
 
 applications/finance/sign/overview/signature_validity.rst applications/finance/sign.rst        #sign/overview/signature_validity -> sign/*