diff --git a/docs/troubleshooting/assets/20250430121118024255.png b/docs/troubleshooting/assets/20250430121118024255.png
new file mode 100644
index 00000000..04960e51
Binary files /dev/null and b/docs/troubleshooting/assets/20250430121118024255.png differ
diff --git a/docs/troubleshooting/assets/20250430121118320891.png b/docs/troubleshooting/assets/20250430121118320891.png
new file mode 100644
index 00000000..14281db6
Binary files /dev/null and b/docs/troubleshooting/assets/20250430121118320891.png differ
diff --git a/docs/troubleshooting/assets/20250430121118592064.png b/docs/troubleshooting/assets/20250430121118592064.png
new file mode 100644
index 00000000..88a773fa
Binary files /dev/null and b/docs/troubleshooting/assets/20250430121118592064.png differ
diff --git a/docs/troubleshooting/assets/20250430121203371000.png b/docs/troubleshooting/assets/20250430121203371000.png
new file mode 100644
index 00000000..6b9e7040
Binary files /dev/null and b/docs/troubleshooting/assets/20250430121203371000.png differ
diff --git a/docs/troubleshooting/assets/20250430121203619318.png b/docs/troubleshooting/assets/20250430121203619318.png
new file mode 100644
index 00000000..15c8ebd6
Binary files /dev/null and b/docs/troubleshooting/assets/20250430121203619318.png differ
diff --git a/docs/troubleshooting/assets/20250430121203911156.png b/docs/troubleshooting/assets/20250430121203911156.png
new file mode 100644
index 00000000..2f0c940b
Binary files /dev/null and b/docs/troubleshooting/assets/20250430121203911156.png differ
diff --git a/docs/troubleshooting/assets/20250430121219360101.png b/docs/troubleshooting/assets/20250430121219360101.png
new file mode 100644
index 00000000..d73369c1
Binary files /dev/null and b/docs/troubleshooting/assets/20250430121219360101.png differ
diff --git a/docs/troubleshooting/assets/20250430121219606895.png b/docs/troubleshooting/assets/20250430121219606895.png
new file mode 100644
index 00000000..a64dca48
Binary files /dev/null and b/docs/troubleshooting/assets/20250430121219606895.png differ
diff --git a/docs/troubleshooting/assets/20250430121219871237.png b/docs/troubleshooting/assets/20250430121219871237.png
new file mode 100644
index 00000000..7e5c9903
Binary files /dev/null and b/docs/troubleshooting/assets/20250430121219871237.png differ
diff --git a/docs/troubleshooting/assets/20250430121220084430.png b/docs/troubleshooting/assets/20250430121220084430.png
new file mode 100644
index 00000000..577aee53
Binary files /dev/null and b/docs/troubleshooting/assets/20250430121220084430.png differ
diff --git a/docs/troubleshooting/assets/20250430121220338400.png b/docs/troubleshooting/assets/20250430121220338400.png
new file mode 100644
index 00000000..03fd1157
Binary files /dev/null and b/docs/troubleshooting/assets/20250430121220338400.png differ
diff --git a/docs/troubleshooting/assets/20250430121224235710.png b/docs/troubleshooting/assets/20250430121224235710.png
new file mode 100644
index 00000000..fa8e51ec
Binary files /dev/null and b/docs/troubleshooting/assets/20250430121224235710.png differ
diff --git a/docs/troubleshooting/assets/20250430121224547832.png b/docs/troubleshooting/assets/20250430121224547832.png
new file mode 100644
index 00000000..a5157380
Binary files /dev/null and b/docs/troubleshooting/assets/20250430121224547832.png differ
diff --git a/docs/troubleshooting/assets/20250430121224874215.png b/docs/troubleshooting/assets/20250430121224874215.png
new file mode 100644
index 00000000..df356ebb
Binary files /dev/null and b/docs/troubleshooting/assets/20250430121224874215.png differ
diff --git a/docs/troubleshooting/assets/20250430121304770472.png b/docs/troubleshooting/assets/20250430121304770472.png
new file mode 100644
index 00000000..4bf03f3d
Binary files /dev/null and b/docs/troubleshooting/assets/20250430121304770472.png differ
diff --git a/docs/troubleshooting/assets/20250430121305056379.png b/docs/troubleshooting/assets/20250430121305056379.png
new file mode 100644
index 00000000..c55cb112
Binary files /dev/null and b/docs/troubleshooting/assets/20250430121305056379.png differ
diff --git a/docs/troubleshooting/assets/20250430121305295728.png b/docs/troubleshooting/assets/20250430121305295728.png
new file mode 100644
index 00000000..27770f6c
Binary files /dev/null and b/docs/troubleshooting/assets/20250430121305295728.png differ
diff --git a/docs/troubleshooting/assets/20250430121305526883.png b/docs/troubleshooting/assets/20250430121305526883.png
new file mode 100644
index 00000000..588942db
Binary files /dev/null and b/docs/troubleshooting/assets/20250430121305526883.png differ
diff --git a/docs/troubleshooting/assets/20250430121305771267.png b/docs/troubleshooting/assets/20250430121305771267.png
new file mode 100644
index 00000000..6487fde1
Binary files /dev/null and b/docs/troubleshooting/assets/20250430121305771267.png differ
diff --git a/docs/troubleshooting/assets/20250430121306066982.png b/docs/troubleshooting/assets/20250430121306066982.png
new file mode 100644
index 00000000..64eb91b6
Binary files /dev/null and b/docs/troubleshooting/assets/20250430121306066982.png differ
diff --git a/docs/troubleshooting/assets/20250430121306294908.png b/docs/troubleshooting/assets/20250430121306294908.png
new file mode 100644
index 00000000..cb8b31c7
Binary files /dev/null and b/docs/troubleshooting/assets/20250430121306294908.png differ
diff --git a/docs/troubleshooting/assets/20250430121306553330.png b/docs/troubleshooting/assets/20250430121306553330.png
new file mode 100644
index 00000000..436d248f
Binary files /dev/null and b/docs/troubleshooting/assets/20250430121306553330.png differ
diff --git a/docs/troubleshooting/assets/20250430121306835223.png b/docs/troubleshooting/assets/20250430121306835223.png
new file mode 100644
index 00000000..d6598a5a
Binary files /dev/null and b/docs/troubleshooting/assets/20250430121306835223.png differ
diff --git a/docs/troubleshooting/assets/20250430121309740417.png b/docs/troubleshooting/assets/20250430121309740417.png
new file mode 100644
index 00000000..f2e4ca46
Binary files /dev/null and b/docs/troubleshooting/assets/20250430121309740417.png differ
diff --git a/docs/troubleshooting/assets/20250430121310019673.png b/docs/troubleshooting/assets/20250430121310019673.png
new file mode 100644
index 00000000..838ce613
Binary files /dev/null and b/docs/troubleshooting/assets/20250430121310019673.png differ
diff --git a/docs/troubleshooting/assets/20250430121310317285.png b/docs/troubleshooting/assets/20250430121310317285.png
new file mode 100644
index 00000000..ce14ca2a
Binary files /dev/null and b/docs/troubleshooting/assets/20250430121310317285.png differ
diff --git a/docs/troubleshooting/assets/20250430121310619096.png b/docs/troubleshooting/assets/20250430121310619096.png
new file mode 100644
index 00000000..0ed08202
Binary files /dev/null and b/docs/troubleshooting/assets/20250430121310619096.png differ
diff --git a/docs/troubleshooting/assets/20250430121310959552.png b/docs/troubleshooting/assets/20250430121310959552.png
new file mode 100644
index 00000000..79014d47
Binary files /dev/null and b/docs/troubleshooting/assets/20250430121310959552.png differ
diff --git a/docs/troubleshooting/assets/20250430121357585709.png b/docs/troubleshooting/assets/20250430121357585709.png
new file mode 100644
index 00000000..f68eb3ac
Binary files /dev/null and b/docs/troubleshooting/assets/20250430121357585709.png differ
diff --git a/docs/troubleshooting/assets/20250430121357870887.png b/docs/troubleshooting/assets/20250430121357870887.png
new file mode 100644
index 00000000..df7a333c
Binary files /dev/null and b/docs/troubleshooting/assets/20250430121357870887.png differ
diff --git a/docs/troubleshooting/assets/20250430121507937548.png b/docs/troubleshooting/assets/20250430121507937548.png
new file mode 100644
index 00000000..229fc6a7
Binary files /dev/null and b/docs/troubleshooting/assets/20250430121507937548.png differ
diff --git a/docs/troubleshooting/assets/20250430121508288240.png b/docs/troubleshooting/assets/20250430121508288240.png
new file mode 100644
index 00000000..cf3184da
Binary files /dev/null and b/docs/troubleshooting/assets/20250430121508288240.png differ
diff --git a/docs/troubleshooting/assets/20250430121508604665.png b/docs/troubleshooting/assets/20250430121508604665.png
new file mode 100644
index 00000000..7a17da5a
Binary files /dev/null and b/docs/troubleshooting/assets/20250430121508604665.png differ
diff --git a/docs/troubleshooting/assets/20250430121508962664.png b/docs/troubleshooting/assets/20250430121508962664.png
new file mode 100644
index 00000000..97153aaf
Binary files /dev/null and b/docs/troubleshooting/assets/20250430121508962664.png differ
diff --git a/docs/troubleshooting/assets/20250430121517855306.png b/docs/troubleshooting/assets/20250430121517855306.png
new file mode 100644
index 00000000..77de10ef
Binary files /dev/null and b/docs/troubleshooting/assets/20250430121517855306.png differ
diff --git a/docs/troubleshooting/assets/20250430121518159572.png b/docs/troubleshooting/assets/20250430121518159572.png
new file mode 100644
index 00000000..2740581d
Binary files /dev/null and b/docs/troubleshooting/assets/20250430121518159572.png differ
diff --git a/docs/troubleshooting/assets/20250430121518370897.png b/docs/troubleshooting/assets/20250430121518370897.png
new file mode 100644
index 00000000..42d102d9
Binary files /dev/null and b/docs/troubleshooting/assets/20250430121518370897.png differ
diff --git a/docs/troubleshooting/assets/20250430121518594245.png b/docs/troubleshooting/assets/20250430121518594245.png
new file mode 100644
index 00000000..229fc6a7
Binary files /dev/null and b/docs/troubleshooting/assets/20250430121518594245.png differ
diff --git a/docs/troubleshooting/firebase-issues/_category_.json b/docs/troubleshooting/firebase-issues/_category_.json
new file mode 100644
index 00000000..95967ea0
--- /dev/null
+++ b/docs/troubleshooting/firebase-issues/_category_.json
@@ -0,0 +1,3 @@
+{
+  "label": "Firebase Issues"
+}
\ No newline at end of file
diff --git a/docs/troubleshooting/firebase-issues/content_manager_error_error_updating_firestore_security_rules.md b/docs/troubleshooting/firebase-issues/content_manager_error_error_updating_firestore_security_rules.md
new file mode 100644
index 00000000..3df9f145
--- /dev/null
+++ b/docs/troubleshooting/firebase-issues/content_manager_error_error_updating_firestore_security_rules.md
@@ -0,0 +1,81 @@
+---
+keywords: ['security', 'error', 'firebase', 'permissions']
+slug: /content-manager-error-error-updating-firestore-security-rules
+title: 'Content Manager Error: Error Updating Firestore Security Rules'
+---
+
+# Content Manager Error: Error Updating Firestore Security Rules
+
+## Issue
+This error may appear when attempting to use the FlutterFlow Content Management System (CMS):
+
+```
+Error updating Firestore Security Rules... 
+Make sure you set up Firebase for your project under "Settings" > "Firebase".
+```
+
+
+![](../assets/20250430121517855306.png)
+
+## Why This Error Appears
+This error occurs when Firebase permissions have not been configured correctly. Fortunately, this can be resolved easily by following the steps below:
+
+### Ensure Email Sign-In Is Enabled
+    Open the Firebase console, and click on **Authentication** (in the left side menu).
+
+- Click on the **Get started** button.
+
+- Select the **Sign-in method** tab.
+
+- Check to see if you see Email/Password with that is turned on with a green check **Enabled**:
+
+![](../assets/20250430121518159572.png)
+
+:::note
+If you don't see this, you will need to use these instructions to turn on email sign-in.
+:::
+
+### Ensure Required Cloud Permissions Are Added
+To enable push notifications, the following cloud permissions must be granted to firebase@flutterflow.io:
+
+- Editor
+
+- Cloud Functions Admin
+
+- Service Account
+
+### Steps: 
+- Head to the Firebase Console and open the project dashboard for your project (click the project tile). 
+
+- Select Project Settings > Users & Permissions.
+
+
+:::info
+- If these roles are not listed next to firebase@flutterflow.io, the setup is incomplete.
+- If you don't have Cloud Functions Admin, Editor, and Service Account listed next to firebase@flutterflow.io, you have not completed this step.
+:::
+
+
+
+![](../assets/20250430121518370897.png)
+
+## Instructions on how to add the required cloud permissions to your project.
+
+- ### Update Your Firebase Rules
+
+    From within your FlutterFlow project, select **Firestore** > **Settings** > Scroll down to **Firestore Rules** > select **Deploy/Redploy**.
+
+![](../assets/20250430121518594245.png) 
+
+- ### Ensure Firebase Schema Is Defined
+
+    Ensure you have defined the fields in your Firebase schema. Only fields defined in your Firebase schema are shown in the Firebase Content Manager.
+
+- ### Ensure you are using the latest version of FlutterFlow
+
+    To upgrade to the latest version of FlutterFlow select `Ctrl + R` on Windows or `Cmd + R` on Mac.
+
+After all this is done, clear your browser cache and log out/in to FlutterFlow. If the above wasn't helpful full please make sure you check this Link as well.
+
+## Create Permissions From Scratch
+If all previous steps have been completed and the issue continues, remove existing permissions and complete a fresh setup. Refer to the FlutterFlow documentation for a step-by-step guide.
\ No newline at end of file
diff --git a/docs/troubleshooting/firebase-issues/email_client_access_to_your_cloud_firestore_database_expired.md b/docs/troubleshooting/firebase-issues/email_client_access_to_your_cloud_firestore_database_expired.md
new file mode 100644
index 00000000..24bd3f71
--- /dev/null
+++ b/docs/troubleshooting/firebase-issues/email_client_access_to_your_cloud_firestore_database_expired.md
@@ -0,0 +1,37 @@
+---
+keywords: ['database', 'firebase', 'client']
+slug: /email-client-access-to-your-cloud-firestore-database-expired
+title: 'Email: Client access to your Cloud Firestore database expired'
+---
+# Email: Client access to your Cloud Firestore database expired
+
+## Background
+You've received an email from the Firebase that "Client access to your Cloud Firestore database expired"​
+
+### Why Am I Seeing This Message?
+
+When the user enables the cloud firestore, there are two rules to select in order to get started:  
+
+![](../assets/20250430121224235710.png)
+
+1. Test Mode (Time bounded)
+2. Production Mode (Not Time bounded but secured at the start)
+
+Usually, the user selects the Test Mode and the Firestore works fine, but after the time has been completed the client access get expired. To keep using Firestore user must update the rules by using either of the solutions below.​
+
+
+### Manage the Firestore Rules directly from FlutterFlow
+Head over to this article to see step by steps instructions about how to Manage the Firestore Rules directly from FlutterFlow.
+
+### Manually update the Firestore Rules from Firebase
+In order to keep using Firestore, User should head over to the **Firebase Firestore** section and select **Rules**. Here we can see our previously defined rules, We have **two options** here, any of these options will solve the problem.
+
+- Update the timestamp date to a future date if you still want to keep it in test mode.​
+
+    ![](../assets/20250430121224547832.png)
+
+- Update the rules with some conditions in your database to make it secure.
+
+    ![](../assets/20250430121224874215.png)
+
+After applying this solution, your problem should be resolved, if the problem still persists, feel free to contact us at support@flutterflow.io​
\ No newline at end of file
diff --git a/docs/troubleshooting/firebase-issues/firebase_storage_section_is_missing_from_firebase_settings_tab_in_flutterflow.md b/docs/troubleshooting/firebase-issues/firebase_storage_section_is_missing_from_firebase_settings_tab_in_flutterflow.md
new file mode 100644
index 00000000..dcaca68f
--- /dev/null
+++ b/docs/troubleshooting/firebase-issues/firebase_storage_section_is_missing_from_firebase_settings_tab_in_flutterflow.md
@@ -0,0 +1,36 @@
+---
+keywords: ['storage', 'firebase', 'missing']
+slug: /firebase-storage-section-is-missing-from-firebase-settings-tab-in-flutterflow
+title: Firebase Storage Section is missing from Firebase Settings Tab In FlutterFlow
+---
+# Firebase Storage Section is missing from Firebase Settings Tab In FlutterFlow
+
+## Issue: 
+
+You are trying to set up Firebase Storage in your FlutterFlow Firebase Settings, but you don't see the Firebase Storage Option (example below).
+
+The Firebase Storage tab is not visible because you have not yet set up storage inside the Firebase Console.
+
+![](../assets/20250430121309740417.png)
+
+## Solution 
+
+1. Select **Open Firebase Console** from inside your FlutterFlow project
+
+![](../assets/20250430121310019673.png)
+
+2. In the build menu in your Firebase project, click on **Storage**
+
+![](../assets/20250430121310317285.png)
+
+3. Click **Get Started** and complete storage setup.
+
+![](../assets/20250430121310619096.png)
+
+After you successfully created your storage bucket, you can go to the FlutterFlow project and see the rules option.
+
+:::note
+After creating Storage it may take up to an hour for this to reflect in your FlutterFlow project.
+:::
+
+![](../assets/20250430121310959552.png)
\ No newline at end of file
diff --git a/docs/troubleshooting/firebase-issues/get_the_sum_of_firebase_document_or_api_values.md b/docs/troubleshooting/firebase-issues/get_the_sum_of_firebase_document_or_api_values.md
new file mode 100644
index 00000000..e9bf4921
--- /dev/null
+++ b/docs/troubleshooting/firebase-issues/get_the_sum_of_firebase_document_or_api_values.md
@@ -0,0 +1,43 @@
+---
+keywords: ['firebase', 'api', 'document']
+slug: /get-the-sum-of-firebase-document-or-api-values
+title: Get the Sum of Firebase Document or API Values
+---
+# Get the Sum of Firebase Document or API Values
+
+Sometimes, when working with databases, you might need to calculate the total of all values for a certain item or category. This is especially common when using APIs or working with Firebase. If you're looking to add up values from a database, this easy-to-follow guide is for you. 
+
+## Steps to Get the Sum of Firebase Document or API Values
+
+Follow this simple steps below:
+
+
+### Step 1: Identify Where You Need the Total
+
+First, decide where in your code you need to display the total sum. This could be a text field or a variable in your code where the final sum will be shown.
+
+![](../assets/20250430121219360101.png)
+
+### Step 2: Prepare Your Data Type
+
+Next, you need to specify what kind of data you're adding up. For example, if you're working with numbers with decimal points, you'll classify your data as `double`. Make sure to indicate that you're dealing with a list of these values.
+
+![](../assets/20250430121219606895.png)
+
+### Step 3: Select Your Data
+
+Now, choose the specific data you want to sum up. You do this by picking out the documents from your database query and then mapping out the exact data field you're interested in.
+
+![](../assets/20250430121219871237.png)
+
+### Step 4: Calculate the Sum
+
+With your list of values ready, store them in a variable (let's call it `var1`). Then, decide on the format you want for your result. Use the `reduce` function to add up all the values in your list, `var1`, to get your total sum.
+
+![](../assets/20250430121220084430.png)
+
+### Step 5: Checking Your Results
+
+After completing these steps, you should have the total sum displayed where you need it. If it looks right, you've successfully calculated the sum!
+
+![](../assets/20250430121220338400.png)
diff --git a/docs/troubleshooting/firebase-issues/how_to_configure_cors_in_firebase_storage.md b/docs/troubleshooting/firebase-issues/how_to_configure_cors_in_firebase_storage.md
new file mode 100644
index 00000000..3a1294be
--- /dev/null
+++ b/docs/troubleshooting/firebase-issues/how_to_configure_cors_in_firebase_storage.md
@@ -0,0 +1,68 @@
+---
+keywords: ['storage', 'firebase', 'cors']
+slug: /how-to-configure-cors-in-firebase-storage
+title: How to Configure CORS in Firebase Storage
+---
+# How to Configure CORS in Firebase Storage
+
+When you deploy your web app to a custom domain, the domain and the Firebase Storage bucket are hosted on different servers. This means that the browser will block requests to the Firebase Storage bucket from your web app, because the origins (the domains and ports) of the two servers are different.
+
+## What is CORS?
+
+CORS stands for **Cross-Origin Resource Sharing**. It allows you to specify which origins are allowed to access your resources. By configuring CORS, you can tell the browser that your web app is allowed to make requests to the Firebase Storage bucket, even though the two servers are hosted on different domains.
+
+## How to configure CORS in Firebase Storage
+
+In Firebase Storage, you can configure CORS by creating a `cors.json` file in your bucket. This file contains a list of origins that are allowed to access your resources.
+
+To create a `cors.json` file, follow these steps:
+
+- Go to the Google Cloud Console: https://console.cloud.google.com​
+    ![](../assets/20250430121203371000.png)
+
+- In the top right corner of the console, click the **Activate Cloud Shell** button and you will see a terminal window inside your current window​
+
+    ![](../assets/20250430121203619318.png)
+
+    ![](../assets/20250430121203911156.png)
+​
+
+- Run the following command:
+
+```
+gcloud config set project <your-project-id>
+```
+
+- Navigate to your Firebase Storage bucket:
+
+```
+cd gs://<your-bucket-name>
+```
+
+- Run the `cors` command to configure CORS:
+
+```
+gsutil cors set cors.json gs://<your-bucket-name>
+```
+
+You can also specify a list of allowed headers by running the following command:
+
+```
+gsutil cors set cors.json gs://<your-bucket-name> --allowed-headers="Content-Type, Authorization"
+```
+
+The `cors.json` file contains a list of origins that are allowed to access your resources. Each origin is a string that identifies a domain or port. For example, the following origin allows access from the domain `www.example.com`:
+
+```
+"origins": ["https://www.example.com"]
+```
+
+You can also specify a list of allowed headers. The following example allows access to the `Content-Type` and `Authorization` headers:
+
+```
+"origins": ["https://www.example.com"], "allowedHeaders": ["Content-Type", "Authorization"]
+```
+
+For more information on configuring CORS in Firebase Storage, please see the [official documentation](https://firebase.google.com/docs/storage/web/download-files#cors_configuration).
+
+
diff --git a/docs/troubleshooting/firebase-issues/how_to_update_firestore_rules.md b/docs/troubleshooting/firebase-issues/how_to_update_firestore_rules.md
new file mode 100644
index 00000000..15ca782b
--- /dev/null
+++ b/docs/troubleshooting/firebase-issues/how_to_update_firestore_rules.md
@@ -0,0 +1,36 @@
+---
+keywords: ['rules', 'firestore', 'update']
+slug: /how-to-update-firestore-rules
+title: How to update Firestore rules?
+---
+# How to update Firestore rules?
+
+Most backend issues are generated by the misconfiguration of the Firestore Security Rules. These backed issues may include Grey Screen errors, Infinite Loading screen, Firestore record creating error, Data mismatch errors, etc.
+
+And to solve these issues, the Firestore rules have to be updated, for which you can follow the given series of steps:
+
+- Update Your Firestore Rules
+
+    From within your FlutterFlow project, select **Firestore** > **Settings** > Scroll down to **Firestore Rules** > select **Deploy**/**Redploy**.
+
+    ![](../assets/20250430121507937548.png)
+
+- Update Firestore Indexes
+
+    The next step is to see if the Firestore Rules and Indexes are **Out of Date** or **Not Deployed** (as shown in the image below). If yes, click on the blue **Deploy** button to push the latest rules. 
+
+    ![](../assets/20250430121508288240.png)
+
+- After clicking on the **Deploy** button, a confirmation dialog would be shown, highlighting the changes in the rules that are being made from the deployment. 
+
+    This compares the existing rules in Firestore and highlights what changes are being made in the Firestore rules. These changes are required when a new collection is created or is been edited or if the rules are Out of Date.
+
+    ![](../assets/20250430121508604665.png)
+
+You can review the changes, and then you can click on the **Deploy Now** button. An orange loading indicator would be shown, which means that the rules are getting deployed (This step usually finishes within less than a minute, and the loading indicator is replaced with a Green Checkbox button).
+
+- Validate the Firestore Schema
+
+    After completing this step, validate the Firestore schema by clicking on the blue **Validate** button. This ensures that everything is configured correctly and the Firestore collection schema matches with the Collection schema configured in FlutterFlow.
+
+    ![](../assets/20250430121508962664.png)
\ No newline at end of file
diff --git a/docs/troubleshooting/firebase-issues/unable_to_validate_firestore_schema_unable_to_load_data_from_collection_missing_or_insufficient_permissions.md b/docs/troubleshooting/firebase-issues/unable_to_validate_firestore_schema_unable_to_load_data_from_collection_missing_or_insufficient_permissions.md
new file mode 100644
index 00000000..a96ba20e
--- /dev/null
+++ b/docs/troubleshooting/firebase-issues/unable_to_validate_firestore_schema_unable_to_load_data_from_collection_missing_or_insufficient_permissions.md
@@ -0,0 +1,86 @@
+---
+keywords: ['permissions', 'database', 'firebase']
+slug: /unable-to-validate-firestore-schema-unable-to-load-data-from-collection-missing-or-insufficient-permissions
+title: 'Unable to validate Firestore Schema: Unable to load data from collection.
+  Missing or insufficient permissions'
+---
+
+# Unable to validate Firestore Schema: Unable to load data from collection. Missing or insufficient permissions
+
+## Issue: 
+
+You see an error like this when trying to validate your Firestore Schema:
+
+Unable to load data from collection. 
+Error: [cloud_firestore/permission-denied] Missing or insufficient permissions.​
+
+![](../assets/20250430121304770472.png)
+
+
+## Troubleshooting Steps:
+
+## 1. Make sure you already created a database in firebase**
+
+  ![](../assets/20250430121305056379.png)
+
+## 2. Make sure your database is not on TEST MODE.
+
+  A Database in Test Mode may not work properly
+
+:::note 
+After creating the database in test mode, there is no visual option to switch to production mode directly. Instead, the Firebase rules must be updated manually. However, if the rules are deployed from FlutterFlow, this transition is handled automatically, and the manual update can be skipped.
+::: 
+
+### Steps to change your database from test mode to production mode:
+
+1. Go to your firebase project.
+2. Select Cloud Firestore.
+3. Select Rules.
+
+You will see something like below.​
+
+![](../assets/20250430121305295728.png)
+
+Change it as follows, 
+
+:::note 
+Be sure to specify the correct rules_version and verify that it is accurately reflected in your configuration.
+::: 
+
+![](../assets/20250430121305526883.png)
+
+4) Publish.
+
+The configuration is now successfully switched to Production mode.
+
+Make sure you give the necessary permissions to firebase@flutterflow.io editor account in your firebase project
+
+You will need to add the following cloud permissions for firebase@flutterflow.io: 
+**Editor**, **Cloud Functions Admin**, and **Service Account**.
+
+Head to the Firebase Console and open the project dashboard for your project (click the project tile). Select **Project Settings** > **Users** & **Permissions**.
+
+If you don't have Cloud Functions Admin, Editor, and Service Account listed next to firebase@flutterflow.io as seen in the image below, you have not completed this step.
+
+![](../assets/20250430121305771267.png)
+
+
+## 3. Make sure you at least one collection created in FlutterFlow
+
+Select the Firestore tab from the left menu. If you have no collections listed, you will need to create one.
+
+![](../assets/20250430121306066982.png)
+
+## 4. Make sure that at least one of your collections has at least one document.
+
+You can use the CMS in FlutterFlow to confirm that you have at least one document. Select Manage Content and view your collections.
+
+If you don't see any data listed, you will need to add data using the CMS.
+
+![](../assets/20250430121306294908.png)![](../assets/20250430121306553330.png)
+
+## 5. Make sure you deployed your database rules with the proper permissions
+
+From within your FlutterFlow project, select **Firestore** > **Settings** > Scroll down to Firestore Rules > select **Deploy**/**Redploy**.
+
+![](../assets/20250430121306835223.png)
diff --git a/docs/troubleshooting/firebase-issues/understanding_firebase_storage_limits_in_flutterflow.md b/docs/troubleshooting/firebase-issues/understanding_firebase_storage_limits_in_flutterflow.md
new file mode 100644
index 00000000..f4981005
--- /dev/null
+++ b/docs/troubleshooting/firebase-issues/understanding_firebase_storage_limits_in_flutterflow.md
@@ -0,0 +1,56 @@
+---
+keywords: ['storage', 'firebase', 'flutterflow']
+slug: /understanding-firebase-storage-limits-in-flutterflow
+title: Understanding Firebase Storage Limits in FlutterFlow
+---
+
+# Understanding Firebase Storage Limits in FlutterFlow
+
+Understanding the limits of **Firebase Storage** is essential for managing your app's files and costs in FlutterFlow. This guide summarizes the key points and best practices.
+
+
+## 1. Firebase Storage Plans & Limits
+
+### 🔹 Spark Plan (Free)
+- Up to **5 GB** of storage at no cost.
+- Once you reach this limit, you must upgrade to continue storing files.
+
+### 🔹 Blaze Plan (Pay-as-you-go)
+- Charges are based on the amount of storage used.
+- The price per TB decreases as your usage increases.
+- For the latest details, always check the [Firebase Pricing page](https://firebase.google.com/pricing).
+
+
+## 2. Firebase Operations Limit
+
+- Firebase also limits the **number of operations** (uploads, downloads, deletes) per day, especially on the Spark plan.
+- Plan your app's functionality and user experience with these limits in mind.
+
+
+## 3. Managing Firebase Storage Wisely
+
+:::tip
+Proactive management helps avoid unexpected costs and storage issues.
+:::
+
+Here's how to manage Firebase storage:
+
+- **Delete unneeded files** regularly.
+- **Compress files** (especially images and videos) before uploading.
+- **Monitor** your storage usage in the Firebase Console.
+- For apps with high data volume or large files, set up automated cleanup routines if possible.
+
+## 4. Additional Resources
+
+- [Firebase Pricing](https://firebase.google.com/pricing)
+- [Firebase Storage Documentation](https://firebase.google.com/docs/storage)
+- [FlutterFlow Docs: Storage](https://docs.flutterflow.io/storage)
+
+## Summary:
+- Know your plan's limits.
+- Monitor usage and operations.
+- Clean up and compress files to save space and costs.
+
+Stay informed and manage your storage to keep your FlutterFlow app running smoothly!
+
+
diff --git a/docs/troubleshooting/firebase-issues/warning_firebase_android_configuration_file_has_not_been_uploaded.md b/docs/troubleshooting/firebase-issues/warning_firebase_android_configuration_file_has_not_been_uploaded.md
new file mode 100644
index 00000000..f6d6a73a
--- /dev/null
+++ b/docs/troubleshooting/firebase-issues/warning_firebase_android_configuration_file_has_not_been_uploaded.md
@@ -0,0 +1,28 @@
+---
+keywords: ['firebase', 'android', 'configuration']
+author: Unknown
+slug: /warning-firebase-android-configuration-file-has-not-been-uploaded
+title: 'Warning: Firebase Android Configuration File Has Not Been Uploaded'
+---
+
+# Warning: Firebase Android Configuration File Has Not Been Uploaded
+
+While working with Firebase, you may come across the error "Warning: Firebase Android configuration file has not been uploaded! Tap to fix." In most cases, this happens when your Firebase configuration files have not been generated.
+
+This issue can be resolved with a few simple steps:
+
+![](../assets/20250430121357585709.png)
+
+## Solution
+
+1. Ensure that you have completely set up Firebase for your project
+
+    For detailed instructions on setting up Firebase, please refer to the [official Firebase documentation](https://firebase.google.com/docs).
+
+2. Open your **Project Settings**, navigate to **Firebase** 
+
+    ![](../assets/20250430121357870887.png)
+
+3. Regenerate you Firebase configuration files 
+
+    If you are still having problems, feel free to contact support@flutterflow.io
\ No newline at end of file
diff --git a/docs/troubleshooting/firebase-issues/what_to_do if_firestore_indexes_are_not_deployed.md b/docs/troubleshooting/firebase-issues/what_to_do if_firestore_indexes_are_not_deployed.md
new file mode 100644
index 00000000..fa900ef2
--- /dev/null
+++ b/docs/troubleshooting/firebase-issues/what_to_do if_firestore_indexes_are_not_deployed.md	
@@ -0,0 +1,65 @@
+---
+keywords: ['firebase', 'deployed', 'firestore']
+slug: /what-to-do-if-firestore-indexes-are-not-deployed
+title: What To Do If Firestore Indexes Are Not Deployed
+---
+# What To Do If Firestore Indexes Are Not Deployed
+
+Properly deployed Firestore indexes are essential for your app's performance and functionality. If your Firebase indexes are not being deployed, follow this clear, step-by-step troubleshooting guide.
+
+---
+
+## 1. Problem Overview
+
+- Issue: Firestore indexes are not being deployed as expected.
+- Expected Outcome:** Indexes should be successfully deployed to Firebase for optimal app performance.
+
+![](../assets/20250430121118024255.png)
+
+
+## 2. Troubleshooting Steps
+
+### 🔹 Step 1: Enable Email Sign-In
+- Go to your Firebase project's **Authentication** section.
+- Ensure the **Email/Password** sign-in method is enabled.
+- **Reference:** [FlutterFlow Email Sign-In Docs](https://docs.flutterflow.io/data-and-backend/firebase/authentication/email-sign-in)
+
+### 🔹 Step 2: Grant Proper Permissions
+- Add **firebase@flutterflow.io** as a member of your Firebase project.
+- Assign the necessary permissions to manage and deploy Firestore indexes.
+- **Reference:** [Firestore Rules & Permissions Guide](https://docs.flutterflow.io/data-and-backend/firebase/firestore-database-cloud-firestore/firestore-rules)
+
+![](../assets/20250430121118320891.png)
+
+### 🔹 Step 3: Update Firebase Rules
+- Review and update your Firestore security rules in both the Firebase console and FlutterFlow.
+- Make sure the rules are correctly set up for your app's needs.
+- **Reference:** [Firestore Rules Documentation](https://docs.flutterflow.io/data-and-backend/firebase/firestore-database-cloud-firestore/firestore-rules)
+
+
+### 🔹 Step 4: Verify Index Deployment
+- In the Firebase console, check the **Indexes** section to confirm deployment.
+    :::note
+    Deployment may take a few minutes. Refresh the console if needed.
+    :::
+
+![](../assets/20250430121118592064.png)
+
+---
+
+## Additional Tips
+
+- Double-check that all steps above are completed before retrying deployment.
+- If issues persist, consult the [official FlutterFlow support article](https://intercom.help/flutterflow/en/articles/9127351-what-to-do-if-firestore-indexes-are-not-deployed).
+- For advanced troubleshooting, review Firebase logs and permissions in the Google Cloud Console.
+
+---
+
+Summary:
+- Enable Email Sign-In
+- Grant permissions to firebase@flutterflow.io
+- Update Firestore rules
+- Verify index deployment in the Firebase console
+
+Following these steps should resolve most issues with Firestore index deployment in FlutterFlow.
+