docs: FAQ page components and data (#6402)

Author: TyroneOrrego

docs/docs/administration-and-security/access-control/saml.md

@@ -28,7 +28,7 @@ Users that log in using SSO can only belong to one Flagsmith organisation. If a
 
 If you are self-hosting Flagsmith, TLS is required. Encrypted SAML assertions are not supported.
 
-## Setup SAML
+## Setup SAML {#setup}
 
 :::tip
 
@@ -105,7 +105,7 @@ this mapping tells Flagsmith to look for user groups in a claim other than the d
 
 By default, users logging in via SAML will have no permissions to view or modify anything in the Flagsmith dashboard. You can customise this by creating a [group](/administration-and-security/access-control/rbac) with the "Add new users by default" option enabled, and assigning your desired default permissions to that group.
 
-### Using groups from your identity provider
+### Using groups from your identity provider {#using-groups-from-your-saml-idp}
 
 Flagsmith can add or remove a user from groups based on your identity provider's SAML response when logging in.
 

docs/docs/deployment-self-hosting/core-configuration/environment-variables.md

@@ -57,4 +57,14 @@ This page provides a comprehensive reference for all the environment variables y
 - `ALBACROSS_CLIENT_ID`: Albacross client ID key for behaviour tracking.
 - `BASE_URL`: Used for specifying a base URL path that's ignored during routing if serving from a subdirectory.
 - `USE_SECURE_COOKIES`: Enable/disable the use of secure cookies. If deploying the frontend in a private network without a domain/SSL cert, disable secure cookies to ensure that session token is persisted. Default: true.
-- `COOKIE_SAME_SITE`: Define the value of the SameSite attribute for the session token cookie set by the frontend. Further reading on this value is available [here](https://web.dev/articles/samesite-cookies-explained). Default: 'none'. 
+- `COOKIE_SAME_SITE`: Define the value of the SameSite attribute for the session token cookie set by the frontend. Further reading on this value is available [here](https://web.dev/articles/samesite-cookies-explained). Default: 'none'.
+
+## OAuth configuration
+
+### Google OAuth {#oauth-google}
+
+To configure Google OAuth, ensure you have set the relevant OAuth client credentials in your deployment platform, and created the **Flagsmith on Flagsmith** flag as described in the [OAuth guide](/administration-and-security/access-control/oauth). This flag controls whether Google SSO is available in your instance.
+
+### GitHub OAuth {#oauth-github}
+
+To configure GitHub OAuth, ensure you have set `GITHUB_CLIENT_ID` and `GITHUB_CLIENT_SECRET` in your environment, and created the **Flagsmith on Flagsmith** flag as described in the [OAuth guide](/administration-and-security/access-control/oauth). This enables the GitHub SSO option in your instance.

docs/docs/deployment-self-hosting/edge-proxy.md

@@ -157,7 +157,7 @@ Optionally, specify the LRU cache size with `cache_max_size`. Defaults to 128.
 
 When set to `true`, the Edge Proxy will use the `X-Forwarded-For` and `X-Forwarded-Proto` HTTP headers to determine
 client IP addresses. This is useful if the Edge Proxy is running behind a reverse proxy, and you want the
-[access logs](#logging.override) to show the real IP addresses of your clients.
+[access logs](#loggingoverride) to show the real IP addresses of your clients.
 
 By default, only the loopback address is trusted. This can be changed with the [`FORWARDED_ALLOW_IPS` environment
 variable](#environment-variables).

docs/docs/flagsmith-concepts/identities.md

@@ -100,6 +100,10 @@ Trait values can be stored as one of four different data types:
 
 If you need to store 64 bit integers or very high precision floats we suggest storing them as strings and then doing the type conversion within the SDK.
 
+## Transient Traits and Identities {#transient-traits}
+
+In some privacy-sensitive cases, you may want to evaluate flags based on traits without persisting those traits in Flagsmith long term. Transient traits and identities let you send data for evaluation while avoiding long-lived storage in the platform. See your SDK documentation for how to mark traits or identities as transient when evaluating flags.
+
 ## Bulk Uploading Identities and Traits
 
 Identities are lazily created within Flagsmith. There might be instances where you want to push identity and trait data into the platform outside of a user session. We have [bulk upload API endpoints](/edge-api/bulk-insert-identities-update) for this.

docs/docs/flagsmith-concepts/segments/index.md

@@ -78,7 +78,7 @@ See [minimum required SDK versions](/flagsmith-concepts/segments/segment-rule-op
 
 In addition to identity [traits](/flagsmith-concepts/identities#identity-traits), you can use the following context values as Segment rule properties. For more information about identities and traits, see the [Identities documentation](/flagsmith-concepts/identities).
 
-- **Identifier**: a unique identifier for an identity, used for segment and multivariate feature flag targeting, and displayed in the Flagsmith UI. Useful for bucketing via the [`% Split`](./segment-rule-operators#percentage-split) operator, or managing a list of users via the [`In`](./segment-rule-operators#in) operator.
+- **Identifier**: a unique identifier for an identity, used for segment and multivariate feature flag targeting, and displayed in the Flagsmith UI. Useful for bucketing via the [`% Split`](./segment-rule-operators?operators=percent#operator-details) operator, or managing a list of users via the [`In`](./segment-rule-operators?operators=in#operator-details) operator.
 - **Identity Key**: a key used when selecting a value for a multivariate feature, or for % split segmentation. Set to an internal identifier or a composite value based on the environment key and identifier, depending on Flagsmith implementation.
 - **Environment Name**: an environment's human-readable name. Useful for restricting Segments to certain environments.
 

docs/docs/integrating-with-flagsmith/integration-overview.md

@@ -49,6 +49,10 @@ For privacy-sensitive use cases, you can use transient traits and identities. Th
 
 Learn more about this feature in our [Transient Traits and Identities documentation](/flagsmith-concepts/identities#transient-traits).
 
+## Local Evaluation Mode {#local-evaluation-mode}
+
+For low-latency, high-throughput back-end use cases, you can run SDKs in Local Evaluation mode or use the [Edge Proxy](/deployment-self-hosting/edge-proxy). In this mode the SDK periodically fetches an environment document and evaluates flags locally without making per-request calls to the Flagsmith API. See the [Server-side SDKs documentation](/integrating-with-flagsmith/sdks/server-side#local-evaluation-mode-network-behaviour) for detailed behaviour and trade-offs.
+
 ## Third-party Integrations
 
 Flagsmith also integrates with a variety of third-party tools for analytics, project management, and more. You can browse all available integrations in the [Integrations section](/third-party-integrations/analytics/segment). 

docs/docs/integrating-with-flagsmith/sdks/index.md

@@ -354,7 +354,7 @@ are all computed locally.
 - Identities and their Traits are **not** read from or written to the Flagsmith API, and so are not persisted in the
   datastore. This means that you have to provide the full complement of Traits when requesting the Flags for a
   particular Identity. Our SDKs all provide relevant methods to achieve this.
-- [Analytics-based Integrations](/third-party-integrations#analytics-platforms) do not run.
+- [Analytics-based Integrations](/third-party-integrations#analytics--data-platforms) do not run.
 -  [Flag Analytics](/managing-flags/flag-analytics) do still work, if enabled within the
    [SDK setup](/integrating-with-flagsmith/sdks/server-side#configuring-the-sdk).
 - **[Edge API](/deployment-self-hosting/edge-proxy) only**: Currently, Flagsmith SDKs support up to ~500 identity overrides, depending on flag value sizes and segment count, when used with

docs/docs/integrating-with-flagsmith/sdks/server-side.mdx

@@ -84,7 +84,7 @@ Server Side SDKs can run in 2 different modes: Local Evaluation and Remote Evalu
 </TabItem>
 </Tabs>
 
-## Add the Flagsmith package
+## Add the Flagsmith package {#python}
 
 <Tabs groupId="language" queryString>
 <TabItem value="python" label="Python">
@@ -117,7 +117,7 @@ pip install flagsmith
 </CodeBlock>
 
 </TabItem>
-<TabItem value="dotnet" label=".NET">
+<TabItem value="dotnet" label=".NET" id="net">
 
 <h3>Package Manager console</h3>
 <CodeBlock>

docs/docs/managing-flags/core-management.md

@@ -88,3 +88,7 @@ Deleting a feature flag is permanent and cannot be undone. Make sure your applic
 ### Permission Issues
 
 - You may need additional permissions to create, edit, clone, or delete feature flags. If you see permission errors or options are disabled, contact your Flagsmith administrator to review your access rights. For more information, see the [Permissions and Roles](/administration-and-security/access-control/rbac) page.
+
+## Remote Config {#remote-config}
+
+Remote Config lets you return a typed value (string, number, boolean or JSON) alongside the on/off state of a feature. You configure Remote Config on the same feature definition, and SDKs read these values when evaluating flags, using the same targeting and rollout rules. This is useful for tweaking behaviour, thresholds, copy or layout without changing code, rather than only enabling or disabling features.

docs/docs/performance/edge-proxy.md

@@ -66,8 +66,8 @@ Please see the [hosting documentation](/deployment-self-hosting/edge-proxy).
 
 The standard Flagsmith architecture:
 
-![Image](/img/edge-proxy-existing.svg)
+![Standard Flagsmith architecture](/img/architecture.svg)
 
 With the proxy added to the mix:
 
-![Image](/img/edge-proxy-proxy.svg)
+![Edge Proxy architecture](/img/edge-api-now.svg)