docs(flutter): Rename Secure Media Access to Token Based File Access

ashfaqcometchat · ashfaqcometchat · commit 2d759b40d4e1 · 2026-02-26T15:02:14.000+05:30
- Update title and sidebarTitle in secure-media-access.mdx
- Rename all references from 'Secure Media Access' to 'Token Based File Access'
- Update URL references from cometchat.com to cometchat.io
- Update overview.mdx, setup.mdx, and send-message.mdx references
- Revert UI Kit changes (will be done in separate branch)
diff --git a/sdk/flutter/overview.mdx b/sdk/flutter/overview.mdx
@@ -108,7 +108,7 @@ The `AppSettings` class allows you to configure three settings:
 * **autoEstablishSocketConnection(boolean value)**: This property takes a boolean value which when set to true informs the SDK to manage the web-socket connection internally. If set to false, it informs the SDK that the web-socket connection will be managed manually. The default value for this parameter is true. For more information on this, please check the [Connection Behaviour](/sdk/flutter/connection-behaviour) section. The default value for this property is **true.**
 * **adminHost(adminHost: string)**: This method takes the admin URL as input and uses this admin URL instead of the default admin URL. This can be used in case of dedicated deployment of CometChat.
 * **clientHost(clientHost: string)**: This method takes the client URL as input and uses this client URL instead of the default client URL. This can be used in case of dedicated deployment of CometChat.
-* **secureMediaMode(SecureMediaMode mode)**: This method sets the secure media access mode for handling media file URLs. See the [Secure Media Access](/sdk/flutter/secure-media-access) guide for details on available modes and configuration.
+* **secureMediaMode(SecureMediaMode mode)**: This method sets the secure media access mode for handling media file URLs. See the [Token Based File Access](/sdk/flutter/secure-media-access) guide for details on available modes and configuration.
 
 <Tabs>
 <Tab title="Dart">
diff --git a/sdk/flutter/secure-media-access.mdx b/sdk/flutter/secure-media-access.mdx
@@ -1,6 +1,6 @@
 ---
-title: "Secure Media Access"
-sidebarTitle: "Secure Media Access"
+title: "Token Based File Access"
+sidebarTitle: "Token Based File Access"
 description: "Control how media files are accessed on CometChat's secure media servers using Embedded, Header-Based, or Presigned token modes."
 ---
 
@@ -27,36 +27,36 @@ await CometChat.init("YOUR_APP_ID", appSettings,
 );
 
 // Fetch a time-limited presigned URL for secure media (Header-Based or Presigned mode)
-String presignedUrl = await CometChat.fetchPresignedUrl("https://files-<region>.cometchat.com/<app_id>/media/file.jpg");
+String presignedUrl = await CometChat.fetchPresignedUrl("https://files-<region>.cometchat.io/<app_id>/media/file.jpg");
 
 // Check if header-based mode is active
 bool isHeaderMode = CometChatHelper.isHeaderModeEnabled();
 
 // Check if a URL requires secure access
