[ADD] General: User portal rework and addition

content/applications/general/users.rst

@@ -58,7 +58,7 @@ User` or :guilabel:`Portal User`.
 Odoo databases have three types of users: :guilabel:`Internal User`, :guilabel:`Portal`, and
 :guilabel:`Public`. Users are considered *internal database* users. Portal users are *external
 users*, who only have access to the database portal to view records. Public users are those visiting
-websites, via the website's frontend. See the documentation on :doc:`users/portal`.
+websites, via the website's frontend. See the documentation on :doc:`users/user_portals`.
 
 The :guilabel:`Portal` user option does **not** allow the administrator to choose access rights.
 These users have specific access rights pre-set (such as, record rules and restricted menus), and
@@ -278,7 +278,7 @@ company.
    users/language
    users/2fa
    users/access_rights
-   users/portal
+   users/user_portals
    users/facebook
    users/google
    users/azure

content/applications/general/users/user_portals.rst

@@ -0,0 +1,29 @@
+:show-content:
+
+============
+User portals
+============
+
+.. _user_portals/main:
+
+The user portal is a module available by default in Odoo. Users, both customers and vendors, can be
+granted :doc:`access to the portal </applications/general/users/access_rights>` by businesses in
+order to view certain documents or information within an Odoo database. For example, some common use
+cases for providing portal access include allowing customers and vendors to:
+
+- Follow, view, and pay orders
+- Follow, download, or pay invoices, including partial payments and down payments
+- Manage payment methods
+- Manage subscriptions
+- Add, remove, or modify their addresses
+- Configure connection parameters between Odoo and 3rd-party services
+
+.. note::
+   Portal users only have read/view access, and will **not** be able to edit any documents in the
+   database.
+
+.. toctree::
+   :titlesonly:
+
+   user_portals/portal_access
+   user_portals/updating_portal_info

content/applications/general/users/user_portals/portal_access.rst

@@ -0,0 +1,52 @@
+======================
+Granting portal access
+======================
+
+In order for the customers and vendors of a business to begin using the user portal, they must first
+be granted access by the business. The process to do this begins in the **Contacts** application.
+
+Adding portal access to a contact
+=================================
+
+From the main Odoo dashboard, open the :guilabel:`Contacts` application. If the contact to be
+granted access is not yet in the database, create an entry for them by clicking on the
+:guilabel:`Create` button and entering their details. Otherwise, choose an existing contact, then
+click on the :icon:`fa-gear` :guilabel:`(Actions)` drop-down menu located at the top-center of the
+interface, and select :guilabel:`Grant portal access`.
+
+.. image:: portal_access/grant-portal-access.png
+   :alt: Use the Contacts application to give portal access to users.
+
+This brings up the :guilabel:`Portal Access Management` window, which has three fields:
+
+- :guilabel:`Contact`: the recorded name of the contact in the Odoo database
+- :guilabel:`Email`: the contact's email address used to log into the portal
+- :guilabel:`Latest Authentication`: the last time the user accessed the portal
+
+.. image:: portal_access/portal-access-management.png
+   :alt: Grant access in the Portal Access Management window.
+
+To grant portal access, first enter the email address the contact will use to log into the portal.
+This may have been automatically entered by the system if an existing contact is being granted
+access. Then click the :guilabel:`Grant Access` button to finish.
+
+Granting accesss to multiple users at once
+------------------------------------------
+
+To grant portal access to multiple users from a single company at once, navigate to the contact
+listing for that company, then click :menuselection:`Action --> Grant portal access` to view a list
+of the company's related contacts. Click :guilabel:`Grant Access` for each contact that needs portal
+access. An email is sent to the specified email address, indicating that the contact is now a portal
+user for that Odoo database.
+
+.. image:: portal_access/multiple-user-access.png
+   :alt: Grant access to multiple users at once.
+
+Revoking portal access
+----------------------
+
+Portal access can be revoked from a contact at any time by navigating to a contact, clicking
+:menuselection:`Action --> Grant portal access`, and then clicking :guilabel:`Revoke Access`.
+
+.. image:: portal_access/revoke-user-access.png
+   :alt: Revoke access from a user.

content/applications/general/users/user_portals/updating_portal_info.rst

@@ -0,0 +1,131 @@
+====================
+Updating portal info
+====================
+
+There may be times when a user would like to make changes to their contact, security, or payment
+information connected to their portal account. Portal users can update most information by logging
+into their account and making the changes themselves, but some updates may require a database user
+with administrator access rights.
+
+Updating user information begins with logging into the user portal. Once a user has logged in and is
+on the portal dashboard, they can begin making changes to their information.
+
+User-driven updates
+===================
+
+.. _user_portal_user_info:
+
+.. note::
+   Passwords for portal users and Odoo.com users remain separate, even if the same email address is
+   used.
+
+Changing contact info
+---------------------
+
+From the portal dashboard, click the :guilabel:`Edit information` button under the user contact
+information. This brings up a new page where contact information can be updated.
+
+On this screen, users can update their:
+
+- Contact name
+- Email address and phone number
+- Company name and VAT (if applicable)
+- Mailing address
+- Invoice delivery preference
+- Electronic format for documents (This is generally only relevant for portal users in the European
+  Union.)
+
+Once users have updated their information, they can click :guilabel:`Save Address` to save any
+changes they've made or :guilabel:`Discard` to return to the portal dashboard. By default, the only
+fields that need to be filled out to save users' information are their names, emails, phone numbers,
+and addresses.
+
+.. important::
+   Once the system has generated any documents for a user's account, their country **cannot** be
+   updated. If users need to update their country at that point, they must reach out to a database
+   user with administrator access rights.
+
+.. _users-portal-payment-methods:
+
+Change payment info
+-------------------
+
+From the portal dashboard, click the :guilabel:`Payment methods` button. This brings up a new page
+that shows any saved payment methods.
+
+* To add a new payment option, choose from the available payment methods, enter the new payment
+  information, and click :guilabel:`Save` to save the details.
+* To erase a payment option, click the :icon:`fa-trash` :guilabel:`(Trash)` icon, then click the
+  :guilabel:`Confirm Deletion` button.
+
+.. important::
+   Users that need to update payment information must delete any existing information and enter
+   their new or updated info. Payment information **cannot** be edited and must be re-entered.
+
+
+Changing passwords and managing security
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+From the portal dashboard, click the :guilabel:`Connection & Security` button. This brings up a new
+page with five sections:
+
+- Change Password. Here the user can enter their current password and a new password they wish to
+  change to. The new password can be saved by clicking :guilabel:`Change Password`.
+- Two-factor authentication. An :icon:`fa-info-circle` :guilabel:`info tooltip` explains how
+  two-factor authentication (2FA) works and the user's currrent 2FA status is shown. If 2FA is not
+  enabled, an :guilabel:`Enable two-factor authentication` appears. If it is enabled, a link reading
+  :guilabel:`Disable two-factor authentication` appears instead.
+- Passkeys. Click :guilabel:`Add Passkey` to create a passkey that simplifies the login process. Any
+  previously created passkeys are shown here, alongside information on when they were created and
+  when they were last used. They can be renamed by clicking their :icon:`fa-pencil` :guilabel:`edit`
+  button or deleted by clicking their :icon:`fa-trash` :guilabel:`Delete` button.
+- Revoke All Sessions. Clicking the :guilabel:`Log out from all devices` button brings up a pop-up
+  prompting the user to enter their password. Once they do so and click
+  :guilabel:`Confirm Password`, the system logs them out of all sessions except for the current one.
+- Delete Account. Clicking the :guilabel:`Delete Account` button brings up a pop-up to completely
+  and irrevocably delete the user's account. Users must enter their password and their login name to
+  complete the process. They can also choose to have their email address and phone number added to
+  an internal block list to prevent any future communication.
+
+Database administrator-driven updates
+=====================================
+
+Accessing users' information as an administrator
+------------------------------------------------
+
+First, navigate to :menuselection:`Settings app --> Users` and click :icon:`oi-arrow-right`
+:guilabel:`Manage Users` Then, click the drop-down arrow in the search bar and add :guilabel:`Portal
+Users` as a filter. After making this selection, search for and open the portal user that needs to
+be edited.
+
+Update email address
+~~~~~~~~~~~~~~~~~~~~
+
+The :icon:`fa-envelope` :guilabel:`Email Address` field shows the email address the user uses to log
+into the Odoo database. A database user with administrator access rights can make any necessary
+changes by clicking into the field, updating the user's email address, and clicking the
+:icon:`fa-cloud-upload` :guilabel:`Save` button.
+
+.. note::
+   Users **cannot** change their own login usernames. Changing the :icon:`fa-key`
+   :guilabel:`(Login)` only changes the *username* on the user's portal login. Users' email
+   addresses can be changed in the :guilabel:`Manage Users` module, the    **Contacts** app, or by
+   the users themselves in the portal.
+
+Update passwords
+~~~~~~~~~~~~~~~~
+
+Users' security settings can be adjusted under the :guilabel:`Security` tab on their Contact form.
+Under the :guilabel:`Security` tab, there are options to:
+
+- :guilabel:`Change password` Click the :guilabel:`Change password` button to bring up a form that
+  shows what logins the user has access to and enter a new password. Click :guilabel:`Change
+  Password` to save the password or click :guilabel:`Cancel` to return to the previous screen.
+- :guilabel:`Send Password Reset`. Click the :guilabel:`Send Password Reset` button to bring up a
+  pop-up notification that a password reset link has been sent by email.
+- :guilabel:`Invite to use 2FA`. Click the :guilabel:`Invite to use 2FA` button to bring up a pop-up
+  notification that an invitation to use two-factor authentication was sent.
+
+.. seealso::
+   - :doc:`Access rights </applications/general/users/access_rights>`
+   - :doc:`Portal access documentation <portal_access>`