v1.34 release (#566)

* (DOCSP-26181): Changed sample mode to subset mode.

* (DOCSP-26641) 1.34 release notes (#564)

* (DOCSP-25990) Org-wide sharing (#565)

Author: zach-carr

config/redirects

@@ -24,3 +24,6 @@ raw: docs/charts/atlas ->${base}/
 # streamlined data source changes
 raw: docs/charts/data-source-pipeline/ ->${base}/create-manage-charts-view
 raw: docs/charts/data-source-permissions -> ${base}/manage-data-sources
+
+# sample mode to subset mode
+raw:  docs/charts/sample-mode/ ->${base}/subset-mode

source/build-charts-reference.txt

@@ -6,7 +6,7 @@ Chart Building Reference
 
 .. default-domain:: mongodb
 
-:ref:`charts-sample-mode`
+:ref:`charts-subset-mode`
   Learn how |charts| samples data to improve rendering performance.
 
 :ref:`aggregation-pipeline-generation`
@@ -16,5 +16,5 @@ Chart Building Reference
 .. toctree::
    :titlesonly:
 
-   /sample-mode
+   /subset-mode
    /aggregation-pipeline-generation

source/chart-type-reference/geospatial-heatmap.txt

@@ -20,7 +20,7 @@ criterion.
 
    Heatmap charts can use a maximum of 10,000 documents. If you
    create a heatmap with a collection of more than 10,000
-   documents, turn on :ref:`Sample Mode <charts-sample-mode>` or use a
+   documents, turn on :ref:`Subset Mode <charts-subset-mode>` or use a
    :ref:`filter <charts-filter-documents>`. Otherwise, your chart may
    use incomplete or misleading data.
 

source/dashboard-permissions.txt

@@ -157,7 +157,8 @@ With the :guilabel:`Share Dashboard` dialog open, read the
 following sections to learn how to grant permissions to a dashboard to:
 
 - :ref:`A specific user <dashboard-specific-access>`
-- :ref:`All users on your MongoDB Charts deployment <dashboard-access-everyone>`
+- :ref:`All users in your project <dashboard-access-project>`
+- :ref:`All users in your organization <dashboard-access-org>`
 - :ref:`Any user with the download link <dashboard-access-link>`
 
 .. _dashboard-specific-access:
@@ -167,7 +168,7 @@ Specific User Permissions
 
 To give specific users permissions on the dashboard:
 
-1. Select the :guilabel:`User Access` tab.
+1. Select the :guilabel:`Project` tab.
 
 #. Search for the desired user using the search bar. You can search for 
    users by their username or email address.
@@ -184,27 +185,30 @@ To give specific users permissions on the dashboard:
       can't see any charts that use that data source.
 
       A :authrole:`Project Owner` can assign the user
-      a :atlas:`project role </reference/user-roles/#project-roles>` with the access you want the user to have. To learn more about granting access, see :ref:`permission-model`.
+      a :atlas:`project role </reference/user-roles/#project-roles>` 
+      with the access you want the user to have. To learn more about 
+      granting access, see :ref:`permission-model`.
 
-#. Repeat steps 1-3 for each user you would like to provide dashboard
+#. Repeat these steps for each user you would like to provide dashboard
    permissions for.
 
 #. Click :guilabel:`Close`. |charts| saves your changes automatically.
 
 To remove permissions for a user, click the trash can icon to the right
 of the user's name.
 
+.. _dashboard-access-project:
 .. _dashboard-access-everyone:
 
-Access for All Users
-~~~~~~~~~~~~~~~~~~~~
+Access for All Users in a Project
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 To allow access to the dashboard for all users in your |service|
 project:
 
-1. Select the :guilabel:`User Access` tab.
+1. Select the :guilabel:`Project` tab.
 
-#. Toggle the switch on the right-side of the :guilabel:`Everyone` user
+#. Toggle the switch to the right of the :guilabel:`Everyone` user
    to ``On``.
 
 #. Select the :ref:`permission <dashboard-roles>` to apply to all
@@ -228,10 +232,42 @@ project:
       access.
 
       A :authrole:`Project Owner` can assign the user
-      a :atlas:`project role </reference/user-roles/#project-roles>` with the access you want the user to have. To learn more about granting access, see :ref:`permission-model`.
+      a :atlas:`project role </reference/user-roles/#project-roles>` 
+      with the access you want the user to have. To learn more about 
+      granting access, see :ref:`permission-model`.
 
 #. Click :guilabel:`Close`. |charts| saves your changes automatically.
 
+.. _dashboard-access-org:
+
+Access for All Users in an Organization
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+To allow access to the dashboard for all users in your |service|
+organization:
+
+1. Select the :guilabel:`Organization` tab.
+
+#. Toggle the switch to the right of your organization's name to
+   to ``On``.
+
+   |charts| provides a link with which users in your organization can 
+   view the dashboard.
+
+#. Click :guilabel:`Close`. |charts| saves your changes automatically.
+
+.. note::
+
+   If your organization uses a :abbr:`SSO (Single Sign-On)` provider,
+   MongoDB Cloud prompts users in your organization sign to in through your 
+   provider to view the dashboard. Users who authenticate through your 
+   organization's SSO provider don't need an |service| account.
+
+You can view all dashboards shared with your organization on the 
+:guilabel:`Organization` page. To open the :guilabel:`Organization` 
+page, click :guilabel:`Organization` under the :guilabel:`Dashboards` 
+heading on the left navigation menu.
+
 .. _dashboard-access-link:
 
 Access for Users with a Link to the Dashboard
@@ -244,14 +280,14 @@ on each data source in the charts in the dashboard.
 To allow access to the dashboard for users on your |charts|
 deployment who have a direct link:
 
-1. Select the :guilabel:`Public Link` tab.
+1. Select the :guilabel:`Public` tab.
 
 #. Toggle the switch on the right-side of the
-   :guilabel:`Anyone with this link can view` user to ``On``.
+   :guilabel:`Public` user to ``On``.
 
-   A user's permissions don't affect their ability to view a chart
-   using a link. |charts| generates two links: a public and a private
-   one. The public link has no permission requirements.
+   |charts| generates a public link with which anyone can 
+   view the dashboard. A user's permissions don't affect their ability 
+   to view a chart using a public link.
 
    .. important::
 

source/includes/steps-launch-charts-saas.yaml

@@ -59,7 +59,7 @@ content: |
 
   To create an |service| cluster:
 
-  a. In the left navigation pane, click :guilabel:`Clusters`.
+  a. In the left navigation menu, click :guilabel:`Clusters`.
 
   #. Click :guilabel:`Build a New Cluster`.
 

source/release-notes.txt

@@ -10,6 +10,28 @@ MongoDB Charts Release Notes
    :depth: 1
    :class: twocols
 
+|charts| v1.34
+--------------
+
+*Released November 16th, 2022*
+
+Improvements in this release:
+
+- You can now :ref:`share dashboards <modify-dashboard-permissions>` 
+  across an |service| organization.
+
+Bug fixes in this release:
+
+- Fixes an issue with adding date filters inside the Chart Builder.
+
+- Fixes an issue where filter selections were not saved 
+  correctly when building charts.
+
+- Fixes an issue where non-binned dates with null values were not saved 
+  correctly when exported as CSV.
+
+- Fixes an issue where the Charts homepage did not load.
+
 |charts| v1.33.2
 ----------------
 

source/sample-mode.txt

@@ -0,0 +1,45 @@
+.. _charts-subset-mode:
+
+===========
+Subset Mode
+===========
+
+.. default-domain:: mongodb
+
+You can enable :guilabel:`Subset Mode` in MongoDB Charts to restrict 
+the input collection to ``1000`` randomly selected documents. To toggle
+:guilabel:`Subset Mode`, use the toggle in the :guilabel:`Preview` 
+section. The :guilabel:`Subset Mode` setting for a chart persists when 
+the chart renders on a dashboard. So, if you enable subset mode when 
+you build a chart, the data that renders in the dashboard is also 
+sampled.
+
+.. note::
+
+   When you enable subset mode and you specify a :ref:`filter 
+   <charts-filter-documents>`, |charts| takes the sample of ``1000``
+   documents *before* it applies the filter. So, |charts| might use 
+   fewer than ``1000`` documents to plot the chart.
+
+Use Cases
+---------
+
+Consider using :guilabel:`Subset Mode` in the following scenarios:
+
+- When you draft a chart and heavily modify chart options. In this
+  situation, :guilabel:`Subset Mode` lets the chart render quickly 
+  during the building process. When you feel satisfied with your chart, 
+  you can disable :guilabel:`Subset Mode` to have all documents 
+  included in your final visualization.
+
+- When you visualize a large data source and the chosen data is
+  sufficiently aggregated (e.g. showing averages of fields) so
+  you don't need all documents to obtain a useful visualization.
+  In this case, if you leave :guilabel:`Subset Mode` enabled for the 
+  rendered dashboard, you can still retain a useful chart.
+
+.. note::
+
+   Due to the random nature of sampling, when you have 
+   :guilabel:`Subset Mode` enabled, your visualizations might change 
+   each time the chart loads.

source/subset-mode.txt

@@ -44,7 +44,7 @@ data source that considers:
 
 - :ref:`Pipelines applied to the data source <data-sources-pipeline>`
 
-- :ref:`Sample mode <charts-sample-mode>` (if toggled on)
+- :ref:`Subset Mode <charts-subset-mode>` (if toggled on)
 
 - :ref:`Queries <query-bar>` or
   :ref:`pipelines specified in the Chart Builder <charts-agg-pipeline>`