Can a scoped application on store create records in system tables example: sys_choice, sys_user etc

[MGR]

Our team is in the process of developing a scoped application intended to create records in the following system tables:

• sys_choice
• contract_sla
• sys_user_group
• sys_user_member
• sys_ui_policy
• sysevent_email_action

We recognize that user permissions need to be configured to grant create access for these tables to enable record creation from our scoped application. We would like to confirm whether this approach adheres to ServiceNow's best practices and guidelines for scoped applications.

Any insights or recommendations you could provide would be greatly appreciated.

Thank you for your assistance.

Best regards,

Govardhan

[Ankur Bawiskar]

@MGR 

Responses inline

• sys_choice - this table doesn't link to any scope, but remember the sys_choice_set table has scope associated to it and you can create it in your scoped app Working with Choices in ServiceNow 

• contract_sla - yes ideally the SLA definitions should be created in your own scoped app
• sys_user_group - doesn't matter as the records are not associated to any scope and are always in global
• sys_user_member -doesn't matter as the records are not associated to any scope and are always in global
• sys_ui_policy - yes in your scoped app
• sysevent_email_action- yes in your scoped app

If my response helped please mark it correct and close the thread so that it benefits future readers.