Currently, the module relies on the generic 'administer site configuration' permission. It is very common to have separate admins for managing product-related content and because of that, it would be nice to have separate permissions for operating this module.

Issue fork magento-3285292

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

gaurav.kapoor created an issue. See original summary.

elber’s picture

Assigned: Unassigned » elber
elber’s picture

Assigned: elber » Unassigned

Vighneshh made their first commit to this issue’s fork.

vighneshh’s picture

Status: Active » Needs review
aarti zikre’s picture

Status: Needs review » Reviewed & tested by the community
StatusFileSize
new38.01 KB
new57.89 KB
new74.89 KB

Reviewed and verified MR
https://git.drupalcode.org/issue/magento-3285292/-/tree/3285292-add-perm...

Testing step:

* Install new instance of Drupal 9.5.x.
* Install and enable Magento and all require modules.
* Go to the /admin/people/roles/add created new role "Magento Access" Set permission "Access magento configuration page"
* Go to the /admin/people/create created new user called "Magento user" which has "Magento Access" role
* Log in as Magento user.

Test Result:
By visiting this rout (/admin/config/magento) the form should is accessible to user.

Reference SS
Without Permission Set:

2022-08-08/3285292 without permission.png

Permission Added:
2022-08-08/3285292 with permission.png

Permission Details:
2022-08-08/3285292 permision.png

Test result : Pass
Can be move to RTBC

  • Vighneshh committed 4fa0adb on 2.0.x
    Issue #3285292 by Vighneshh, aarti zikre, gaurav.kapoor: Add permissions...
vighneshh’s picture

Status: Reviewed & tested by the community » Fixed

Thanks @aarti_zikre .

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.