mongodb
diff --git a/‎conf.py‎
Lines changed: 3 additions & 0 deletions b/‎conf.py‎
Lines changed: 3 additions & 0 deletions
diff --git a/‎config/sphinx_local.yaml‎
Lines changed: 2 additions & 0 deletions b/‎config/sphinx_local.yaml‎
Lines changed: 2 additions & 0 deletions
diff --git a/‎source/admin-settings.txt‎
Lines changed: 31 additions & 8 deletions b/‎source/admin-settings.txt‎
Lines changed: 31 additions & 8 deletions
diff --git a/‎source/build-charts.txt‎
Lines changed: 2 additions & 0 deletions b/‎source/build-charts.txt‎
Lines changed: 2 additions & 0 deletions
diff --git a/‎source/configure-auth-providers.txt‎
Lines changed: 96 additions & 0 deletions b/‎source/configure-auth-providers.txt‎
Lines changed: 96 additions & 0 deletions
diff --git a/‎source/dashboard-permissions.txt‎
Lines changed: 2 additions & 2 deletions b/‎source/dashboard-permissions.txt‎
Lines changed: 2 additions & 2 deletions
diff --git a/‎source/dashboards.txt‎
Lines changed: 58 additions & 46 deletions b/‎source/dashboards.txt‎
Lines changed: 58 additions & 46 deletions
@@ -66,6 +66,9 @@
     '.. |aws| replace:: :abbr:`AWS (Amazon Web Services)`',
     '.. |gcp| replace:: :abbr:`GCP (Google Cloud Platform)`',
     '.. |html| replace:: :abbr:`HTML (HyperText Markup Language)`',
+    '.. |jwt| replace:: :abbr:`JWT (JSON Web Token)`',
+    '.. |cloud-svc| replace:: :abbr:`Cloud`',
+    '.. |css| replace:: :abbr:`CSS (Cascading Style Sheets)`',
 ]
 
 rst_epilog.extend(get_replacements(conf))
 
@@ -29,6 +29,8 @@ theme:
      - /customize-charts
      - /embedding-charts
      - /view-export-chart-data
+     - /embedding-tutorials
+
 sidebars:
   '**':
     - 'pagenav.html'
 
@@ -11,20 +11,20 @@ Admin Settings
 .. contents:: On this page
    :local:
    :backlinks: none
-   :depth: 1
+   :depth: 2
    :class: singlecol
 
 To access the :guilabel:`Admin Settings` page, you must be an |service|
 :atlas:`Project Owner </reference/user-roles/#project-roles>`.
 If you have the ``Project Owner`` role, the :guilabel:`Admin Settings`
-link appears in the top right corner of the Charts UI.
+link appears in the sidebar of the Charts UI.
 
 .. _admin-usage:
 
-Usage
------
+Monthly Data Usage
+------------------
 
-The :guilabel:`Usage` panel of the :guilabel:`Admin Settings` shows
+The :guilabel:`Usage` panel of the :guilabel:`Admin Settings` page shows
 the data usage of your |charts| instance over the current month.
 
 The panel displays the following metrics:
@@ -55,12 +55,35 @@ all |charts-short| use cases should fall within this ``1 GB`` free
 tier. For more information on |charts| pricing and sample pricing
 scenarios, see :ref:`charts-billing`.
 
+.. _embedding-auth-providers:
+
+Embedding Authentication Providers
+----------------------------------
+
+The :guilabel:`Embedding Authentication Providers` panel lists the 
+providers |charts-short| can use to authenticate users who access 
+embedded charts.
+
+|charts-short| requires a token from one of the providers you configure
+to render authenticated charts embedded with the SDK.
+
+For more information about embedding authentication providers, see 
+:doc:`/configure-auth-providers`.
+
 Embedding Key Generation
 ------------------------
 
-Embedding keys are necessary for verified signature generation, and are
-used in conjunction with :doc:`embedded charts <embedding-charts>`. To
-generate a new embedding key, click the :guilabel:`Generate New Key`
+.. important::
+
+   Embedding keys are deprecated and will be removed in a future 
+   release. Use :doc:`Embedding Authentication Providers 
+   </configure-auth-providers>` and the :doc:`Embedding SDK 
+   </embedding-charts-sdk>` instead.
+
+Embedding keys are necessary for generating and verifying digital 
+signatures of charts embedded using the Verified Signature mode. 
+
+To generate a new embedding key, click the :guilabel:`Generate New Key`
 button on the right side of the page.
 
 .. warning::
 
