That said let’s see what the AI can suggest - @Ask Inkeep

The available documentation covers the basic SCIM setup with Okta (1) , but doesn't specifically address group linking issues or the 100-object import limitation you're encountering. Based on the SCIM integration guide, the setup process involves configuring the SCIM 2.0 Test App with your Permit.io project and environment IDs, and using the Push Groups tab to add Okta groups corresponding to Permit.io roles . However, the specific troubleshooting steps for "No match found" errors or pagination limits aren't covered in the available sources. For this level of debugging, you'll need direct engineering support to investigate: 1. Which Workspace / Project / Env you are using 2. The specific API calls being made during the group sync (you can check Okta's system logs for the exact SCIM requests) 3. Whether there are pagination settings in Okta's SCIM configuration that might be limiting results to 100 objects 4. Any error logs from the SCIM integration on the Permit.io side The 100-object limit suggests a pagination issue in how Okta is querying the Permit.io SCIM endpoint, which would require configuration adjustments in either Okta or investigation of the SCIM endpoint's response format.

To learn more, see the sources I considered: [[1] SCIM Integration with Permit.io via Okta](https://docs.permit.io/integrations/SCIM/OKTA)