diff --git a/reporting-analytics/analytics.mdx b/reporting-analytics/analytics.mdx
index f7e1b16..d14300d 100644
--- a/reporting-analytics/analytics.mdx
+++ b/reporting-analytics/analytics.mdx
@@ -15,7 +15,7 @@ In addition to OpenOps tables, OpenOps Analytics can connect to and visualize yo
 
 To configure data visualizations, click **Analytics** on the main navigation bar in OpenOps. When the **Analytics** view opens, click **Admin Panel** to proceed to the Analytics admin portal that is separate from the main OpenOps application.
 
-To sign in to the Analytics portal, use `admin` as the username and the password defined with the `OPS_ANALYTICS_ADMIN_PASSWORD` variable in the `.env` file in your OpenOps installation folder. (If you haven’t changed the password, the default is `please-change-this-password-1`.)
+To sign in to the Analytics portal, use `admin` as the username and the password defined with the `OPS_ANALYTICS_ADMIN_PASSWORD` variable in the `.env` file in your OpenOps installation folder. (If you haven't changed the password, the default is `please-change-this-password-1`.)
 
 <Note>
 If you don't have access to the OpenOps installation folder:
@@ -31,6 +31,18 @@ Behind every OpenOps table, there is a Postgres database view that can be used t
 
 When a new table is created in [OpenOps tables](/reporting-analytics/tables/), the system automatically creates a new database view with the naming convention _table name \_ table id \_ userfriendly_. You can use this view to create dashboards in OpenOps, as well as connect it to other BI systems.
 
+## Running OpenOps without Analytics
+
+OpenOps can run without the Analytics service.
+
+If `OPS_ANALYTICS_PRIVATE_URL` is not set, OpenOps skips Analytics seeding.
+
+## Demo dashboard seeding
+
+OpenOps can seed a demo dashboard named **Homepage** in the analytics portal.
+
+This seeding runs only when the `SHOW_DEMO_HOME_PAGE` flag is set. When the flag is not set, OpenOps skips seeding the demo dashboard.
+
 ## Building new charts
 
 To configure a new chart based on an OpenOps table to display in the **Analytics** view in OpenOps, do the following:
@@ -59,7 +71,7 @@ Here's what you can do to connect OpenOps Analytics to external data sources suc
 1. In the Analytics admin portal, in the top right corner, click **Settings**, then **Database Connections**.
     <NarrowImage src="/images/analytics-external-menu.png" alt="Database connections settings" widthPercent={40} />
 2. Click **+ Database** to connect to an external data source, such as your own Postgres instance or Google Sheets.
-3. Once you have created a database connection, if you’d like to upload CSVs to it, click the **Edit** icon for the database connection:
+3. Once you have created a database connection, if you'd like to upload CSVs to it, click the **Edit** icon for the database connection:
     ![Editing a database connection](/images/analytics-edit-db-connection.png)
 4. In the popup that displays, go to **Advanced > Security**, scroll down, and enable **Allow file uploads to database**.
     <NarrowImage src="/images/analytics-database-allow-file-uploads.png" alt="Allowing file uploads" widthPercent={60} />
diff --git a/reporting-analytics/tables.mdx b/reporting-analytics/tables.mdx
index b0ddd09..55f73e7 100644
--- a/reporting-analytics/tables.mdx
+++ b/reporting-analytics/tables.mdx
@@ -58,6 +58,16 @@ To better understand how the two tables described above are used in real-life wo
     * **Dismissed** if the owner has chosen to dismiss the opportunity.
     * **Snoozed** if the owner has chosen to consider the opportunity later. The number of days to delay is reflected in the **Snoozed until** field.
 
+## Multiple workspaces, databases, and tokens
+
+OpenOps Tables setup expects a single workspace, database, and database token for the Tables admin user:
+
+* If the Tables admin user has more than one workspace, OpenOps throws an error.
+* If the workspace has more than one database, OpenOps throws an error.
+* If the workspace has more than one database token, OpenOps throws an error.
+
+This constraint exists because OpenOps uses that workspace, database, and token for creating and accessing the default OpenOps Tables database.
+
 ## Creating new tables
 
 In addition to preconfigured tables, you can create your own. This is especially useful when you're developing original workflows that are not based on OpenOps templates and you want to set up a visual way to save data generated by the workflows.