Skip to content

Conversation

@MathijsNabbe
Copy link

After researching the minimal permissions for the Update listItem i have found a discrepancy in the documentation page:

The documentation states that the minimal permission required to update column values is Sites.ReadWrite.All. After further research using the Graph Explorer, it can be proven with the screenshots below that only Files.ReadWrite.All is enough to make the request.

Updating a listItem with the Graph Explorer with basic permissions (results in 403 - Forbidden):
Screenshot 2025-05-23 100250

Updating a listItem with the Graph Explorer with Files.ReadWrite.All added (results in 200 - Ok):
Screenshot 2025-05-23 100553

I have updated the documentation file accordingly.


Important

The following guidance is for Microsoft employees only. Community contributors can ignore this message; our content team will manage the status.

After you've created your PR, expand this section for tips and additional instructions.
  • do not merge is the default PR status and is automatically added to all open PRs that don't have the ready to merge label.
  • Add the ready for content review label to start a review. Only PRs that have met the minimum requirements for content review and have this label are reviewed.
  • If your content reviewer requests changes, review the feedback and address accordingly as soon as possible to keep your pull request moving forward. After you address the feedback, remove the changes requested label, add the review feedback addressed label, and select the Re-request review icon next to the content reviewer's alias. If you can't add labels, add a comment with #feedback-addressed to the pull request.
  • After the content review is complete, your reviewer will add the content review complete label. When the updates in this PR are ready for external customers to use, replace the do not merge label with ready to merge and the PR will be merged within 24 working hours.
  • Pull requests that are inactive for more than 6 weeks will be automatically closed. Before that, you receive reminders at 2 weeks, 4 weeks, and 6 weeks. If you still need the PR, you can reopen or recreate the request.

For more information, see the Content review process summary.

@MathijsNabbe
Copy link
Author

I just noticed the DO NOT MODIFY description in the file. Is there any other way this change can be made? I'd be happy to make the change if pointed in the right direction.

@learn-build-service-prod
Copy link

Learn Build status updates of commit 8a4b973:

✅ Validation status: passed

File Status Preview URL Details
api-reference/v1.0/includes/permissions/listitem-update-permissions.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@Danielabom
Copy link
Contributor

@MathijsNabbe, permissions should be updated in our main repo. Which workload are you with?

@MathijsNabbe
Copy link
Author

@Danielabom i don't think i understand what you are asking. Do i need to make this change in another repository?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants