I have a custom table with following ACLs:
- create/write/delete - only admin
- read - users with itil role
During testing a scheduled import, I set the 'run_as' field to an itil user (NOT an admin account). The import ran successfully and inserted records show the forementioned itil user in the 'sys_created_by' field.
So here's my question: do scheduled imports respect ACLs in regards to the user in 'run_as' field? My tests suggest that they don't but I wasn't able to find anything to back my claim in the documentation.
PS. Yes, the example is over-simplified and unrealistic - it's obviously wrong to run imports as itil user. However, it wouldn't be hard to come up with a more realistic example and I'm only asking about the relation between import sets and ACLs - not a specific use case.
