Working/ Testing without Admin role on QA/PROD

Nikhil Bajaj9
Tera Sage

Hi All,

 

I want my testers to Test in QA environment and cross verify the things in PROD after code movement but i don't want to give them Admin Role on PROD and QA as well. Can you please suggest the best strategy or what role apart from sn_read_onlyITIL and impersonator i should provide my Dev and Testers on QA/PROD environment. 

 

 

@Ankur Bawiskar , @Dr Atul G- LNG , @Allen Andreas , @Mark Roethof , @Maik Skoddow , @Ashutosh Munot1 , @Sandeep Rajput , @Anurag Tripathi , @Prasad Pagar , @Ravi Gaurav , 

Please appreciate my efforts, help and support extended to you by clicking on – “Accept as Solution”; button under my answer. It will motivate me to help others as well.
Regards,
Nikhil Bajaj

ServiceNow Rising Star-2025
7 REPLIES 7

Deepak Shaerma
Mega Sage

Hi @Nikhil Bajaj9 

If testing ITSM: itil, approver_user, incident_read, change_read, problem_read .
reports_admin (or report_publisher)
: Often testers need to verify that reports/dashboards are functioning after a deployment. This allows them to view report configurations without modifying system data.
configuring ATF also helps the testers.
Happy to help! ‌‌
To help others in the community find this solution, kindly mark this response as the Correct Answer ‌‌ and Helpful‌‌.
Warm Regards,
Deepak Sharma
Community Rising Star 2025


Ankur Bawiskar
Tera Patron

@Nikhil Bajaj9 

my thoughts

-> in PROD admin can verify if everything came fine, you can try to give Read-only admins to some users to verify

-> in QA try giving minimum these roles

itil, snc_read_only, impersonator + these additional roles:
- asset
- inventory_user
- knowledge
- report_user
- report_admin
- pa_user (Platform Analytics)

💡 If my response helped, please mark it as correct and close the thread 🔒— this helps future readers find the solution faster! 🙏

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

Dr Atul G- LNG
Tera Patron

Hi @Nikhil Bajaj9 

 

The testing is crucial part of any go live.

 

For QA I will say try to get admin rights the reason is bcz if client raised any defect , Dev can easily check n reproduce there only.

 

For testing purpose if admin role not available 

Then

1st ,use ATFvas maximum testing

And test case which are left give the minimum role to complete that part, like ITIL, module specific.

 

 

For prod , yes we never do actual testing, it done by business only.

 

You can request for read only admin that is best way only to see all configuration and also take client help if need to deep dive for testing as I assume they have admin rights.

 

These are kind of best practice you can follow mate.

*************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.

Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/dratulgrover [ Connect for 1-1 Session]

****************************************************************************************************************

AndersBGS
Tera Patron

Hi @Nikhil Bajaj9 ,

 

You shouldn't provide any additional role besides what they normally have on PROD, as UAT = User acceptance test. So basically, they need to verify the solution from a user/fulfiller perspective - not from a developer perspective.

 

If my answer has helped with your question, please mark my answer as the accepted solution and give a thumbs up.

Best regards
Anders

Rising star 2024
MVP 2025
linkedIn: https://www.linkedin.com/in/andersskovbjerg/