Context / Environment
- Use case: Reassigning incidents via REST API and adding a work note.
- Tables involved: incident (standard task table with work_notes).
- Auth: Integration user (OAuth).
- Expected author: The actual operator (e.g., demouser) should be shown as the creator of the work note.
- Actual author: Work notes are showing as “System Administrator”.
✅ What I’m Doing
- Calling PATCH on /api/now/table/incident/{sys_id} with body containing:JSON{"assigned_to": "<user_sys_id>","assignment_group": "<group_sys_id>","work_notes": "[Reassigned by <operator>] <short note>"
- I also tested creating a journal row explicitly via POST /api/now/table/sys_journal_field.
🎯 Expected vs Actual
- Expected: The work note appears as created by the operator(logged in user from API) (e.g., demouser).
- Actual: The work note appears under System Administrator(Admin logged in SNOW Portal), regardless of who triggered the action.
Question :
1.Any special permission to be assigned to Admin to add worknotes_or_comments on behalf of user - 2.Any way we can (via modern Authentication) be used to assign user of the worknote in SNOW Portal
In the above image, instead of [reassigned by demouser] displayed under System Administrator , the expected behavior is worknote should be created under DemoUser via rest api (it will show the user until user impersonation is done, but is it possible to do it on behalf of user without user impersonation )
- Calling PATCH on /api/now/table/incident/{sys_id} with body containing:
