need best practice recommendation

Servicenow lear
Tera Contributor

Dear All,

I’m in a bit of a challenging situation and would appreciate your insights.

 

Our team is currently facing significant bandwidth constraints, yet we frequently receive requests from individuals outside the platform team for access to our ServiceNow instances so they can develop solutions on their own.

While their intentions are good, most of them do not have prior experience with ServiceNow—just some exposure through online videos and they are part of devops and other software development background —which raises concerns around quality, stability, and long-term maintainability. At the same time, there is increasing pressure to unlock development access.

I’d like to know if others have encountered similar scenarios:

Do you grant admin-level access in lower environments and rely on guardrails?
How do you balance agility with platform integrity, especially when bandwidth limits the ability to perform code reviews or implement a BPE tool?

Given our current team size and workload, we cannot commit to code reviews or governance tooling at this time. I’m trying to determine whether opening up the instance for external development is advisable, or if there are alternative approaches we should consider.

Any recommendations or experiences would be greatly appreciated.

2 REPLIES 2

Dr Atul G- LNG
Tera Patron

Hi @Servicenow lear 

 

yet we frequently receive requests from individuals outside the platform team for access to our ServiceNow instances so they can develop solutions on their own.

 

Atul:

This is a clear case of implementing Idea and Demand Management, where any individual or group outside the platform can submit a new idea or request for work. The platform team, demand board, governance board, or product owner then evaluates the idea and converts the approved demand into a project.

Providing direct access to external users is not a best practice. Your internal platform team should own the platform and be responsible for all development activities.

More than just a tool, you need to implement proper governance and a standardized process to manage this effectively.

*************************************************************************************************************
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]

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

Thanks for the response.

 

The 3 pillars of governance is already there.  However the mindset is still the same where in it is treated as tool just like anyother such as devops and expectation is to unlock and unblock development.  Unfortunately , the pressure is such if you cannot fdo it then we want to do it and then escalations and what not. So I am trying to understand if there has been or somewehre people outside of platform team are given access to lower instances because I am afraid then it will allow other parts of org to strart accessing it