-
Notifications
You must be signed in to change notification settings - Fork 10.8k
[ADD] General: User portal rework and addition #15777
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: 19.0
Are you sure you want to change the base?
Conversation
|
Hi @theRealThagomizer, this PR looks to be a real lift! The portal.rst page has been replaced by user_portal.rst, correct? could you create a redirect link for that? |
Done! The next commit has an updated redirect file. |
larm-odoo
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My goodness- what a BEAST of a doc as usual @theRealThagomizer! I had a lot of edits and suggestions - some are optional/stylistic, others I think would help with structure and detail. Take what you will, ignore the rest, and tag me when it's ready for another look =) Also, I apologize- I tend to make comments before reading thorugh a whole odc, so you'll see my htought process as I went along =D
| The user portal is a module available by default in Odoo. Users, both customers and vendors, can be | ||
| granted access to the portal 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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"granted access" could be a doc link to the granting access doc (just a suggestion!)
| .. toctree:: | ||
| :titlesonly: | ||
|
|
||
| user_portals/portal_access | ||
| user_portals/updating_portal_info |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| From the main Odoo dashboard, select 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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| From the main Odoo dashboard, select 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 | |
| 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 |
Just a preference- disregard if you like!
|
|
||
| From the main Odoo dashboard, select 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, entering their details, and then clicking :guilabel:`Save`. Otherwise, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| :guilabel:`Create` button, entering their details, and then clicking :guilabel:`Save`. Otherwise, | |
| :guilabel:`New` button, and entering their details. Otherwise, |
There's no more Save button, and the form auto-saves so we typically skip 'clicking save'unless you need to, like on the Settings page.
| choose an existing contact, and then click on the :guilabel:`Action` drop-down menu located at the | ||
| top-center of the interface. | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| choose an existing contact, and then click on the :guilabel:`Action` drop-down menu located at the | |
| top-center of the interface. | |
| choose an existing contact, and then click the :icon:`fa-gear` :guilabel:`(Actions)` drop-down menu located at the | |
| top-center of the interface, and select :guilabel:`Grant portal access`. |
Since we see the gear but the text is not visible, the text should be in parenthesis.
Also, I felt the instructiosn shouldn't be broken up between accessing th emenu and making the selection, sinc ht eimage shows the seleciotn you shoudl make.
| .. note:: | ||
| Changing the :guilabel:`Email Address` (or login) only changes the *username* on the user's | ||
| portal login. | ||
|
|
||
| In order to change the contact email, this change needs to take place on the contact template in | ||
| the **Contacts** app. Alternatively, the user can change their email directly from the portal, | ||
| but their login **cannot** be changed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a little ocnfused- do they not use an email as the "username"? Am i correct to infer that the email on this page, is what they type in the portal login? I understand that the Contact email is separate form the portal user- but would someone just write in a name/handle in the email field? Like "awesomeportaluser" or does it need to be an actual email? I feel like 99.9% of peopple would use an email.
| Users` as a filter. After making this selection, search for and open the portal user that needs to | ||
| be edited. | ||
|
|
||
| Changing emails |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| Changing emails | |
| Update email address |
| the **Contacts** app. Alternatively, the user can change their email directly from the portal, | ||
| but their login **cannot** be changed. | ||
|
|
||
| Changing passwords |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| Changing passwords | |
| Update passwords | |
| ~~~~~~~~~~~~~~~ |
I think this should be nested in the 'admin changes' like the emails, yes?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| - Change user passwords. Clicking 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. | ||
| - Send users a password reset invitation. Clicking the :guilabel:`Send Password Reset` button brings | ||
| up a pop-up notification that a password reset link has been sent by email. | ||
| - Send users a two-factor authentication invite. Clicking the :guilabel:`Invite to use 2FA` button |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| - Change user passwords. Clicking 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. | |
| - Send users a password reset invitation. Clicking the :guilabel:`Send Password Reset` button brings | |
| up a pop-up notification that a password reset link has been sent by email. | |
| - Send users a two-factor authentication invite. Clicking the :guilabel:`Invite to use 2FA` button | |
| - :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. | |
| - Send users a password reset invitation. Clicking the :guilabel:`Send Password Reset` button brings | |
| up a pop-up notification that a password reset link has been sent by email. | |
| - Send users a two-factor authentication invite. Clicking the :guilabel:`Invite to use 2FA` button |
All the itmes written on the UI can be in a GUI. Exmaple: Change Password, Two-Factor Authentication.
| .. seealso:: | ||
| :doc:`Access rights </applications/general/users/access_rights>` | ||
| :doc:`Portal access documentation <portal_access>` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| .. seealso:: | |
| :doc:`Access rights </applications/general/users/access_rights>` | |
| :doc:`Portal access documentation <portal_access>` | |
| .. seealso:: | |
| - :doc:`Access rights </applications/general/users/access_rights>` | |
| - :doc:`Portal access documentation <portal_access>` |
These appear net to each other, so if it's bulleted they won't be squished, or you can add a space between the lines.




Hiya, @larm-odoo! Here are the user portal pages I've been mentioning in the past couple stand-ups. This is a mixture of all-new material and extant material that's been revised and rearranged in a new format. It's meant to capture the broad strokes of the user portal and its default features without going to deep into specific app integrations at this time. Thanks for the review!
@auva-odoo, I saw a few comments on tasks where you mentioned that there should be a dedicated customer/user portal page, so I thought you'd want to take a look at these. Please let me know if you have any feedback or if there's anything I'm missing/not representing correctly. Thanks!
This 19.0 PR can be FWP up to master.