@@ -16,6 +16,8 @@ add a :doc:`data source </data-sources>` and create a :doc:`dashboard
 For a complete list of available chart types and how to build specific
 charts, refer to the :ref:`Chart Types <chart-type-reference>` page.
 
+.. _create-new-chart:
+
 Create a Chart
 --------------
 
 
@@ -0,0 +1,96 @@
+.. _configure-auth-providers:
+
+============================================
+Configure Embedding Authentication Providers
+============================================
+
+.. default-domain:: mongodb
+
+.. contents:: On this page
+   :local:
+   :backlinks: none
+   :depth: 2
+   :class: singlecol
+
+|charts| uses tokens passed with the Embedding SDK to authenticate users
+who want to view authenticated embedded charts. If the details in the 
+token do not match criteria you specify, if the token is invalid, 
+or if a token is not present, |charts-short| doesn't render the chart.
+
+Considerations
+--------------
+- You must be an |service|
+  :atlas:`Project Owner </reference/user-roles/#project-roles>` to
+  configure embedding authentication providers for your linked 
+  |charts-short| instance.
+
+- |charts-short| supports these authentication providers:
+
+  - :stitch:`Realm </authentication/>`
+  - Google
+  - Custom |jwt|
+
+Realm Providers
+~~~~~~~~~~~~~~~
+
+|charts-short| considers tokens from Realm providers valid if they:
+
+- Are syntactically valid |jwt|\s.
+
+- Are issued by the relevant authority.
+
+- Match the Realm App ID you configure the provider to accept.
+
+Google Providers
+~~~~~~~~~~~~~~~~
+
+|charts-short| considers tokens from Google providers valid if they:
+
+- Are syntactically valid |jwt|\s.
+
+- Are issued by the relevant authority.
+
+- Match the Google Client ID you configure the provider to accept.
+
+JWT Providers
+~~~~~~~~~~~~~
+
+.. include:: /includes/jwt-provider-valid-token.rst
+
+Procedures
+----------
+
+View Authentication Providers
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+To view the embedding authentication providers you have configured:
+
+.. include:: /includes/steps/view-auth-providers.rst
+
+.. _add-auth-provider-steps:
+
+Add an Authentication Provider
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+To add an embedding authentication provider:
+
+.. include:: /includes/steps/add-auth-providers.rst
+
+Modify an Authentication Provider
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+To modify an embedding authentication provider:
+
+.. include:: /includes/steps/edit-auth-providers.rst
+
+Delete an Authentication Provider
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+To delete an embedding authentication provider:
+
+.. include:: /includes/steps/delete-auth-providers.rst
+
+.. important::
+
+   After you delete a provider, all embedded charts that the deleted 
+   provider authenticated no longer render.
@@ -70,7 +70,7 @@ To view a chart on a dashboard, the user must have both:
    :class: note
 
    You can have no permissions on a dashboard. That dashboard won't
-   appear on your :ref:`dashboards tab <dashboards-tab>`. Newly-created
+   appear on your :ref:`dashboards page <dashboards-tab>`. Newly-created
    dashboards aren't shared by default. Only the dashboard ``Owner``
    can view the dashboard until they grant access to more users.
 
@@ -120,7 +120,7 @@ Modify Dashboard Permissions
 
 To modify dashboard permissions, either click the click the
 :ref:`permission icon <dashboard-permission-icons>` at the top-right of
-the dashboard from the :guilabel:`Dashboards` tab:
+the dashboard from the :guilabel:`Dashboards` page:
 
 .. figure:: /images/charts/dashboard-permission-icon.png
    :figwidth: 750px
 
@@ -19,11 +19,12 @@ attain insight into multiple focal points of your data in a single
 display. Dashboards can be shared with other users.
 
 .. _dashboards-tab:
+.. _dashboards-page:
 
-Dashboards Tab
---------------
+Dashboards Page
+---------------
 
-The :guilabel:`Dashboards` tab shows all dashboards you have access to
+The :guilabel:`Dashboards` page shows all dashboards you have access to
 view. To learn more about dashboard permissions in |charts|, see
 :ref:`Dashboard Permissions <dashboard-permissions>`.
 
@@ -46,12 +47,14 @@ By default, the most recently modified dashboards are shown first in
 the list. You can change the sort order by using the
 :guilabel:`Sort By` dropdown menu.
 
+.. _create-new-dashboard:
+
 Create a New Dashboard
 ----------------------
 
 To create a new dashboard:
 
-1. From the :guilabel:`Dashboards` tab, click the
+1. From the :guilabel:`Dashboards` page, click the
    :guilabel:`New Dashboard` button.
 
 #. In the :guilabel:`New Dashboard` dialog, enter a title for your
@@ -74,62 +77,72 @@ add the first chart to your dashboard:
 Refresh Dashboard Data
 ----------------------
 