-bool needsSecure = CometChatHelper.requiresSecureAccess("https://files-<region>.cometchat.com/<app_id>/media/file.jpg");
+bool needsSecure = CometChatHelper.requiresSecureAccess("https://files-<region>.cometchat.io/<app_id>/media/file.jpg");
 ```
 </Info>
 
-Secure Media Access lets you control how media files (images, videos, audio, documents) are accessed on CometChat's secure media servers. The SDK supports three modes — **Embedded** (FAT appended as a query parameter automatically), **Header-Based** (FAT added in request headers), and **Presigned** (clean URLs where you fetch presigned URLs explicitly). Once Secure Media Access is enabled in the CometChat Dashboard, it cannot be disabled.
+Token Based File Access lets you control how media files (images, videos, audio, documents) are accessed on CometChat's secure media servers. The SDK supports three modes — **Embedded** (FAT appended as a query parameter automatically), **Header-Based** (FAT added in request headers), and **Presigned** (clean URLs where you fetch presigned URLs explicitly). Once Token Based File Access is enabled in the CometChat Dashboard, it cannot be disabled.
 
 <Note>
 **Available via:** SDK | [REST API](https://api-explorer.cometchat.com) | [CometChat Dashboard](https://app.cometchat.com)
 </Note>
 
 <Warning>
-Enabling Secure Media Access is **irreversible**. Once you enable this feature in the CometChat Dashboard, it cannot be disabled. All media URLs will require a valid File Access Token (FAT) for access. Make sure your application is ready to handle secure media URLs before enabling.
+Enabling Token Based File Access is **irreversible**. Once you enable this feature in the CometChat Dashboard, it cannot be disabled. All media URLs will require a valid File Access Token (FAT) for access. Make sure your application is ready to handle secure media URLs before enabling.
 </Warning>
 
 ## Prerequisites
 
-Before using Secure Media Access in your application, ensure the following:
+Before using Token Based File Access in your application, ensure the following:
 
 1. **Enable in Dashboard:** Navigate to your CometChat Dashboard → **Chats** → **Settings** and enable the **Token Based File Access** configuration. This is a one-time setup step that activates token-based media access for your app.
 
 2. **SDK Initialization:** Your application must initialize the CometChat SDK with a valid App ID and region before configuring secure media modes. See [Setup](/sdk/flutter/setup) for details.
 
 <Warning>
-Once Secure Media Access is enabled, all media URLs served by CometChat's secure media servers require a valid **File Access Token (FAT)** for access. Any request to a media URL without a valid FAT will receive a **401 Unauthorized** response. Ensure your application handles secure media URLs before enabling this feature.
+Once Token Based File Access is enabled, all media URLs served by CometChat's secure media servers require a valid **File Access Token (FAT)** for access. Any request to a media URL without a valid FAT will receive a **401 Unauthorized** response. Ensure your application handles secure media URLs before enabling this feature.
 </Warning>
 
 ## Secure Media Modes
@@ -231,7 +231,7 @@ try {
 
 ## How Attachment URLs Differ
 
-When Secure Media Access is enabled, the format of media attachment URLs depends on the configured mode. Understanding this difference is important for rendering media correctly in your application.
+When Token Based File Access is enabled, the format of media attachment URLs depends on the configured mode. Understanding this difference is important for rendering media correctly in your application.
 
 ### Embedded Mode
 
@@ -290,7 +290,7 @@ In **Embedded Mode**, you can use attachment URLs directly from message objects.
 
 ## API Reference
 
-The following static members are available on the `CometChat` class for working with Secure Media Access:
+The following static members are available on the `CometChat` class for working with Token Based File Access:
 
 | Member | Type | Description |
 | --- | --- | --- |
@@ -407,11 +407,11 @@ if (needsSecure) {
 
 ## Error Handling
 
-When working with Secure Media Access, handle these common error scenarios gracefully in your application.
+When working with Token Based File Access, handle these common error scenarios gracefully in your application.
 
 ### Feature Not Enabled
 
-If Secure Media Access is not enabled in the CometChat Dashboard, calling `CometChat.fetchPresignedUrl()` will not throw an error — it simply returns the same URL string that was passed in. Media URLs work normally without a File Access Token in this case.
+If Token Based File Access is not enabled in the CometChat Dashboard, calling `CometChat.fetchPresignedUrl()` will not throw an error — it simply returns the same URL string that was passed in. Media URLs work normally without a File Access Token in this case.
 
 <Tabs>
 <Tab title="Callback">
@@ -594,7 +594,7 @@ loadSecureMedia(mediaUrl);
     **Symptom:** Media files fail to load and the server returns a 401 Unauthorized response.
 
     **Possible causes:**
-    - Secure Media Access is enabled in the Dashboard but the SDK is not configured with a secure media mode.
+    - Token Based File Access is enabled in the Dashboard but the SDK is not configured with a secure media mode.
     - The File Access Token (FAT) has expired or is missing.
     - In Header-Based Mode, you are not including the FAT in request headers.
     - In Presigned Mode, you are using the raw media URL instead of a presigned URL.
diff --git a/sdk/flutter/send-message.mdx b/sdk/flutter/send-message.mdx
@@ -191,7 +191,7 @@ To send a media message to any user or group, you need to use the `sendMediaMess
 
 <Note>
 
-If [Secure Media Access](/sdk/flutter/secure-media-access) is enabled for your app, media URLs returned by the SDK may require token-based access. Depending on the configured mode, the SDK either appends a File Access Token (FAT) automatically, requires you to add the FAT to request headers, or requires you to fetch a presigned URL before rendering media. See the [Secure Media Access](/sdk/flutter/secure-media-access) guide for details.
+If [Token Based File Access](/sdk/flutter/secure-media-access) is enabled for your app, media URLs returned by the SDK may require token-based access. Depending on the configured mode, the SDK either appends a File Access Token (FAT) automatically, requires you to add the FAT to request headers, or requires you to fetch a presigned URL before rendering media. See the [Token Based File Access](/sdk/flutter/secure-media-access) guide for details.
 
 </Note>
 
