Forum Discussion
Best Practices for Tracking Changes on a SharePoint List Accessed by a Service Account
Almost all the information you need can be tracked using versioning in SharePoint. Check:
But if everyone logins using the single service account and making changes to SharePoint list items, you will not be able track "who" made the changes.
Ideally, you should share the SharePoint list with individual users or "group" (SharePoint group or Azure AD group) of users directly instead of sharing service account with everyone.
Please click Mark as Best Response & Like if my post helped you to solve your issue. This will help others to find the correct solution easily. It also closes the item. If the post was useful in other ways, please consider giving it Like.
- rando230May 28, 2024Copper Contributor
Hello again,
Thank you for your prompt response and for suggesting the use of versioning in SharePoint. I have reviewed the versioning settings and understand how it can track the history of individual list items. However, upon further inspection, it appears that versioning in our SharePoint list is limited to list items and does not provide a history of changes made to the list structure itself, such as modifications to calculated column formulas.
This is a significant concern for us because if someone alters the formula in a calculated column, there is no audit trail to indicate who made the change or when it occurred. The lack of this information can lead to confusion and potential data integrity issues, especially since multiple individuals access the list through a shared service account.
Could you please advise on any alternative methods or tools that would allow us to track changes to the list structure, particularly the formulas in calculated columns? We are looking for a solution that can provide a clear audit trail for such changes, which is crucial for maintaining accountability and transparency within our team.
Additionally, I understand the recommendation to share the SharePoint list with individual users or groups directly. However, due to specific operational requirements, we currently need to maintain access through a shared service account. Given this constraint, are there any best practices or workarounds that can help us monitor who is making changes when logged in through the service account?
I appreciate your assistance and look forward to any further insights you may have on this matter.
- cseb96Aug 08, 2024Copper ContributorHey mate, after the same thing. Were you able to get an answer for this?