No Admin Access in Production

[Richard101]

In our IT environment, admin access is generally not granted in production systems to development teams. This has raised some concerns of areas of support for us. Areas I think that this could get in the way:

• Cloning
• Applying Updates sets
• Monitoring background stuff like MID Servers, LDAP, scheduled jobs, etc.

If you are in a similar situations, how do you handle these activities? What kind of access are you granted if not full admin that allows you to troubleshoot and maintain the system effectively? What are other areas of concern if the development team does not have admin access? How do you handle these situations?

We still have the admin role now since we are still in the early stages after our go-live and first upgrade.

[Pradeep Sharma]

Hi Richard,

Here is the list of all OOTB roles with what access are granted with individual role. Depending on your req you may grant few roles to the users. More info here

Base System Roles - ServiceNow Wiki

[Chris M3]

This is a serious sore spot with ServiceNow.   While some of the functions you might monitor in production have a secondary role that will give you access, there are a lot that do not.   A great example is logs.

Customizing roles & ACL's for all of these tables would be a nightmare.   I would like to see a read only admin role, and a write admin role.   Or use the same type of functionality as security_admin, where you have to escalate your privledges to modify anything system related.   It is really easy when you first start to modify something you thought was our personal view, when it was actually the global (better now that the right click option is configure, and not personalize)

To answer your question, our developers/support personnel have admin in production.