-You can refresh dashboard data to update all charts on the dashboard
-with the most current data from their respective data sources. When
-|charts| loads charts on a dashboard, it does not consistently query
-the data source for each chart. Instead, |charts| queries the data
-source when the dashboard first loads, and that data
-is stored in the browser cache and used to render the charts.
-
-|charts| provides options to both manually refresh dashboard data and
-configure the dashboard to automatically refresh at a specified time
-interval.  These options allow you to control how current the data
-displayed on your dashboard is. By default, when you first create a
-dashboard, it is configured to refresh its data every hour. The
-:guilabel:`Auto` text next to the :icon:`sync-alt` icon signifies that
-auto refresh is enabled.
-
-Manually Refresh Dashboard Data
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-To manually refresh dashboard data, first select a dashboard from the
-:guilabel:`Dashboards` tab, then click the :icon:`sync-alt` button at
-the top-right of the dashboard.
+|charts| automatically refreshes chart data once it becomes out of
+date with the backing data source. You can also manually refresh dashboard data at any time.
 
 .. _configure-auto-refresh:
 
 Configure Auto Refresh Settings
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-You can configure auto refresh settings to change the interval at which
-the dashboard data is refreshed. The dashboard shows the time its data
-was last updated and when the next update will occur at the top-right
-of the view.
+Charts on a dashboard automatically refresh once their data becomes out
+of date. You can specify how stale your charts' data can be before it is
+refreshed. This is known as your staleness tolerance. The default
+behavior is to refresh when data is one hour stale.
 
-To configure auto refresh settings for a dashboard:
+To configure auto-refresh settings for a dashboard:
 
-1. From the dashboard view, click the arrow next to the
-   :icon:`sync-alt` button and click :guilabel:`Auto Refresh Settings`.
+1. Select a dashboard from the :guilabel:`Dashboards` page.
 
-#. Select the desired refresh interval.
+#. Click :guilabel:`Settings` at the top of the dashboard.
+
+#. Select your data staleness tolerance from the dropdown.
+   |charts-short| supports staleness tolerances between 1 minute and 30
+   days.
 
 #. Click :guilabel:`Save`.
 
-.. note::
+Behavior
+````````
 
-   Auto refresh settings are stored in the local browser state.
-   Settings dictating whether auto refresh is enabled and its
-   configured interval are not persisted with the dashboard or
-   shared with other users.
+- When |charts-short| refreshes dashboard data, only charts with data
+  older than your specified staleness tolerance are refreshed.
+  |charts-short| does not refresh the entire dashboard at once.
 
-Disable and Enable Auto Refresh
+- Auto-refresh settings are stored in the local browser state. These
+  settings are not persisted with the dashboard or shared between
+  users.
+
+- When |charts| loads charts on a dashboard, it does not consistently
+  query the data source for each chart. Instead, |charts| queries the
+  data sources when the dashboard first loads, and that data is cached
+  on both the client and server. 
+
+- When a dashboard refreshes automatically:
+
+  - If a chart's data is within the staleness tolerance period,
+    |charts-short| doesn't refresh the chart's data.
+
+  - If a chart's data is outside of the staleness tolerance period, 
+    |charts-short| returns the latest data from the server cache. If the
+    server cache contains stale data, |charts-short| queries the data 
+    source for the latest data, refreshes the chart, and updates the 
+    data cached on both the client and server.
+    
+- When you manually refresh a dashboard, |charts-short| updates all chart
+  data by querying the data source for the latest data even if the chart
+  data is within the specified staleness tolerance period.
+
+Manually Refresh Dashboard Data
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-To disable auto refresh, click the arrow next to the :icon:`sync-alt`
-button and click :guilabel:`Disable Auto Refresh`.
+To manually refresh dashboard data:
+
+1. Select a dashboard from the :guilabel:`Dashboards` page.
+
+#. Click the arrow next to the :guilabel:`Settings` button.
 
-To enable auto refresh, click the arrow next to the :icon:`sync-alt`
-button and click :guilabel:`Enable Auto Refresh`.
+#. Click :guilabel:`Force Refresh`.
 
 .. _fullscreen-view:
 
@@ -142,7 +155,7 @@ show the title, description, time of last modification, and charts in
 the entire space of the screen.
 
 To open a dashboard in fullscreen view, first select a dashboard from
-the :guilabel:`Dashboards` tab, then click the expanding arrows at the
+the :guilabel:`Dashboards` page, then click the expanding arrows at the
 top-right of the dashboard:
 
 .. figure:: /images/charts/full-screen-view.png
@@ -158,8 +171,7 @@ top-right of the dashboard:
    over the desired chart.
 
    Additionally, in fullscreen view you can still configure
-   auto-refresh settings and manually refresh chart data using the
-   refresh button.
+   auto-refresh settings and manually refresh chart data.
 
 To exit fullscreen view, either click the contracting arrows at the
 top-right of the dashboard or press the escape key.
Original file line number	Diff line number	Diff line change
`@@ -66,6 +66,9 @@`
`66`	`66`	'.. \|aws\| replace:: :abbr:`AWS (Amazon Web Services)`',
`67`	`67`	'.. \|gcp\| replace:: :abbr:`GCP (Google Cloud Platform)`',
`68`	`68`	'.. \|html\| replace:: :abbr:`HTML (HyperText Markup Language)`',
	`69`	+ '.. \|jwt\| replace:: :abbr:`JWT (JSON Web Token)`',
	`70`	+ '.. \|cloud-svc\| replace:: :abbr:`Cloud`',
	`71`	+ '.. \|css\| replace:: :abbr:`CSS (Cascading Style Sheets)`',
`69`	`72`	`]`
`70`	`73`
`71`	`74`	`rst_epilog.extend(get_replacements(conf))`