- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-07-2014 11:35 AM
So I'm having some concerns with my role within my company and using SN. Technically by title, I am the SN Admin. However, lately it seems that I'm being pushed more into the Developer side of SN. Does anyone have any strict definition of duties of a SN Admin and a SN Developer? I don't mind working my way into the Development side, however i'm currently NOT a developer and would need quite a bit more training to bring my skill set up to par in SN. Right now my time is being split between SN Admin role and a Tech Support Lead role. I don't have any problem with my current work load, however if they need me to work more on the development side, then i'd have to step away from the tech support side of things. . . . anyways that is a long way around for asking about having strict definition of duties between a SN Admin and a SN Developer?
Solved! Go to Solution.
- Labels:
-
Service Mapping

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-07-2014 11:59 AM
I think most people would say they are the same thing. ServiceNow development and administration fit under the same permissions and roles in the system so they are generally accomplished by the same people. You might have admins with different specialties though (scripting and integrations vs standard configurations for example) but I think the two terms are pretty much interchangeable.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-08-2014 05:51 AM
Not unlike the others, what I've seen (and witnessed in the past) is the word "Engineer". A ServiceNow Engineer would be both Admin and Developer. I've been in similar roles where I'd be the lead developer but also have a lot of admin responsibilities, much like all the admins on the team would also have developer activities.
Unless you have a large team and they need a full time developer, I'd say in most places the developer would be in charge of administration as well (and you'd expect that the admins would also dabble in development).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-08-2014 07:21 AM
Thanks everyone! Your answers were exactly what I was looking for!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-09-2014 11:18 AM
Hi Timothy,
I understand your dilema. I have two admins supporting our instances and occassionaly they need to get invovled in helping to fix things, edit UI or fields, etc. However, the lines are easy to blur and the real danger is in the old "fox/hen house" scenario. You are supposed to run the application and maintain the application. Part of that is ensuring that all changes are authorized, validated and released per your defined processes. Unauthorized changes (especially in production) will lead to an unsupportable mess. None of my developers have admin role in production.
I recommend caution and setting some strict policies/guidelines...
Matt
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-13-2018 10:17 AM
In my company, we devide the roles and administrators should not have access to Studio. Is there a way to create like an HR Administrator role that allows an HR Admin perform any configuration role excep getting into Studio?