permitio · alon-boshi · Nov 23, 2025 · Nov 16, 2025 · Nov 16, 2025 · Nov 17, 2025
diff --git a/docs/ai-security/integrations/langchain.mdx b/docs/ai-security/integrations/langchain.mdx
@@ -627,7 +627,7 @@ user_input = "Yes"  # Imagine this comes from a UI click
 if user_input.strip().lower() == "yes":
     schedule_response = await external_access_manager.schedule_appointment(
         token=settings.test_jwt_token,
-        appointment_details={"date": "2025-03-10", "time": "10:00 AM"}
+        appointment_details={"date": "2025-12-10", "time": "10:00 AM"}
     )
     print("Scheduling Response:", schedule_response)
 ```

diff --git a/docs/ai-security/integrations/mongodb-rag.mdx b/docs/ai-security/integrations/mongodb-rag.mdx
@@ -109,7 +109,7 @@ Query endpoint:
 ```bash
 curl -X POST http://localhost:8000/query \
  -H "Content-Type: application/json" \
- -d '{"query": "Tell me about 2024 budget", "user_id": "user_marketing_1"}'
+ -d '{"query": "Tell me about 2026 budget", "user_id": "user_marketing_1"}'
 ```
 
 Try querying as:

diff --git a/docs/api/background-tasks.mdx b/docs/api/background-tasks.mdx
@@ -4,11 +4,7 @@ title: Background APIs
 description: "Understand APIs that run in the background"
 ---
 
-# Background APIs (EAP)
-
-:::info Early Access Program
-Background APIs are part of the Early Access Program (EAP) and are subject to change.
-:::
+# Background APIs
 
 Some APIs in Permit run in the background and can be triggered without awaiting a response.
 These APIs are commonly used for operations that require scheduling, are not time-sensitive, or may take significant time to complete.

diff --git a/docs/api/v2-migration-guide.mdx b/docs/api/v2-migration-guide.mdx
@@ -157,7 +157,7 @@ Obviously if you have code that interfaces directly with the Permit.io cloud API
 
 Other than that, you'll want to switch to the new v2 PDP. It's configured exactly the same, and if you're not using Organization-scoped objects, should work identically but be a lot faster, as we've also done major optimization work on the v2 PDPs.
 
-Once you have the v2 PDP running in parallel to the v1 PDP, you need to switch to the v2 SDKs. For now, they're available in Python, Javascript, and .Net, with other languages becoming available in the coming weeks.
+Once you have the v2 PDP running in parallel to the v1 PDP, you need to switch to the v2 SDKs. 
 
 ### Migration Order
 
@@ -224,7 +224,7 @@ await permit.api.sync_user(user)
 
 With user being a dict containing the same attributes as in the REST API (in this case, only 'key' is mandatory, though usually you'd also provide either an email address or first and last names to make the decision logs more user-friendly).
 
-For more information, see the full documentation for [Node.js](/sdk/nodejs/quickstart-nodejs) and [Python](/sdk/python/quickstart-python). (more languages coming soon!)
+For more information, see the full documentation for [Node.js](/sdk/nodejs/quickstart-nodejs) and [Python](/sdk/python/quickstart-python).
 
 ## V1 API Deprecation
 

diff --git a/docs/api/working-with-abac/examples.mdx b/docs/api/working-with-abac/examples.mdx
@@ -3,7 +3,7 @@ sidebar_position: 6
 title: Condition Set Rule Examples
 ---
 
-### Example #1
+### Example
 
 #### Students that study at Stanford University and are not part of the part-time study scheme can rent University bicycles after 5pm.
 
@@ -78,7 +78,3 @@ Finally, let's define our condition rule:
     "resource_set": "rent_bicycle_after_5"
 }
 ```
-
-### Example #2
-
-Coming Soon.
diff --git a/docs/concepts/pdp/configuration.mdx b/docs/concepts/pdp/configuration.mdx
@@ -186,16 +186,6 @@ Default: `None`
 
 The token used for centralized logging.
 
