How do I set up Scoped Application roles?

[darengneiting]

I have created a scoped application to track details of our morning status call.   We have 4 facilitators that would open a status call record and have ability to edit any field (except the ticket number).   Then there are about 40 contributors that should be able to access the status call form and provide details.

I created an admin role, editor role, and user role.   I also created groups that match and added members to these groups.

Do I need to assign the roles to something else to make this work?   Do I need to specify exactly what each role will have ability to edit?

There are some default Access Controls; read, create, write, delete - Do I need to assign these?

I'm not a developer by trade, but a Problem & Change Manager attempting to create this and let our developers work on other more critical items.

Any help is appreciated!

[coryseering]

Hi Daren,

You cannot edit the ACL until you elevate to Security Admin, and so you cannot change the roles for that ACL.

Elevate to a privileged role

If you're familiar with a Linux system, this would be like temporarily elevating to an admin using su. Windows has a similar functionality, where you have to run some things "as an administrator". You are telling the system to temporarily grant you the "security_admin" role, which is required to edit ACLs. This is an action that you take outside of Studio (though we are working on getting that built in). Once you have elevated to security_admin, you can open the ACL in Studio and edit it- including adding or removing roles from the Role List.

You may want to take a crash course on the security model and ACLs beforehand:

Access control list (ACL) rules

ServiceNow Developers

Using Access Control Rules - ServiceNow Wiki

Thanks

Cory

[darengneiting]

Thank you for the references!

[Mike Allen]