Hi @ravi-chandra3197. Thank you for your contribution
Here are some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

• @magento give me test instance - deploy test instance based on PR changes
• @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

• @magento run all tests - run or re-run all required tests against the PR changes
• @magento run <test-build(s)> - run or re-run specific test build(s)
  For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names. Allowed build names are:

1. Database Compare
2. Functional Tests CE
3. Functional Tests EE,
4. Functional Tests B2B
5. Integration Tests
6. Magento Health Index
7. Sample Data Tests CE
8. Sample Data Tests EE
9. Sample Data Tests B2B
10. Static Tests
11. Unit Tests
12. WebAPI Tests
13. Semantic Version Checker

You can find more information about the builds here

ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review.

For more details, please, review the Magento Contributor Guide documentation.

⚠️ According to the Magento Contribution requirements, all Pull Requests must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of Pull Requests 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.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

@magento run all tests

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@magento run Functional Tests CE

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

Hi @ravi-chandra3197 Thanks for your contribution!
This PR has no details about the issue at all. Kindly provide me the below details in order to process it please.

1. Issue summary
2. Detailed description about the issue
3. Detailed steps to reproduce the issue
4. Expected result
5. Actual result
6. Any additional information if you can provide along with screenshots as such please

Thanks in advance!

Hello @engcom-Alfa
Admin configuration is a global level configuration so security configuration is not visible on the website and store wise, This PR remove security configuration to show in website and store as the admin section is not allowed to set configuration website wise.
Here is the ref. snapshot for the same.

@magento run all tests

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@magento run all tests

Pull Requests are not mergeable to the mainline. Please merge the latest mainlines to your Pull Requests and restart the builds.

@ravi-chandra3197 , Please resolve the conflicts on the PR to proceed further.

Thanks,

@magento create issue

@magento run all tests

Hi @ravi-chandra3197,

Thanks for your contribution.

We have verified the issue in Latest 2.4-develop instance and the issue is no more reproducible.Please refer the screenshot.

Hence We are closing this PR please feel free to reopen the PR.

Thanks.