-#### PDP_CENTRAL_LOG_ENABLED
-
-Default: `False`
-
-Forward logs to the centralized logging service.
-
-:::danger
-This feature is deprecated and will be removed in future versions.
-:::
-
 #### PDP_PING_INTERVAL
 
 Default: `10`
@@ -342,12 +332,6 @@ Data update callbacks can increase data synchronization latency.
 Optimize the callback endpoint to handle expected loads efficiently.
 :::
 
-#### PDP_FACTDB_ENABLED
-
-Default: `False`
-
-Enable FactDB for this PDP. For more information, see the [FactDB documentation](/concepts/pdp/factdb).
-
 #### PDP_CACHE_STORE
 
 Default: `none`

diff --git a/docs/concepts/pdp/factdb.mdx b/docs/concepts/pdp/factdb.mdx
diff --git a/docs/concepts/pdp/overview.mdx b/docs/concepts/pdp/overview.mdx
@@ -302,33 +302,6 @@ flowchart LR
 
 For truly massive data sets needed in the PDP, you can apply sharding to split the data between multiple PDPs within the same cluster.
 
-This is done by using an [Envoy Server](https://www.envoyproxy.io/docs/envoy/latest/) as proxy to route requests to the relevant PDP based on the tenant.
-For more information, see the [Sharded PDPs guide](/how-to/manage-data/pdp-sharding).
-
-```mermaid
-graph LR
-    subgraph Your Network
-        envoy[Envoy]
-        pdp1[PDP - Shard #1]
-        pdp2[PDP - Shard #2]
-        app1[Service #1] -- query --> envoy
-        app2[Service #2] -- query --> envoy
-        envoy -->|Based on Tenant| pdp1
-        envoy -->|Based on Tenant| pdp2
-    end
-
-    cloud[Permit.io Cloud]
-    pdp1 <--> cloud
-    pdp2 <--> cloud
-
-    style cloud fill:#ffb381,color:#000;
-    style app1 fill:#974ef2,color:#fff;
-    style app2 fill:#974ef2,color:#fff;
-    style pdp1 fill:#f76808,color:#fff;
-    style pdp2 fill:#f76808,color:#fff;
-    style envoy fill:#4e7ef2,color:#fff;
-```
-
 ## PDP Caching Mechanism
 
 The PDP server includes a configurable caching mechanism that significantly improves performance by reducing redundant policy evaluations. 

diff --git a/docs/embeddable-uis/element-login.mdx b/docs/embeddable-uis/element-login.mdx
@@ -630,7 +630,7 @@ permit.elements.logout();
 ```
 
 ---
-### Support for private browsing mode (EAP)
+### Support for private browsing mode
 
 
 Permit Element is now compatible with private browsers, such as Chrome Incognito Mode and Safari.

diff --git a/docs/embeddable-uis/embedding-elements.mdx b/docs/embeddable-uis/embedding-elements.mdx
@@ -69,7 +69,7 @@ Make sure your Permit user key is the same as the JWT sub. You can see your Perm
 Dashboard. You can see your JWT sub with sites like [jwt.io](https://jwt.io/). Just paste your JWT token into the text dialog
 and check the left side of the sub field.
 
-For more information about the JWKS configuration, you can read the [Permit JWKS Configuration](/foaz/fetching-jwks/#what-are-jwks)
+For more information about the JWKS configuration, you can read the [Permit JWKS Configuration](/how-to/enforce-permissions/url-mapping/fetching-jwks/#what-are-jwks)
 documentation.
 
 ## Installing Permit-js
-Original file line number
+Diff line change
@@ Expand Up / @@ -630,7 +630,7 @@ permit.elements.logout(); @@
     ```
     ---
-    ### Support for private browsing mode (EAP)
+    ### Support for private browsing mode
     Permit Element is now compatible with private browsers, such as Chrome Incognito Mode and Safari.
@@ Expand Down @@