diff --git a/sdk/flutter/setup.mdx b/sdk/flutter/setup.mdx
@@ -99,7 +99,7 @@ The `AppSettings` class allows you to configure three settings:
 * **autoEstablishSocketConnection(boolean value)**: This property takes a boolean value which when set to true informs the SDK to manage the web-socket connection internally. If set to false, it informs the SDK that the web-socket connection will be managed manually. The default value for this parameter is true. For more information on this, please check the [Connection Behaviour](/sdk/flutter/connection-behaviour) section. The default value for this property is **true.**
 * **adminHost(adminHost: string)**: This method takes the admin URL as input and uses this admin URL instead of the default admin URL. This can be used in case of dedicated deployment of CometChat.
 * **clientHost(clientHost: string)**: This method takes the client URL as input and uses this client URL instead of the default client URL. This can be used in case of dedicated deployment of CometChat.
-* **secureMediaMode(SecureMediaMode mode)**: This method sets the secure media access mode for handling media file URLs. See the [Secure Media Access](/sdk/flutter/secure-media-access) guide for details on available modes and configuration.
+* **secureMediaMode(SecureMediaMode mode)**: This method sets the secure media access mode for handling media file URLs. See the [Token Based File Access](/sdk/flutter/secure-media-access) guide for details on available modes and configuration.
 
 <Tabs>
 <Tab title="Dart">
