This article provides options for sharing access with a third party for testing/validation when you are having an issue with an extension for Adobe Commerce on cloud infrastructure.
Proper internal data security procedures and requirements should be followed on your part when deciding the way to provide access to a third party.
Depending on your internal security standards, you may choose to have the third-party troubleshoot on a local environment. If the issue cannot be reproduced locally, you may wish to provide access to your cloud environment. If you elect to do so, please be sure to work within your internal security standards. If providing access to any of your cloud environments, be sure that your third party is clear on what can be done and what approval is required for things such as replication only or allowing for code changes. This is especially important for Production environments.
Provide your third-party vendor access to the cloud environment. Related articles:
Create a database dump (or give the third-party vendor access to do this). It can be done using the CLI or in the Commerce Admin. This DB dump will obfuscate customer data, so all they get is code and product SKU’s, etc., no proprietary/customer data. For reference, use [Sharing Your Commerce Account] (/docs/commerce-knowledge-base/how-to/general/create-database-dump-on-cloud.html?lang=en) in our support knowledge base.
Once testing is complete, make sure to revoke the shared access to your cloud environment, as described in Adobe Commerce Help Center User Guide > Revoke (delete shared access) in our support knowledge base.
Standard practice is to troubleshoot on a local environment. If the issue cannot be reproduced locally, go to Staging. The third party might need to check on Production. Ensure that your third party is aware that they are only to try to reproduce the issue on Production and Staging and to not make any code changes, and if they need to make code changes, they must first get your permission.