Based on the information provided in the knowledge sources, I don't have enough specific details to directly address your issue about updating Ory Network Permissions Rules and the new function not being recognized by the check API. However, I can provide some general insights and suggestions based on the available information about Ory Permissions. 1. Testing Permissions: According to the [Ory documentation on creating permission models](https://www.ory.sh/docs/keto/modeling/create-permission-model#test-permissions), it's important to test your permission model after making changes. The documentation suggests: - Automating testing of your permission model using the SDK in your preferred programming language. - For complex permission model changes, using a separate Ory Network project for testing before deploying changes. 2. Relationship Creation: The new function you've added (

readOwnedObjects

) might need corresponding relationships to be created. As mentioned in the [Ory Permissions overview](https://www.ory.sh/docs/guides/permissions/overview), permissions are based on relationships between subjects and objects. 3. API Synchronization: There might be a delay or synchronization issue between updating the permissions in the web UI and the changes being reflected in the API. The documentation doesn't explicitly mention a process for applying updated permission models, but it's possible that there could be a propagation delay. 4. Checking Permissions: You might want to double-check your permission check using the methods described in the [API documentation for checking permissions](https://www.ory.sh/docs/reference/api). Ensure that you're using the correct API endpoints and parameters for your check. 5. Potential Bug: There's a possibility that this could be a bug. In the [GitHub issue about loading permissions](https://github.com/ory/network/issues/293), there was a problem with loading permission rules in the Ory console. While this issue was marked as fixed, it shows that such issues can occur. Given the lack of specific information about applying updated permission models, I would recommend reaching out to Ory support or posting in their community forums for more targeted assistance with this issue. They would be able to provide more specific guidance on whether there are additional steps needed to apply updated permission models or if this is a potential bug in the system.