diff --git a/ui-kit/flutter/core-features.mdx b/ui-kit/flutter/core-features.mdx
@@ -34,10 +34,6 @@ Beyond text, CometChat allows users to share various media types within their co
 | [MessageComposer](/ui-kit/flutter/message-composer) | [MessageComposer](/ui-kit/flutter/message-composer) is a Widget that has ActionSheet, ActionSheet is a menu that appears over the context of the app, providing multiple options for sharing media files.                                                                                                         |
 | [MessageList](/ui-kit/flutter/message-list)         | [MessageList](/ui-kit/flutter/message-list) is a Widget that renders different Media Message bubbles like [Image Bubble](/ui-kit/flutter/message-bubble-styling-styling#image-bubble), [File Bubble](/ui-kit/flutter/message-bubble-styling-styling#file-bubble), [Audio Bubble](/ui-kit/flutter/message-bubble-styling-styling#audio-bubble) [Video Bubble](/ui-kit/flutter/message-bubble-styling#video-bubble) |
 
-<Note>
-For secure media access using presigned URLs, you can enable Header-Based or Presigned mode during initialization. See [Setting Secure Media Mode](/ui-kit/flutter/methods#setting-secure-media-mode) for configuration details.
-</Note>
-
 ## Read Receipts
 
 CometChat's Read Receipts feature provides visibility into the message status, letting users know when a message has been delivered and read. This brings clarity to the communication and ensures users are informed about the status of their messages.
diff --git a/ui-kit/flutter/getting-started.mdx b/ui-kit/flutter/getting-started.mdx
@@ -53,7 +53,7 @@ To get started, create a new flutter application project.
 To use this UI Kit in your Flutter project, you'll need to add the following dependency to the dependencies section of your `pubspec.yaml` file:
 
 ```yaml pubspec.yaml
-  cometchat_chat_uikit: ^5.2.10
+  cometchat_chat_uikit: ^5.2.8
   cometchat_calls_uikit: ^5.0.12 #Optional: Include if you're using Audio/Video Calling
 ```
 
@@ -74,7 +74,7 @@ Final `pubspec.yaml`
     flutter:
       sdk: flutter
 
-    cometchat_chat_uikit: ^5.2.10
+    cometchat_chat_uikit: ^5.2.8
     cometchat_calls_uikit: ^5.0.12 #Optional: Include if you're using Audio/Video Calling
     cupertino_icons: ^1.0.8
 
@@ -170,12 +170,6 @@ Before using any features from the CometChat UI Kit, initialize it with your app
 
    > Store your CometChat credentials in a config file to simplify environment management and avoid hardcoding.
 
-<Note>
-
-You can configure secure media access during initialization using `UIKitSettingsBuilder`. To enable presigned URL-based media access, see [Setting Secure Media Mode](/ui-kit/flutter/methods#setting-secure-media-mode).
-
-</Note>
-
 ***
 
 ### **Step 4: Login to UI Kit**
diff --git a/ui-kit/flutter/methods.mdx b/ui-kit/flutter/methods.mdx
@@ -40,7 +40,6 @@ Here's the table format for the properties available in `UIKitSettings`:
 | **autoEstablishSocketConnection** | `Boolean`                     | Configures if web socket connections will established automatically on app initialization or be done manually, set to true by default |
 | **aiFeature**                     | `List<AIExtensionDataSource>` | Sets the AI Features that need to be added in UI Kit                                                                                  |
 | **extensions**                    | `List<ExtensionsDataSource>`  | Sets the list of extension that need to be added in UI Kit                                                                            |
-| **secureMediaMode**               | `SecureMediaMode`             | Sets the secure media access mode for handling media file URLs. Options: `embedded`, `headerBased`, `presigned`. See [Secure Media Access](/sdk/flutter/secure-media-access) for details. |
 
 ***
 
@@ -70,81 +69,6 @@ CometChatUIKit.init(uiKitSettings: uiKitSettings,onSuccess: (successMessage) asy
 
 ***
 
-### Setting Secure Media Mode
-
-CometChat supports three modes for accessing media files. In **embedded** mode (the default), media URLs include a query-parameter token automatically and no extra steps are needed. In **headerBased** mode, the FAT token is added to request headers for media access. In **presigned** mode, media URLs are resolved via presigned URLs using `CometChat.fetchPresignedUrl(url)`, providing enhanced security for media access.
-
-<Tabs>
-<Tab title="Embedded Mode">
-```dart
-UIKitSettings uiKitSettings = (UIKitSettingsBuilder()
-  ..subscriptionType = CometChatSubscriptionType.allUsers
-  ..autoEstablishSocketConnection = true
-  ..region = "your_region" // Replace with your region
-  ..appId = "your_appID" // Replace with your app Id
-  ..authKey = "your_authKey" // Replace with your app auth key
-  ..secureMediaMode = SecureMediaMode.embedded
-).build();
-
-// Initialize CometChat UI Kit with Embedded Secure Media Mode
-CometChatUIKit.init(uiKitSettings: uiKitSettings, onSuccess: (successMessage) async {
-  debugPrint("Initialization completed successfully with embedded secure media mode");
-  // You can now call login function.
-}, onError: (error) {
-  debugPrint("Initialization failed: ${error.message}");
-});
-```
-</Tab>
-
-<Tab title="Header-Based Mode">
-```dart
-UIKitSettings uiKitSettings = (UIKitSettingsBuilder()
-  ..subscriptionType = CometChatSubscriptionType.allUsers
-  ..autoEstablishSocketConnection = true
-  ..region = "your_region" // Replace with your region
-  ..appId = "your_appID" // Replace with your app Id
-  ..authKey = "your_authKey" // Replace with your app auth key
-  ..secureMediaMode = SecureMediaMode.headerBased
-).build();
-
-// Initialize CometChat UI Kit with Header-Based Secure Media Mode
-CometChatUIKit.init(uiKitSettings: uiKitSettings, onSuccess: (successMessage) async {
-  debugPrint("Initialization completed successfully with header-based secure media mode");
-  // You can now call login function.
-}, onError: (error) {
-  debugPrint("Initialization failed: ${error.message}");
-});
-```
-</Tab>
-
-<Tab title="Presigned Mode">
-```dart
-UIKitSettings uiKitSettings = (UIKitSettingsBuilder()
-  ..subscriptionType = CometChatSubscriptionType.allUsers
-  ..autoEstablishSocketConnection = true
-  ..region = "your_region" // Replace with your region
-  ..appId = "your_appID" // Replace with your app Id
-  ..authKey = "your_authKey" // Replace with your app auth key
-  ..secureMediaMode = SecureMediaMode.presigned
-).build();
-
-// Initialize CometChat UI Kit with Presigned Secure Media Mode
-CometChatUIKit.init(uiKitSettings: uiKitSettings, onSuccess: (successMessage) async {
-  debugPrint("Initialization completed successfully with presigned secure media mode");
-  // You can now call login function.
-}, onError: (error) {
-  debugPrint("Initialization failed: ${error.message}");
-});
-```
-</Tab>
-</Tabs>
-
-<Note>
-For more details on secure media access modes and how to handle media URLs in your application, see the [Secure Media Access](/sdk/flutter/secure-media-access) guide.
-</Note>
-
-***
-
 ### Login using Auth Key
 
 Only the `UID` of a user is needed to log in. This simple authentication procedure is useful when you are creating a POC or if you are in the development phase. For production apps, we suggest you use [AuthToken](#login-using-auth-token) instead of Auth Key.
