system user permissions for the Flow Designer to execute Look Up Records action to get records

[Naveen Bagula]

All,

I have a question on system user permissions. Loop Up Records is not working in flow designer for system user, Here is the scenario, "Lookup Records" action on the CMDB table within the Flow Designer. When executed as the "system user" in the properties, this action fails to get records. However, it operates as expected when run under a user account possessing CMDB-related roles.

Given that the "system user" is an out-of-the-box system account, it cannot be directly "found" or "selected" in the same manner as a human user account. Could you please advise on how to handle this situation? Specifically, I need guidance on granting "cmdb_read" permissions to the system user to enable it to execute an encoded query for the "Lookup Records" action in flow designer.

[Chaitanya ILCR]

Hi @Naveen Bagula ,

you won't find System user it's Service account( I don't think there are any restrictions unless we ask ServiceNow to do so) 

cmdb_read is a basic role system user should be able to perform the query operation

check if there is any query business rule or ACL which is blocking it

if no better raise an HI case with serivcenow vendor on this

Please mark my answer as helpful/correct if it resolves your query.

Regards,
Chaitanya

[AnveshKumar M]

Hello @Naveen Bagula 

As suggested by @Chaitanya ILCR you can not add roles to the system user.

You can try an alternative, select run as user as "User who initiates session" and in the "Run with roles" section, select all the roles which are needed to complete the job in that flow.

This will ensure security and avoid unnecessary concerns of running as system user.

See the documentation at https://www.servicenow.com/docs/bundle/yokohama-build-workflows/page/administer/flow-designer/task/c... 

Please mark my answer helpful 👍 and accept as solution ✅ if it helped you.

[Ankur Bawiskar]

@Naveen Bagula 

system user should have all the access.

if it's not working as expected then raise a case with ServiceNow.

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