Update permission.md

[BOAScripts]

Updated the possible property values permission.

Important

Required for API changes:

• Link to API.md file: ADD LINK HERE
• Link to PR for public-facing schema changes (schema-Prod-beta/v1.0.csdl) VALID PRs DON'T INCLUDE API.MD or permissions JSON FILES: ADD LINK HERE

---

Add other supporting information, such as a description of the PR changes:
POST to https://graph.microsoft.com/v1.0/sites/{site-id}/permissions/ with an "owner" role creates a new "none" role.
POST to https://graph.microsoft.com/v1.0/sites/{site-id}/permissions/ with an "fullcontrol" role creates a new "fullcontrol" role.
PATCH to https://graph.microsoft.com/v1.0/sites/{site-id}/permissions/{permission-id} with an "owner" role result in an invalid request
PATCH to https://graph.microsoft.com/v1.0/sites/{site-id}/permissions/{permission-id} with a role "fullcontrol" updates the "none" role to "fullcontrol"

---

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.

[learn-build-service-prod]

Learn Build status updates of commit 939fa4f:

✅ Validation status: passed

File	Status	Preview URL	Details
api-reference/v1.0/resources/permission.md	✅Succeeded

For more details, please refer to the build report.

[learn-build-service-prod]

Learn Build status updates of commit fa2358d:

✅ Validation status: passed

File	Status	Preview URL	Details
api-reference/v1.0/resources/permission.md	✅Succeeded

For more details, please refer to the build report.

[Danielabom]

@BOAScripts are you a MS FTE? Can you provide more context? We can't change permissions content if we don't have enough info.

[BOAScripts]

I guess that If I don't know what a MS FTE means, I'm not one of them.
I had to use this API during sysadmin my job, trying to limit a registered app to only 1 Sharepoint Site and not all of them (Site.Selected scope) but with fullcontrol on it. And at that time, only the "owner" value was mentioned in the doc. Now I see that "fullcontrol" is also mentioned. So I 'll close this merge request as it's resolved.