Fix SharePoint Showing the Wrong Created By User
Question details
Users notice that a SharePoint document library displays an unexpected user name in the system 'Created By' field, and files sometimes disappear completely after HR personnel update metadata like the 'Verified' status.

- Product
- Microsoft SharePoint
- Device & OS
- not provided
- Scenario
- Managing employee records in a SharePoint document library using custom columns, Power Apps, and automated workflows.
- Observed behavior
- The 'Created By' column displays the account of the uploader (such as an HR admin or workflow connection) instead of the actual employee, and files unexpectedly vanish from the library view after their status is changed to 'Verified'.
Ensure you have Site Collection Administrator or Library Owner permissions to access SharePoint audit logs, library settings, and the Power Automate run history.
Identify the Root Cause of the 'Created By' Discrepancy
Understand how SharePoint assigns the system 'Created By' value and cross-reference it with custom metadata columns.
SharePoint automatically sets the system 'Created By' field to the exact account that uploaded or created the file. If an HR administrator, a shared service account, or a Power Automate connection uploads the file on behalf of an employee, that specific account will appear as the creator.
Go to your SharePoint document library, click the gear icon for 'Settings', and select 'Library settings'. Ensure your custom 'Submitted By' column is properly mapped and separated from the system 'Created By' column.
Click the three dots (...) next to the affected file and select 'Version history'. Review the initial version to see exactly which account originally uploaded the document to the library.
If a workflow or Power App is responsible for uploading the files, navigate to the Power Automate portal, locate the flow, and check the 'Connection references' to see whose credentials the flow is using to create the files.

Locate Disappearing Files After Status Updates
Investigate missing files by checking filtered views, retention policies, audit logs, and recycle bins.
Edit Document Properties Seamlessly with WPS Office
While resolving complex SharePoint library workflows requires adjustments within the Microsoft ecosystem, managing your offline document creation and editing doesn't have to be complicated. WPS Office is a lightweight, highly compatible alternative to Microsoft Office that lets you view, edit, and organize document properties easily before uploading them to your team's portals.

Frequently Asked Questions
Can I manually change the 'Created By' field in a SharePoint library?
By default, the SharePoint user interface does not allow users to edit the 'Created By' system column. To change it, you must use Power Automate (via the 'Send an HTTP request to SharePoint' action), PowerShell (such as PnP PowerShell), or third-party SharePoint migration tools to overwrite the system metadata.
Why do files disappear from my view when I change a column value to 'Verified'?
Files usually disappear after a metadata change because of an active Power Automate workflow that moves the file to an archive library, a filtered view that hides 'Verified' items from the active list, or strict compliance retention policies that archive completed records.
How do I make the 'Submitted By' column accurately reflect the employee's name?
If you are using a Power Apps front end, ensure the app captures the 'User().FullName' or 'User().Email' and writes it specifically to your custom 'Submitted By' column during the patch or submit function. Relying on the SharePoint 'Created By' column will only capture the account running the workflow.




