As a merchant I want to require my customers to choose if Login as Customer can be used on their account so that I can respect their preferences for their online account.
MoSCoW
Must have
Current State
The ability to Login as Customer can be restricted via Admin Roles for particular admin users. Using the Admin Roles it can also be restricted to particular websites in a multi-store configuration. However, it is not possible to disable Login as Customer on a per-customer basis.
Business Value
For a variety of reasons, customers may not want merchant admin users to log in to their storefront account. To respect the privacy and choices of these users, the ability to log in to a customer's account should be an opt-in permission.
UX design/mockups
AC
Stores>Configuration>Customers>Login as CustomerGET /V1/customers/:customerIdPOST /V1/customersPUT /V1/customers/:customerIdPUT /V1/customers/meGET /V1/customers/meOut of Scope
Exact Wording for Options
Allow remote shopping assistanceThis allows merchants to "see what you see" and take actions on your behalf in order to provide better assistance.Login as Customer not enabledThe user has not enabled the “Allow remote shopping assistance” functionality. Contact the customer to discuss this user configuration.CloseTitle for Login as Customer opt-in checkboxLogin as Customer checkbox tooltipMy suggestions:
Opt-in permission: Allow remote shopping assistance
Tooltip text: This allows merchants to "see what you see" and take actions on your behalf in order to provide better assistance.
Modal title: Login as Customer not enabled
Modal text: The user has not enabled the “Allow remote shopping assistance” functionality. Contact the customer to discuss this user configuration.
Modal action button: Close
Name of title setting in admin panel: Title for Login as Customer opt-in checkbox
Name of tooltip setting in admin panel: Login as Customer checkbox tooltip
Thank you @dobooth! I have updated the AC to reflect your wording suggestions.
UX mockups to be added on 13 May
Hello @mbrinton01
fyi: @naydav @engcom-Foxtrot @engcom-Delta @engcom-Lima
During testing, we found small inconsistencies between UX Design and Requirements related to SCOPE for opt/in setting in Admin Panel
In Requirements(description of this issue):
Merchant can adjust title for setting and wording used in tooltip in admin settings
Under Stores>Configuration>Customers>Login as Customer
Title and tooltip are two different settings
Settings are responsive to website scope
Use System Value is checked by default
In UX Design this option has GLOBAL scope: https://xd.adobe.com/view/b9d43ac6-ee9f-4e94-516a-70dd15b45232-cfe5/screen/1a053b2c-4dcf-47e2-9927-493425bbadce/
I assume it should be on website level, but want to double-check with you
Correct, it should be on website level.
Hi @sdzhepa. Thank you for your report.
To help us process this issue please make sure that you provided the following information:
Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:
@magento give me 2.4-develop instance - upcoming 2.4.x release
For more details, please, review the Magento Contributor Assistant documentation.
Please, add a comment to assign the issue: @magento I am working on this
Join Magento Community Engineering Slack and ask your questions in #github channel.
:warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
:clock10: You can find the schedule on the Magento Community Calendar page.
:telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.
:movie_camera: You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel
:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel
Does this affect the GraphQL mutations for creating/updating a customer? (createCustomerV2 and updateCustomerV2 in 2.4.1.)
Please, with all due respect but this function is only used when customers are stuck. Most of these customers have no idea and now you have to talk them through a list of steps to get this setting done.
By the way I just got a new customer that has a bought theme that doesn't have this setting present in the frontend for customers.
So you-re stuck unless you enter their ID directly into the database.
I will log a new request to make this a system setting.
Make Login as Customer:
Drop down: Opt-in/ opt-out/ Available/ Not Available.
Most helpful comment
Correct, it should be on website level.