A group of Microsoft Products and technologies used for sharing and managing content, knowledge, and applications.
Hello @Evan,
Based on my testing, this behavior is expected in SharePoint Online.
The “Require content approval for submitted items” option is part of the classic approval model. When "Configure approvals" > Enable approvals is turned on in a document library, SharePoint automatically hides the classic content approval setting. This is likely because SharePoint does not allow both approval models to be enabled at the same time.
In summary:
- When "Configure approvals" is enabled, SharePoint uses the modern approval framework and the "Require content approval" option is hidden.
- When "Configure approvals"s is disabled, the classic "Require content approval for submitted items option" becomes visible again in Versioning settings.
This is not a permissions issue and does not indicate a problem with the library.
To prevent conflicts between these two features, I recommend the following:
- If you want to use modern approvals (integrated with the Approvals app, Power Automate, and Teams), keep Configure approvals enabled and do not use the classic content approval option.
- If you need the classic “Require content approval” behavior, first turn off Configure approvals, then enable content approval from the library’s Versioning settings.
Please choose one approval method based on your business requirements, as these approaches typically cannot be used together within the same document library.
If you have any further question, please feel free to reply. I'm here and happy to help!
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.