diff --git a/docs/README.md b/docs/README.md index 1093b47bcb..c02143a1f0 100644 --- a/docs/README.md +++ b/docs/README.md @@ -66,10 +66,10 @@ Check out the existing patterns in the source files and you'll catch on. For Voxel51 developers who are working with a source install of the FiftyOne Brain: the build script will automatically use your source install! -### Teams SDK +### Enterprise SDK -Voxel51 developers can include Teams SDK-related components in their local docs -build by including the `-t` flag: +Voxel51 developers can include Enterprise SDK-related components in their local +docs build by including the `-t` flag: ```shell bash docs/generate_docs.bash -t /path/to/fiftyone-teams diff --git a/docs/generate_docs.bash b/docs/generate_docs.bash index 5c11b80dc4..9209c5e3dc 100755 --- a/docs/generate_docs.bash +++ b/docs/generate_docs.bash @@ -15,7 +15,7 @@ Options: -f Perform a fast build (don't regenerate zoo/plugin docs). -c Perform a clean build (deletes existing build directory). -s Copy static files only (CSS, JS). --t Path to fiftyone-teams clone to use for Teams docs +-t Path to fiftyone-teams clone to use for Enterprise docs " } diff --git a/docs/source/_templates/layout.html b/docs/source/_templates/layout.html index 76457ed838..8ac5ffacfa 100644 --- a/docs/source/_templates/layout.html +++ b/docs/source/_templates/layout.html @@ -42,7 +42,7 @@
@@ -132,7 +132,7 @@

Products

FiftyOne - FiftyOne Teams + FiftyOne Enterprise Use Cases Success Stories
diff --git a/docs/source/cheat_sheets/fiftyone_terminology.rst b/docs/source/cheat_sheets/fiftyone_terminology.rst index d3a74eee46..02ff769bdf 100644 --- a/docs/source/cheat_sheets/fiftyone_terminology.rst +++ b/docs/source/cheat_sheets/fiftyone_terminology.rst @@ -20,7 +20,7 @@ __________ - The :ref:`provided user interface ` for graphically viewing, filtering, and understanding your datasets. Can be launched in the browser or within notebooks. - * - FiftyOne Teams + * - FiftyOne Enterprise - `The enterprise-grade suite `_ built on top of FiftyOne for collaboration, permissioning, and working with cloud-backed media. diff --git a/docs/source/deprecation.rst b/docs/source/deprecation.rst index c5637ef0b0..9f47281c5b 100644 --- a/docs/source/deprecation.rst +++ b/docs/source/deprecation.rst @@ -32,6 +32,6 @@ Kubernetes 1.27 *Support ended November 1, 2024* `Kubernetes 1.27 `_ -transitioned to `end-of-life` effective July of 2024. FiftyOne Teams +transitioned to `end-of-life` effective July of 2024. FiftyOne Enterprise releases after October 31, 2024 might no longer be compatible with Kubernetes 1.27 and older. diff --git a/docs/source/environments/index.rst b/docs/source/environments/index.rst index e4c28a3ec4..9b4a6d16dd 100644 --- a/docs/source/environments/index.rst +++ b/docs/source/environments/index.rst @@ -519,7 +519,7 @@ environments. not recommended or officially supported. It is useful only for prototyping. Our recommended, scalable approach to work with cloud-backed data is - :ref:`FiftyOne Teams `, an enterprise deployment of + :ref:`FiftyOne Enterprise `, an enterprise deployment of FiftyOne with multiuser collaboration features, native cloud dataset support, and much more! diff --git a/docs/source/faq/index.rst b/docs/source/faq/index.rst index b6f1288fe6..123eb52315 100644 --- a/docs/source/faq/index.rst +++ b/docs/source/faq/index.rst @@ -163,7 +163,7 @@ you can :ref:`load a dataset remotely ` and then explore it via an Can I access data stored in the cloud? -------------------------------------- -Yes! Check out :ref:`FiftyOne Teams `. +Yes! Check out :ref:`FiftyOne Enterprise `. .. _faq-supported-os: diff --git a/docs/source/getting_started/install.rst b/docs/source/getting_started/install.rst index 9419d0d8c9..3f4701dbe3 100644 --- a/docs/source/getting_started/install.rst +++ b/docs/source/getting_started/install.rst @@ -12,7 +12,7 @@ FiftyOne Installation .. note:: Need to collaborate on your datasets? Check out - :ref:`FiftyOne Teams `! + :ref:`FiftyOne Enterprise `! .. _install-prereqs: diff --git a/docs/source/index.rst b/docs/source/index.rst index 1990c62927..fb0e771c3e 100644 --- a/docs/source/index.rst +++ b/docs/source/index.rst @@ -477,7 +477,7 @@ us at support@voxel51.com. :hidden: Overview - FiftyOne Teams 🚀 + FiftyOne Enterprise 🚀 Installation Environments Tutorials diff --git a/docs/source/plugins/developing_plugins.rst b/docs/source/plugins/developing_plugins.rst index c538a1f5ff..ef1a7d1b3e 100644 --- a/docs/source/plugins/developing_plugins.rst +++ b/docs/source/plugins/developing_plugins.rst @@ -1323,9 +1323,9 @@ on their execution context from within .. note:: - :ref:`FiftyOne Teams ` users can view the current progress + :ref:`FiftyOne Enterprise ` users can view the current progress of their delegated operations from the - :ref:`Runs page ` of the Teams App! + :ref:`Runs page ` of the Enterprise App! For your convenience, all builtin methods of the FiftyOne SDK that support rendering progress bars provide an optional `progress` method that you can use diff --git a/docs/source/plugins/using_plugins.rst b/docs/source/plugins/using_plugins.rst index d234714a4d..097acf1fd1 100644 --- a/docs/source/plugins/using_plugins.rst +++ b/docs/source/plugins/using_plugins.rst @@ -811,7 +811,7 @@ operator's input modal when executing it from within the App: .. note:: - :ref:`FiftyOne Teams ` users can also specify an optional + :ref:`FiftyOne Enterprise ` users can also specify an optional delegation target for their delegated operations: .. code-block:: python @@ -857,11 +857,11 @@ curation, and evaluation are performed. Want to run delegated operations at scale? `Contact us `_ about - :ref:`FiftyOne Teams `, an open source-compatible + :ref:`FiftyOne Enterprise `, an open source-compatible enterprise deployment of FiftyOne with multiuser collaboration features, native cloud dataset support, and much more! - Think of FiftyOne Teams as the single source of truth on which you + Think of FiftyOne Enterprise as the single source of truth on which you co-develop your data and models together 📈 .. _managing-delegated-operations: @@ -974,9 +974,9 @@ development environment by following these steps: Want to run delegated operations at scale in production? `Contact us `_ about - :ref:`FiftyOne Teams `, an open source-compatible + :ref:`FiftyOne Enterprise `, an open source-compatible enterprise deployment of FiftyOne with multiuser collaboration features, native cloud dataset support, and much more! - FiftyOne Teams as the single source of truth on which you + FiftyOne Enterprise as the single source of truth on which you co-develop your data and models together 📈 diff --git a/docs/source/release-notes.rst b/docs/source/release-notes.rst index 80fdc71710..dca6a0f882 100644 --- a/docs/source/release-notes.rst +++ b/docs/source/release-notes.rst @@ -3,7 +3,7 @@ FiftyOne Release Notes .. default-role:: code -FiftyOne Teams 2.1.3 +FiftyOne Enterprise 2.1.3 -------------------- *Released November XX, 2024* @@ -52,14 +52,14 @@ App - Fixed batch selection with ctrl + click in the grid `#5046 `_ -FiftyOne Teams 2.1.2 +FiftyOne Enterprise 2.1.2 -------------------- *Released October 31, 2024* - Fixed an issue that prevented `delegation_target` from being properly set when running delegated operations with orchestrator registration enabled -FiftyOne Teams 2.1.1 +FiftyOne Enterprise 2.1.1 -------------------- *Released October 14, 2024* @@ -94,7 +94,7 @@ Core :ref:`COCO format ` `#4884 `_ -FiftyOne Teams 2.1.0 +FiftyOne Enterprise 2.1.0 -------------------- *Released October 1, 2024* @@ -107,7 +107,7 @@ Includes all updates from :ref:`FiftyOne 1.0.0 `, plus: :ref:`Internal Mode ` - Optimized performance of the :ref:`dataset page ` - Fixed a BSON serialization bug that could cause errors when cloning or - exporting certain dataset views from the Teams UI + exporting certain dataset views from the Enterprise UI .. _release-notes-v1.0.0: @@ -214,7 +214,7 @@ FiftyOne 0.25.2 - Require `pymongo<4.9` to fix database connections - Require `pydicom<3` for :ref:`DICOM datasets ` -FiftyOne Teams 2.0.1 +FiftyOne Enterprise 2.0.1 -------------------- *Released September 6, 2024* @@ -280,7 +280,7 @@ Plugins don't return outputs `#4715 `_ -FiftyOne Teams 2.0.0 +FiftyOne Enterprise 2.0.0 -------------------- *Released August 20, 2024* @@ -321,7 +321,7 @@ SDK - Added a :mod:`user_groups ` module to the Management SDK for programmatically managing user groups -- The `fiftyone delegated` CLI command is now available to Teams users +- The `fiftyone delegated` CLI command is now available to Enterprise users - Upgraded the :ref:`upload_media() ` function to gracefully support fields with missing media paths - Added an `overwrite` parameter to @@ -466,7 +466,7 @@ Zoo `#4509 `_, `#4512 `_ -FiftyOne Teams 1.7.1 +FiftyOne Enterprise 1.7.1 -------------------- *Released June 11, 2024* @@ -516,7 +516,7 @@ Annotation - Added support loading annotations for large CVAT tasks with many jobs `#4392 `_ -FiftyOne Teams 1.7.0 +FiftyOne Enterprise 1.7.0 -------------------- *Released May 29, 2024* @@ -527,8 +527,8 @@ Includes all updates from :ref:`FiftyOne 0.24.0 `, plus: - Added support for customizing the role that a user will have when sending an invitation for a new user to access a specific dataset - Added the ability to configure the expiration time for signed URLs used by - your FiftyOne Teams deployment -- Fixed a regression from FiftyOne Teams 1.6 that could cause login errors when + your FiftyOne Enterprise deployment +- Fixed a regression from FiftyOne Enterprise 1.6 that could cause login errors when accepting invites .. _release-notes-v0.24.0: @@ -629,16 +629,16 @@ Zoo - Fixed a bug with :ref:`YOLO-NAS inference ` `#4429 `_ -FiftyOne Teams 1.6.1 +FiftyOne Enterprise 1.6.1 -------------------- *Released May 10, 2024* Bugs -- Fixed an issue with logging into FiftyOne Teams in Enterprise Proxy +- Fixed an issue with logging into FiftyOne Enterprise in Enterprise Proxy enviornments -FiftyOne Teams 1.6.0 +FiftyOne Enterprise 1.6.0 -------------------- *Released April 30, 2024* @@ -647,22 +647,22 @@ What's New - Added :ref:`Groups ` for managing and dataset access for groups of users - Introduced a new :ref:`Pluggable Authentication ` system for - customizing FiftyOne Teams authentication -- Removed Auth0 as a hard dependency for Teams deployments with the + customizing FiftyOne Enterprise authentication +- Removed Auth0 as a hard dependency for Enterprise deployments with the introduction of :ref:`Internal Mode ` - Added support for directly authenticating with :ref:`Identity Providers ` - Added a :ref:`Super Admin UI ` for administering FiftyOne - Teams deployments + Enterprise deployments - Added the ability to search for users on the Users page -FiftyOne Teams 1.5.10 +FiftyOne Enterprise 1.5.10 --------------------- *Released April 18, 2024* - Fixed an issue where video datasets were not loading due to ffmpeg dependency -FiftyOne Teams 1.5.9 +FiftyOne Enterprise 1.5.9 -------------------- *Released April 15, 2024* @@ -793,7 +793,7 @@ Zoo frames of video datasets `#4229 `_ -FiftyOne Teams 1.5.8 +FiftyOne Enterprise 1.5.8 -------------------- *Released March 21, 2024* @@ -900,7 +900,7 @@ Core - Cloning a dataset or view now includes any custom MongoDB indexes `#4115 `_ -FiftyOne Teams 1.5.7 +FiftyOne Enterprise 1.5.7 -------------------- *Released March 6, 2024* @@ -958,7 +958,7 @@ Bugs selection is present `#4113 `_ -FiftyOne Teams 1.5.6 +FiftyOne Enterprise 1.5.6 -------------------- *Released February 14, 2024* @@ -1005,7 +1005,7 @@ Bugs `#4048 `_ -FiftyOne Teams 1.5.5 +FiftyOne Enterprise 1.5.5 -------------------- *Released January 25, 2024* @@ -1032,7 +1032,7 @@ Brain :ref:`custom visualization methods ` `#4038 `_ -FiftyOne Teams 1.5.4 +FiftyOne Enterprise 1.5.4 -------------------- *Released January 19, 2024* @@ -1044,7 +1044,7 @@ General :meth:`export() ` calls involving cloud-backed media - Deployments with their `FIFTYONE_API_URI` environment variable set will now - display the API URI to users in the Teams App + display the API URI to users in the Enterprise App - Improved debug logs by adding the head and tail of large results - Updated `motor` dependency to 3.3.0 @@ -1151,7 +1151,7 @@ Tutorials .. _release-notes-teams-v1.5.3: -FiftyOne Teams 1.5.3 +FiftyOne Enterprise 1.5.3 -------------------- *Released December 21, 2023* @@ -1247,7 +1247,7 @@ Plugins .. _release-notes-teams-v1.5.2: -FiftyOne Teams 1.5.2 +FiftyOne Enterprise 1.5.2 -------------------- *Released December 11, 2023* @@ -1258,7 +1258,7 @@ Bugs .. _release-notes-teams-v1.5.1: -FiftyOne Teams 1.5.1 +FiftyOne Enterprise 1.5.1 -------------------- *Released December 8, 2023* @@ -1293,7 +1293,7 @@ Core .. _release-notes-teams-v1.5.0: -FiftyOne Teams 1.5.0 +FiftyOne Enterprise 1.5.0 -------------------- *Released December 6, 2023* @@ -1312,7 +1312,7 @@ Features - Added support for uploading media :ref:`to Labelbox ` directly from S3 buckets - Added support for executing the builtin ``open_dataset`` operator in the - Teams UI + Enterprise UI - Added support for executing operators when viewing datasets with no samples, for example to add media/labels to the dataset from within the App - Added support for :ref:`editing the label ` of a @@ -1337,7 +1337,7 @@ Bugs delegated operations that were scheduled via the SDK - Users with special access to a dataset are now displayed properly - Fixed an issue when loading certain datasets with saved - :ref:`color schemes ` in the Teams UI + :ref:`color schemes ` in the Enterprise UI - Fixed an issue on the dataset listing page where the page size menu would sometimes stay open after making a selection - Fixed an issue when downloading plugins via the API that contain bytes data @@ -1518,7 +1518,7 @@ Bugs .. _release-notes-teams-v1.4.5: -FiftyOne Teams 1.4.5 +FiftyOne Enterprise 1.4.5 -------------------- *Released November 21, 2023* @@ -1528,7 +1528,7 @@ General .. _release-notes-teams-v1.4.4: -FiftyOne Teams 1.4.4 +FiftyOne Enterprise 1.4.4 -------------------- *Released November 3, 2023* @@ -1610,7 +1610,7 @@ CLI .. _release-notes-teams-v1.4.3: -FiftyOne Teams 1.4.3 +FiftyOne Enterprise 1.4.3 -------------------- *Released October 20, 2023* @@ -1699,7 +1699,7 @@ Zoo .. _release-notes-teams-v1.4.2: -FiftyOne Teams 1.4.2 +FiftyOne Enterprise 1.4.2 -------------------- *Released October 6, 2023* @@ -1779,17 +1779,17 @@ Plugins .. _release-notes-teams-v1.4.1: -FiftyOne Teams 1.4.1 +FiftyOne Enterprise 1.4.1 -------------------- *Released September 21, 2023* Bugs -- Patched a regression that prevented the Teams App from working behind proxies +- Patched a regression that prevented the Enterprise App from working behind proxies .. _release-notes-teams-v1.4.0: -FiftyOne Teams 1.4.0 +FiftyOne Enterprise 1.4.0 -------------------- *Released September 20, 2023* @@ -1926,7 +1926,7 @@ Zoo .. _release-notes-teams-v1.3.6: -FiftyOne Teams 1.3.6 +FiftyOne Enterprise 1.3.6 -------------------- *Released August 8, 2023* @@ -1947,7 +1947,7 @@ App .. _release-notes-teams-v1.3.5: -FiftyOne Teams 1.3.5 +FiftyOne Enterprise 1.3.5 -------------------- *Released August 7, 2023* @@ -2109,7 +2109,7 @@ FiftyOne 0.21.4 .. _release-notes-teams-v1.3.3: -FiftyOne Teams 1.3.3 +FiftyOne Enterprise 1.3.3 -------------------- *Released July 12, 2023* @@ -2163,7 +2163,7 @@ Core .. _release-notes-teams-v1.3.2: -FiftyOne Teams 1.3.2 +FiftyOne Enterprise 1.3.2 -------------------- *Released July 5, 2023* @@ -2184,7 +2184,7 @@ App .. _release-notes-teams-v1.3.1: -FiftyOne Teams 1.3.1 +FiftyOne Enterprise 1.3.1 -------------------- *Released June 30, 2023* @@ -2194,9 +2194,9 @@ plus: General - App containers no longer need to be restarted in order for Azure/MinIO - credentials uploaded via the Teams UI to be properly recognized + credentials uploaded via the Enterprise UI to be properly recognized - Fixed an intermittent bug when computing metadata for remote filepaths -- Reverted a change from Teams 1.3.0 so that the SDK again supports the +- Reverted a change from Enterprise 1.3.0 so that the SDK again supports the declared minimum version requirement of `pymongo==3.12` SDK @@ -2204,7 +2204,7 @@ SDK - Updated the order of precedence for SDK connections so that :ref:`API connections ` take precedence over :ref:`direct database connections ` -- Fixed a bug when connecting to Teams deployments with non-standard database +- Fixed a bug when connecting to Enterprise deployments with non-standard database names via API connections - Fixed a bug when saving run results using API connections - Fixed a bug when deleting datasets using API connections @@ -2293,7 +2293,7 @@ Annotation .. _release-notes-teams-v1.3.0: -FiftyOne Teams 1.3.0 +FiftyOne Enterprise 1.3.0 -------------------- *Released May 31, 2023* @@ -2311,15 +2311,15 @@ General - Improved non-persistent dataset cleanup behavior - Fixed a bug that could cause the media cache to erroneously garbage collect large files while they are downloading -- Fixed a bug when cloning views into new datasets via the Teams UI +- Fixed a bug when cloning views into new datasets via the Enterprise UI Admin - Added support for :ref:`uploading and managing plugins ` via - the Teams UI + the Enterprise UI - Added support for cross account IAM roles when configuring cloud storage credentials -- Fixed a bug that prevented Azure/MinIO credentials uploaded via the Teams UI +- Fixed a bug that prevented Azure/MinIO credentials uploaded via the Enterprise UI from being properly recognized by the App .. _release-notes-v0.21.0: @@ -2432,7 +2432,7 @@ Tutorials .. _release-notes-teams-v1.2.1: -FiftyOne Teams 1.2.1 +FiftyOne Enterprise 1.2.1 -------------------- *Released April 5, 2023* @@ -2444,7 +2444,7 @@ General - When your session expires, you are now automatically logged out rather than being presented with a cryptic server error - Improved the accuracy of size estimates when exporting filepaths and/or tags - from the Teams UI + from the Enterprise UI Admin @@ -2528,7 +2528,7 @@ Documentation .. _release-notes-teams-v1.2: -FiftyOne Teams 1.2 +FiftyOne Enterprise 1.2 ------------------ *Released March 22, 2023* @@ -2537,7 +2537,7 @@ plus: Admin settings -- Admins who use SSO to authorize new users to auto-join their FiftyOne Teams +- Admins who use SSO to authorize new users to auto-join their FiftyOne Enterprise deployment can now configure the :ref:`default role ` for those users - Admins can now configure the @@ -2549,7 +2549,7 @@ Dataset page - Added support for viewing :ref:`Segmentation ` and :ref:`Heatmap ` data stored as images in the cloud in the App - Added support for exporting one or more fields of a dataset in CSV format - through the Teams UI + through the Enterprise UI - Stack traces for unhandled errors are now presented directly in the App so that users can self-diagnose issues @@ -2773,7 +2773,7 @@ Tutorials .. _release-notes-teams-v1.1.1: -FiftyOne Teams 1.1.1 +FiftyOne Enterprise 1.1.1 -------------------- *Released February 14, 2023* @@ -2782,7 +2782,7 @@ plus: Plugins -- Resolved a bug that prevented Teams deployments from recognizing installed +- Resolved a bug that prevented Enterprise deployments from recognizing installed plugins .. _release-notes-v0.19.1: @@ -2806,7 +2806,7 @@ Core .. _release-notes-teams-v1.1: -FiftyOne Teams 1.1 +FiftyOne Enterprise 1.1 ------------------ *Released February 9, 2023* @@ -2825,7 +2825,7 @@ User roles Homepage - Added a Recent views widget to the homepage that shows the most recent saved - views that you have viewed in the Teams UI + views that you have viewed in the Enterprise UI Dataset page @@ -2837,7 +2837,7 @@ Dataset page Deployment -- Added support for deploying Teams into environments with proxy networks +- Added support for deploying Enterprise into environments with proxy networks .. _release-notes-v0.19.0: @@ -2847,7 +2847,7 @@ FiftyOne 0.19.0 News -- :ref:`FiftyOne Teams ` documentation is now publicly +- :ref:`FiftyOne Enterprise ` documentation is now publicly available! `#2388 `_ App @@ -3045,7 +3045,7 @@ Docs .. _release-notes-teams-v1.0: -FiftyOne Teams 1.0 +FiftyOne Enterprise 1.0 ------------------ *Released November 8, 2022* @@ -3054,7 +3054,7 @@ plus: News -- FiftyOne Teams is now generally available, +- FiftyOne Enterprise is now generally available, :ref:`read more here `! .. _release-notes-v0.18.0: diff --git a/docs/source/teams/api_connection.rst b/docs/source/teams/api_connection.rst index f8f5fb6f38..2c670800ea 100644 --- a/docs/source/teams/api_connection.rst +++ b/docs/source/teams/api_connection.rst @@ -6,7 +6,7 @@ API Connection .. default-role:: code This page describes how to create API keys and configure your -:ref:`SDK installation ` to connect to your Teams +:ref:`SDK installation ` to connect to your Enterprise deployment's API. All actions taken via API connections are authenticated based on the user @@ -16,7 +16,7 @@ dataset permissions *are enforced*. .. note:: **API connections are currently in beta.** The recommended stable solution - is to use your Teams deployment's + is to use your Enterprise deployment's :ref:`MongoDB connection `. .. _configuring-an-api-connection: @@ -27,13 +27,13 @@ Configuring an API connection You can configure an API connection by adding an API URI and API key to your FiftyOne config as described below: -+-------------------------------+-------------------------------------+----------------------------------------------------------------------------------------+ -| Config field | Environment variable | Description | -+===============================+=====================================+========================================================================================+ -| `api_uri` | `FIFTYONE_API_URI` | The URI of your FiftyOne Teams API. Ask your deployment admin for this value. | -+-------------------------------+-------------------------------------+----------------------------------------------------------------------------------------+ -| `api_key` | `FIFTYONE_API_KEY` | Your FiftyOne Teams API key. :ref:`See here ` to generate one. | -+-------------------------------+-------------------------------------+----------------------------------------------------------------------------------------+ ++-------------------------------+-------------------------------------+---------------------------------------------------------------------------------------------+ +| Config field | Environment variable | Description | ++===============================+=====================================+=============================================================================================+ +| `api_uri` | `FIFTYONE_API_URI` | The URI of your FiftyOne Enterprise API. Ask your deployment admin for this value. | ++-------------------------------+-------------------------------------+---------------------------------------------------------------------------------------------+ +| `api_key` | `FIFTYONE_API_KEY` | Your FiftyOne Enterprise API key. :ref:`See here ` to generate one. | ++-------------------------------+-------------------------------------+---------------------------------------------------------------------------------------------+ For example, you can set environment variables: @@ -62,7 +62,7 @@ Generating keys via the UI ~~~~~~~~~~~~~~~~~~~~~~~~~~ You can access API key management features by clicking on your account icon in -the upper-right of the FiftyOne Teams App and navigating to the +the upper-right of the FiftyOne Enterprise App and navigating to the "Settings > API keys" page. A new key can be generated by clicking on "Generate API key" and optionally diff --git a/docs/source/teams/cloud_media.rst b/docs/source/teams/cloud_media.rst index c9cac450d4..7fbf5e8fa0 100644 --- a/docs/source/teams/cloud_media.rst +++ b/docs/source/teams/cloud_media.rst @@ -5,13 +5,13 @@ Cloud-Backed Media .. default-role:: code -FiftyOne Teams datasets may contain samples whose filepath refers to cloud +FiftyOne Enterprise datasets may contain samples whose filepath refers to cloud object storage paths and/or publicly available URLs. .. note:: :ref:`Click here ` to see how to configure FiftyOne - Teams to load your cloud credentials! + Enterprise to load your cloud credentials! .. _teams-cloud-media-caching: @@ -19,7 +19,7 @@ Cloud media caching ___________________ When you work with cloud-backed datasets using the -:ref:`Teams SDK `, media files will automatically be +:ref:`Enterprise SDK `, media files will automatically be downloaded and cached on the machine you’re working from when you execute workflows such as model inference or Brain methods that require access to the pixels of the media files. This design minimizes bandwidth usage and can @@ -37,7 +37,7 @@ file repeatedly: # Automatically downloads cloud media to your local cache for processing fob.compute_visualization(dataset, brain_key="img_viz") -When launching the App locally using the Teams SDK, media will be served from +When launching the App locally using the Enterprise SDK, media will be served from your local cache whenever possible; otherwise it will be automatically retrieved from the cloud: @@ -121,7 +121,7 @@ precedence over JSON config settings. Working with cloud-backed datasets __________________________________ -When writing Python code using the Teams client that may involve cloud-backed +When writing Python code using the Enterprise client that may involve cloud-backed datasets, use `sample.local_path` instead of `sample.filepath` to retrieve the location of the locally cached version of a media file: @@ -142,7 +142,7 @@ the location of the locally cached version of a media file: .. note:: If `sample.filepath` itself is a local path, then `sample.local_path` - will simply return that path. In other words, it is safe to write all Teams + will simply return that path. In other words, it is safe to write all Enterprise Python code as if the dataset contains cloud-backed media. .. note:: @@ -837,15 +837,15 @@ method to pass URLs for your S3-backed media when creating Labelbox data rows. AWS Lambda and Google Cloud Functions _____________________________________ -FiftyOne Teams can easily be used in AWS Lambda Functions and Google Cloud +FiftyOne Enterprise can easily be used in AWS Lambda Functions and Google Cloud Functions. **Requirements** -We recommend including Teams in your function’s `requirements.txt` file by +We recommend including Enterprise in your function’s `requirements.txt` file by passing your token as a build environment variable, e.g., `FIFTYONE_TEAMS_TOKEN` and then using the syntax below to specify the version -of the Teams client to use: +of the Enterprise client to use: .. code-block:: text diff --git a/docs/source/teams/dataset_versioning.rst b/docs/source/teams/dataset_versioning.rst index 68ff457ffe..9868d1850b 100644 --- a/docs/source/teams/dataset_versioning.rst +++ b/docs/source/teams/dataset_versioning.rst @@ -5,7 +5,7 @@ Dataset Versioning .. default-role:: code -FiftyOne Teams provides native support for versioning your datasets! +FiftyOne Enterprise provides native support for versioning your datasets! Dataset Versioning allows you to capture the state of your dataset in time so that it can be referenced in the future. This enables workflows like recalling @@ -24,7 +24,7 @@ annotation added, etc) as well as helping to prevent accidental data loss. Overview ________ -Dataset Versioning in FiftyOne Teams is implemented as a linear sequence of +Dataset Versioning in FiftyOne Enterprise is implemented as a linear sequence of read-only :ref:`Snapshots `. In other words, creating a new Snapshot creates a permanent record of the dataset’s contents that can be loaded and viewed at any time in the future, but not directly @@ -78,7 +78,7 @@ Dataset Versioning has been built with an extensible architecture so that different versioning backends can be swapped in. Each backend may have different tradeoffs in terms of performance, storage, and deployment needs, so users should be able to choose the best fit for their needs. In addition, many -users may already have a versioning solution external to FiftyOne Teams, and +users may already have a versioning solution external to FiftyOne Enterprise, and the goal is to support integration around those use cases as well. Currently, only the @@ -97,7 +97,7 @@ are :ref:`on the roadmap `. Snapshots _________ -Dataset Versioning in FiftyOne Teams is implemented as a linear history of +Dataset Versioning in FiftyOne Enterprise is implemented as a linear history of **Snapshots**. A Snapshot captures the state of a dataset at a particular point in time as an immutable object. Compare this concept to creating commits and tags in a single branch of a version control system such as git or svn; a @@ -133,7 +133,7 @@ choices and user actions. Virtual Snapshot A Snapshot whose state and contents are stored by the pluggable backend versioning implementation in whatever way it chooses. In order to be - loaded by FiftyOne Teams users, the Snapshot must be *materialized* + loaded by FiftyOne Enterprise users, the Snapshot must be *materialized* into its workable form in MongoDB. This is done through a combination of the overarching versioning infrastructure and the specific versioning backend. @@ -278,7 +278,7 @@ trigger a modification to the stored dataset. List snapshots -------------- -Teams UI +Enterprise UI ~~~~~~~~ To access the Snapshot history and management page, click the "History tab" on @@ -330,10 +330,10 @@ Loading snapshots ----------------- Any user with Can View permissions to a dataset can view and load its snapshots -via the Teams UI or the SDK. +via the Enterprise UI or the SDK. -Teams UI -~~~~~~~~ +Enterprise UI +~~~~~~~~~~~~~ From the dataset's History tab, click the "Browse" button next to a Snapshot in the :ref:`snapshot list ` to load the @@ -409,14 +409,14 @@ Creating a snapshot ------------------- Users with Can Manage permissions to a dataset can create Snapshots through the -Teams UI or the Management SDK. +Enterprise UI or the Management SDK. .. note:: Snapshots can only be created from the HEAD of the dataset. -Teams UI -~~~~~~~~ +Enterprise UI +~~~~~~~~~~~~~ At the top of the History tab for a dataset is the Create snapshot panel. This panel shows the number of changes that have happened between the last @@ -505,7 +505,7 @@ Deleting a snapshot ------------------- Users with Can Manage permissions to a dataset can delete snapshots through the -Teams UI or the Management SDK. +Enterprise UI or the Management SDK. If the Snapshot is the most recent, the latest (HEAD) sample changes summary is not automatically recalculated. See @@ -520,8 +520,8 @@ Snapshot. Deleting a Snapshot cannot be undone! -Teams UI -~~~~~~~~ +Enterprise UI +~~~~~~~~~~~~~ To delete a Snapshot via the App, open the 3-dot (kebab) menu for the Snapshot. In the menu, click "Delete snapshot". This will bring up a confirmation dialog @@ -562,8 +562,8 @@ of a given Snapshot. **all** changes between the selected Snapshot and the current working version of the dataset, including all newer Snapshots. -Teams UI -~~~~~~~~ +Enterprise UI +~~~~~~~~~~~~~ To revert a dataset to a Snapshot's state, click the 3-dot (kebab) menu in the History tab for the Snapshot you want to rollback to and select @@ -615,8 +615,8 @@ configured cold storage location via the UI or the Management SDK. The snapshot must first be :ref:`unarchived `. -Teams UI -~~~~~~~~ +Enterprise UI +~~~~~~~~~~~~~ To manually archive a snapshot, click the 3-dot (kebab) menu in the History tab for a snapshot you want to archive and select "Archive snapshot". This will @@ -655,8 +655,8 @@ Unarchive snapshot To make an archived snapshot browsable again, users with Can Manage permissions to the dataset can unarchive it via the UI or Management SDK. -Teams UI -~~~~~~~~ +Enterprise UI +~~~~~~~~~~~~~ To unarchive a snapshot, click the "Unarchive" button in the History tab for a snapshot you want to unarchive. This will begin the unarchival process and the @@ -701,7 +701,7 @@ better suit the users' needs and technology preferences. In the future, this section will contain information and discussion about each of these available backends, including their strengths/limitations and configuration options. -For the initial release in FiftyOne Teams v1.4.0, however, there is only one +For the initial release in FiftyOne Enterprise v1.4.0, however, there is only one backend choice described below. Additional backends may be implemented in the future, but for now, releasing dataset versioning with the first iteration was prioritized so that users can begin to see value and provide @@ -808,7 +808,7 @@ following advice: Configuration ------------- -Since Snapshots impact the storage needs of FiftyOne Teams, some guard rails +Since Snapshots impact the storage needs of FiftyOne Enterprise, some guard rails have been put in place to control the maximum amount of Snapshots that can be created. If a threshold has been exceeded while a user attempts to create a new Snapshot, they will receive an error informing them that it may be time to @@ -844,7 +844,7 @@ Roadmap _______ The following are some items that are on the roadmap for future iterations -of the dataset versioning system. Keep an eye out for future FiftyOne Teams +of the dataset versioning system. Keep an eye out for future FiftyOne Enterprise versions for these additional features! **Near term** diff --git a/docs/source/teams/index.rst b/docs/source/teams/index.rst index 25044a0530..4225f81182 100644 --- a/docs/source/teams/index.rst +++ b/docs/source/teams/index.rst @@ -1,7 +1,7 @@ .. _fiftyone-teams: -FiftyOne Teams -============== +FiftyOne Enterprise +=================== .. Social links --------------------------------------------------------------- @@ -32,14 +32,14 @@ FiftyOne Teams .. End social links ----------------------------------------------------------- -`FiftyOne Teams `_ enables multiple users +`FiftyOne Enterprise `_ enables multiple users to securely collaborate on the same datasets and models, either on-premises or in the cloud, all built on top of the open source FiftyOne workflows that you're already relying on. -FiftyOne Teams is fully backwards-compatible with the +FiftyOne Enterprise is fully backwards-compatible with the `open source project `_, so all other -pages on this site apply to Teams deployments as well. +pages on this site apply to Enterprise deployments as well. |br| @@ -58,19 +58,19 @@ pages on this site apply to Teams deployments as well. .. customcalloutitem:: :header: Overview - :description: What's FiftyOne Teams? We think you'll be glad you asked! + :description: What's FiftyOne Enterprise? We think you'll be glad you asked! :button_text: Learn the basics :button_link: overview.html .. customcalloutitem:: :header: Installation - :description: Learn how to install the FiftyOne Teams Python SDK. + :description: Learn how to install the FiftyOne Enterprise Python SDK. :button_text: Install the SDK :button_link: installation.html .. customcalloutitem:: :header: Cloud-backed media - :description: Integrate FiftyOne Teams with your media stored in the cloud. + :description: Integrate FiftyOne Enterprise with your media stored in the cloud. :button_text: Get started with cloud media :button_link: cloud_media.html @@ -82,38 +82,38 @@ pages on this site apply to Teams deployments as well. .. customcalloutitem:: :header: Dataset Versioning - :description: Explore or revert to historical snapshots of your FiftyOne Teams datasets. + :description: Explore or revert to historical snapshots of your FiftyOne Enterprise datasets. :button_text: Version your FiftyOne datasets :button_link: dataset_versioning.html .. customcalloutitem:: - :header: FiftyOne Teams App - :description: See how you can collaboratively work on datasets in the FiftyOne Teams App. - :button_text: Explore the Teams App + :header: FiftyOne Enterprise App + :description: See how you can collaboratively work on datasets in the FiftyOne Enterprise App. + :button_text: Explore the Enterprise App :button_link: teams_app.html .. customcalloutitem:: :header: Management SDK :description: Learn how to programmatically manage your deployment with the Management SDK. - :button_text: Manage your Teams deployment + :button_text: Manage your Enterprise deployment :button_link: management_sdk.html .. customcalloutitem:: :header: Plugins - :description: Learn how to install and manage shared plugins for your Teams deployment. - :button_text: Get plugins for Teams + :description: Learn how to install and manage shared plugins for your Enterprise deployment. + :button_text: Get plugins for Enterprise :button_link: teams_plugins.html .. customcalloutitem:: :header: Secrets - :description: Safely store and access secrets in your Teams deployment. + :description: Safely store and access secrets in your Enterprise deployment. :button_text: Learn more about secrets :button_link: secrets.html .. customcalloutitem:: :header: Migrations - :description: Learn how to migrate to FiftyOne Teams and manage your Teams deployment. - :button_text: Migrate to Teams + :description: Learn how to migrate to FiftyOne Enterprise and manage your Enterprise deployment. + :button_text: Migrate to Enterprise :button_link: migrations.html .. End callouts --------------------------------------------------------------- @@ -129,7 +129,7 @@ pages on this site apply to Teams deployments as well. Look interesting? `Schedule a demo `_ to get - started with Teams + started with Enterprise .. toctree:: :maxdepth: 1 @@ -141,7 +141,7 @@ pages on this site apply to Teams deployments as well. Cloud-backed media Roles and permissions Dataset Versioning - FiftyOne Teams App + FiftyOne Enterprise App Management SDK Plugins Secrets diff --git a/docs/source/teams/installation.rst b/docs/source/teams/installation.rst index 42a70cc7b8..e45b0a2236 100644 --- a/docs/source/teams/installation.rst +++ b/docs/source/teams/installation.rst @@ -1,21 +1,21 @@ .. _teams-installation: -FiftyOne Teams Installation -=========================== +FiftyOne Enterprise Installation +================================ .. default-role:: code -FiftyOne Teams deployments come with a centralized FiftyOne Teams App and +FiftyOne Enterprise deployments come with a centralized FiftyOne Enterprise App and database that allows your entire team to collaborate securely on the same -datasets. FiftyOne Teams is deployed entirely into your environment, either +datasets. FiftyOne Enterprise is deployed entirely into your environment, either on-premises or in a private cloud. Your data never leaves your environment. -FiftyOne Teams can be deployed on a wide variety of infrastructure solutions, +FiftyOne Enterprise can be deployed on a wide variety of infrastructure solutions, including Kubernetes and Docker. .. note:: - Detailed instructions for the initial FiftyOne Teams deployment, along with + Detailed instructions for the initial FiftyOne Enterprise deployment, along with all necessary components, are made available by your Voxel51 CS engineer during the onboarding process. @@ -24,17 +24,17 @@ including Kubernetes and Docker. Python SDK ---------- -While the :ref:`FiftyOne Teams App ` allows for countless new +While the :ref:`FiftyOne Enterprise App ` allows for countless new App-centric workflows, any existing Python-based workflows that you've fallen in love with in the open-source version of FiftyOne are still directly applicable! -FiftyOne Teams requires an updated Python SDK, which is a wrapper around the +FiftyOne Enterprise requires an updated Python SDK, which is a wrapper around the open-source FiftyOne package that adds new functionality like support for cloud-backed media. You can find the installation instructions under the "Install FiftyOne" section -of the Teams App by clicking on your user icon in the upper right corner: +of the Enterprise App by clicking on your user icon in the upper right corner: .. image:: /images/teams/install_fiftyone.png :alt: install-teams @@ -55,14 +55,14 @@ private PyPI server as shown below: .. note:: - The Teams Python package is named ``fiftyone`` and has the same module + The Enterprise Python package is named ``fiftyone`` and has the same module structure as :doc:`fiftyone <../api/fiftyone>`, so any existing scripts you built using open source will continue to run after you upgrade! Next Steps __________ -After installing the Teams Python SDK in your virtual environment, you'll need +After installing the Enterprise Python SDK in your virtual environment, you'll need to configure two things: * Your team's :ref:`API connection ` or @@ -73,7 +73,7 @@ to configure two things: That's it! Any operations you perform will be stored in a centralized location and will be available to all users with access to the same datasets in the -Teams App or their Python workflows. +Enterprise App or their Python workflows. .. _teams-installation-poetry: @@ -160,10 +160,10 @@ You should then see snippets in the ``pyproject.toml`` file like the following Cloud credentials ----------------- -In order to utilize cloud-backed media functionality of FiftyOne Teams, at +In order to utilize cloud-backed media functionality of FiftyOne Enterprise, at least one cloud source must be configured with proper credentials. Below are instructions for configuring each supported cloud provider for local SDK use -or directly to the Teams containers. An admin can also :ref:`configure +or directly to the Enterprise containers. An admin can also :ref:`configure credentials for use by all app users `. .. _teams-cors: @@ -193,7 +193,7 @@ _________ To work with FiftyOne datasets whose media are stored in Amazon S3, you simply need to provide `AWS credentials `_ -to your Teams client with read access to the relevant objects and buckets. +to your Enterprise client with read access to the relevant objects and buckets. You can do this in any of the following ways: @@ -240,7 +240,7 @@ and the shared credentials file should use .. note:: - FiftyOne Teams requires either the `s3:ListBucket` or + FiftyOne Enterprise requires either the `s3:ListBucket` or `s3:GetBucketLocation` permission in order to access objects in S3 buckets. If you wish to use multi-account credentials, your credentials must have @@ -283,7 +283,7 @@ ____________________ To work with FiftyOne datasets whose media are stored in Google Cloud Storage, you simply need to provide `credentials `_ -to your Teams client with read access to the relevant objects and buckets. +to your Enterprise client with read access to the relevant objects and buckets. You can do this in any of the following ways: @@ -341,7 +341,7 @@ _______________ To work with FiftyOne datasets whose media are stored in Azure Storage, you simply need to provide `Azure credentials `_ -to your Teams client with read access to the relevant objects and containers. +to your Enterprise client with read access to the relevant objects and containers. You can do this in any of the following ways: @@ -456,7 +456,7 @@ _____ To work with FiftyOne datasets whose media are stored in `MinIO `_, you simply need to provide the credentials to your -Teams client with read access to the relevant objects and buckets. +Enterprise client with read access to the relevant objects and buckets. You can do this in any of the following ways: @@ -531,7 +531,7 @@ Extra client arguments ______________________ Configuring credentials following the instructions above is almost always -sufficient for FiftyOne Teams to properly utilize them. In rare cases where the +sufficient for FiftyOne Enterprise to properly utilize them. In rare cases where the cloud provider client needs non-default configuration, you can add extra client kwargs via the :ref:`media cache config `: @@ -565,9 +565,9 @@ Cloud storage page Admins can also configure cloud credentials via the Settings > Cloud storage page. -Credentials configured via this page are stored (encrypted) in the Teams +Credentials configured via this page are stored (encrypted) in the Enterprise database, rather than needing to be configured through environment variables in -your Teams deployment. +your Enterprise deployment. .. note:: @@ -616,17 +616,17 @@ Alternatively, credentials can be updated programmatically with the method in the Management SDK. Any cloud credentials uploaded via this method will automatically be used by -the Teams UI when any user attempts to load media associated with the +the Enterprise UI when any user attempts to load media associated with the appropriate provider or specific bucket. .. note:: - By default, Teams servers refresh their credentials every 120 seconds, so + By default, Enterprise servers refresh their credentials every 120 seconds, so you may need to wait up to two minutes after modifying your credentials via this page in order for the changes to take effect. .. note:: - Users cannot access stored credentials directly, either via the Teams UI or - by using the Teams SDK locally. The credentials are only decrypted and - used internally by the Teams servers. + Users cannot access stored credentials directly, either via the Enterprise UI or + by using the Enterprise SDK locally. The credentials are only decrypted and + used internally by the Enterprise servers. diff --git a/docs/source/teams/management_sdk.rst b/docs/source/teams/management_sdk.rst index 503c07428c..e5bcdc57c5 100644 --- a/docs/source/teams/management_sdk.rst +++ b/docs/source/teams/management_sdk.rst @@ -1,14 +1,14 @@ .. _teams-management-sdk: -Teams Management SDK -==================== +Enterprise Management SDK +========================= .. default-role:: code One of FiftyOne's core design principles is that you should be able to do everything *programmatically* if you want. -To this end, the `fiftyone.management` module provides Teams-specific methods +To this end, the `fiftyone.management` module provides Enterprise-specific methods for managing users, invitations, dataset permissions, plugins, API keys, and more. diff --git a/docs/source/teams/migrations.rst b/docs/source/teams/migrations.rst index cb1323f9bd..54abf441bd 100644 --- a/docs/source/teams/migrations.rst +++ b/docs/source/teams/migrations.rst @@ -5,27 +5,27 @@ Migrations .. default-role:: code -This page describes how to migrate between FiftyOne Teams versions, both for -:ref:`admins ` migrating the core Teams App infrastructure and +This page describes how to migrate between FiftyOne Enterprise versions, both for +:ref:`admins ` migrating the core Enterprise App infrastructure and :ref:`individual users ` who need to install a new -version of the Teams Python SDK. +version of the Enterprise Python SDK. Refer to :ref:`this section ` to see how to migrate -existing datasets from open source to Teams. +existing datasets from open source to Enterprise. .. _teams-upgrade-python-sdk: Upgrading your Python SDK _________________________ -Users can upgrade their FiftyOne Teams Python client to the latest version as +Users can upgrade their FiftyOne Enterprise Python client to the latest version as follows: .. code-block:: shell pip install --index-url https://${TOKEN}@pypi.fiftyone.ai –-upgrade fiftyone -A specific FiftyOne Teams client version can be installed like so: +A specific FiftyOne Enterprise client version can be installed like so: .. code-block:: shell @@ -33,7 +33,7 @@ A specific FiftyOne Teams client version can be installed like so: .. note:: - You can find your `TOKEN` by logging into the FiftyOne Teams App and + You can find your `TOKEN` by logging into the FiftyOne Enterprise App and clicking on the :ref:`account icon ` in the upper right. .. _teams-upgrading: @@ -41,12 +41,12 @@ A specific FiftyOne Teams client version can be installed like so: Upgrading your deployment _________________________ -The basic **admin workflow** for upgrading a FiftyOne Teams deployment is: +The basic **admin workflow** for upgrading a FiftyOne Enterprise deployment is: - :ref:`Upgrade ` all automated services and - individual user workflows that use the Teams Python SDK to an appropriate + individual user workflows that use the Enterprise Python SDK to an appropriate SDK version -- Upgrade your core Teams App infrastructure (via Kubernetes, Docker, etc) +- Upgrade your core Enterprise App infrastructure (via Kubernetes, Docker, etc) - Upgrade your database's version, as described below .. note:: @@ -55,7 +55,7 @@ The basic **admin workflow** for upgrading a FiftyOne Teams deployment is: including compatible SDK versions, deployment assets, and upgrade assistance. -New FiftyOne Teams versions occasionally introduce data model changes that +New FiftyOne Enterprise versions occasionally introduce data model changes that require database migrations when upgrading your deployment. Admins can check a deployment's current version via the Python SDK as shown @@ -77,9 +77,9 @@ below: migration required, but there could be. `Unlike open source FiftyOne `_, -a Teams database is not automatically upgraded when a user connects to the +a Enterprise database is not automatically upgraded when a user connects to the database with a newer Python client version. Instead, an admin must manually -upgrade your Teams database by installing the newest version of the Teams SDK +upgrade your Enterprise database by installing the newest version of the Enterprise SDK locally, assuming admin privileges, and running the command shown below: .. code-block:: shell @@ -103,20 +103,20 @@ locally, assuming admin privileges, and running the command shown below: Downgrading your deployment ___________________________ -Admins can also downgrade their FiftyOne Teams deployment to an older version +Admins can also downgrade their FiftyOne Enterprise deployment to an older version if necessary. The steps are the same as :ref:`when upgrading `, except that you’ll need to know the appropriate database version to migrate down to. Each -version of Teams corresponds to a version of open source FiftyOne called its +version of Enterprise corresponds to a version of open source FiftyOne called its "open source compatibility version", and this versioning system is used to set the database version. -For example, you can downgrade to Teams v0.10 like so: +For example, you can downgrade to Enterprise v0.10 like so: .. code-block:: shell - OS_COMPAT_VERSION=0.18.0 # OS compatibility version for Teams v0.10.0 + OS_COMPAT_VERSION=0.18.0 # OS compatibility version for Enterprise v0.10.0 export FIFTYONE_DATABASE_ADMIN=true fiftyone migrate --all -v ${OS_COMPAT_VERSION} @@ -128,16 +128,16 @@ For example, you can downgrade to Teams v0.10 like so: .. note:: Contact your Voxel51 CS engineer if you need to know the open source - compatibility version for a particular Teams version that you wish to + compatibility version for a particular Enterprise version that you wish to downgrade to. .. _teams-migrating-datasets: -Migrating datasets to Teams -___________________________ +Migrating datasets to Enterprise +________________________________ Any datasets that you have created via open source FiftyOne can be migrated to -your Teams deployment by exporting them in +your Enterprise deployment by exporting them in :ref:`FiftyOneDataset ` format: .. code-block:: python @@ -154,13 +154,13 @@ your Teams deployment by exporting them in export_media=False, ) -and then re-importing them with the Teams SDK connected to your Teams +and then re-importing them with the Enterprise SDK connected to your Enterprise deployment: .. code-block:: python :linenos: - # Teams SDK + # Enterprise SDK import fiftyone as fo dataset = fo.Dataset.from_dir( @@ -170,9 +170,9 @@ deployment: ) Note that you'll need to update any local filepaths to cloud paths in order to -use the dataset in Teams. +use the dataset in Enterprise. -If you need to upload the local media to the cloud, the Teams SDK provides a +If you need to upload the local media to the cloud, the Enterprise SDK provides a builtin utility for this: .. code-block:: python diff --git a/docs/source/teams/overview.rst b/docs/source/teams/overview.rst index 5acba726dd..9dcdd6dc9a 100644 --- a/docs/source/teams/overview.rst +++ b/docs/source/teams/overview.rst @@ -1,31 +1,31 @@ .. _teams-overview: -FiftyOne Teams Overview -======================= +FiftyOne Enterprise Overview +============================ .. default-role:: code -FiftyOne Teams is purpose-built to integrate into your existing ML workflows, +FiftyOne Enterprise is purpose-built to integrate into your existing ML workflows, including annotation, evaluation, model training, and deployment. .. note:: - `Learn more `_ about FiftyOne Teams and + `Learn more `_ about FiftyOne Enterprise and `contact us `_ to try it! .. _fiftyone-vs-fiftyone-teams: -FiftyOne vs FiftyOne Teams -__________________________ +FiftyOne vs FiftyOne Enterprise +_______________________________ -Here's a high-level overview of the capabilities that FiftyOne Teams brings: +Here's a high-level overview of the capabilities that FiftyOne Enterprise brings: .. raw:: html - + @@ -88,7 +88,7 @@ Here's a high-level overview of the capabilities that FiftyOne Teams brings: Backwards compatibility _______________________ -FiftyOne Teams is fully backwards compatible with open-source FiftyOne. This +FiftyOne Enterprise is fully backwards compatible with open-source FiftyOne. This means that all of your pre-existing FiftyOne workflows should be usable without modification. @@ -122,39 +122,39 @@ would with open source FiftyOne: System architecture ___________________ -FiftyOne Teams is implemented as a set of interoperable services, as described +FiftyOne Enterprise is implemented as a set of interoperable services, as described in the figure below. .. image:: /images/teams/teams_architecture.png :alt: teams-architecture :align: center -FiftyOne Teams is strictly a software offering. All relevant hardware is owned +FiftyOne Enterprise is strictly a software offering. All relevant hardware is owned and managed by your organization, whether on-premises or in your virtual private cloud. -**Teams database services** +**Enterprise database services** -The primary storage location for all of the FiftyOne Teams datasets and related +The primary storage location for all of the FiftyOne Enterprise datasets and related metadata (excluding media files) for your organization. -**Teams web service** +**Enterprise web service** An always-on front-end from which you can visually access the datasets in your -FiftyOne Teams deployment. Web-based access is the standard entrypoint for +FiftyOne Enterprise deployment. Web-based access is the standard entrypoint for non-technical users who need point-and-click access to dataset curation and related features, as well as basic workflows for technical users. Most dataset curation and model analysis work by engineers happens via client installations. -**Teams API authentication** +**Enterprise API authentication** -Technical users connecting to FiftyOne Teams via Python or Jupyter notebooks +Technical users connecting to FiftyOne Enterprise via Python or Jupyter notebooks use token-based authentication to make authorized connections to the centralized database storing your Team’s dataset metadata. **Python/notebook users (your organization)** -Similar to FiftyOne, technical users can install the FiftyOne Teams client in +Similar to FiftyOne, technical users can install the FiftyOne Enterprise client in their working environment(s). These clients are configured to use the centralized database service and will additionally serve their own App instances (like open source FiftyOne) so that engineers can work locally, @@ -162,24 +162,24 @@ remotely, and in Jupyter notebooks. **Web users (your organization)** -FiftyOne Teams provides an always-on login portal at +FiftyOne Enterprise provides an always-on login portal at ``https://.fiftyone.ai`` that users can login to from any browser for web-only workflows. **Data lake (your organization)** -FiftyOne Teams does not require duplication or control over how your source -media files are stored. Instead, FiftyOne Teams stores references (e.g., cloud +FiftyOne Enterprise does not require duplication or control over how your source +media files are stored. Instead, FiftyOne Enterprise stores references (e.g., cloud object URLs or network storage paths) to the media in your datasets, thereby minimizing storage costs and providing you the flexibility to provision your -object storage as you see fit. FiftyOne Teams has full support for cloud, +object storage as you see fit. FiftyOne Enterprise has full support for cloud, network, and local media storage. **User authentication (your organization)** -FiftyOne Teams can be configured to work with your organization’s +FiftyOne Enterprise can be configured to work with your organization’s authentication and authorization systems, enabling you to manage access to -FiftyOne Teams using your existing OAuth stack. FiftyOne Teams supports SAML +FiftyOne Enterprise using your existing OAuth stack. FiftyOne Enterprise supports SAML 2.0 and OAuth 2.0. .. _security-considerations: @@ -187,18 +187,18 @@ FiftyOne Teams using your existing OAuth stack. FiftyOne Teams supports SAML Security considerations _______________________ -FiftyOne Teams relies on your organization's existing security infrastructure. -No user accounts are created specifically for FiftyOne Teams; we integrate +FiftyOne Enterprise relies on your organization's existing security infrastructure. +No user accounts are created specifically for FiftyOne Enterprise; we integrate directly with your OAuth system. -Usage of the FiftyOne Teams client by technical users of your organization is +Usage of the FiftyOne Enterprise client by technical users of your organization is also secure. All database access is managed by the central authentication service, and self-hosted App instances can be configured to only accept connections from known servers (e.g., only localhost connections). In remote client workflows, users are instructed how to configure ssh tunneling to securely access self-hosted App instances. -No outside network access is required to operate FiftyOne Teams. Voxel51 only +No outside network access is required to operate FiftyOne Enterprise. Voxel51 only requests the ability to (a) access the system logs for usage tracking and auditing purposes, and (b) access the system at the customer’s request to provide technical support. We are flexible in the mechanisms used to accomplish diff --git a/docs/source/teams/pluggable_auth.md b/docs/source/teams/pluggable_auth.md index 585e8fc657..de07d60ae6 100644 --- a/docs/source/teams/pluggable_auth.md +++ b/docs/source/teams/pluggable_auth.md @@ -2,12 +2,12 @@ # Pluggable Authentication -FiftyOne Teams v1.6.0 introduces Pluggable Authentication that provides the -Central Authentication Service (CAS). CAS is a self-contained authentication -system with two modes (`legacy` and `internal`). Legacy mode uses Auth0. -Internal mode eliminates the Auth0 external dependency and may run in -environments without egress to the internet. CAS provides a UI, REST API, and -JavaScript (JS) Hook mechanism to manage FiftyOne Teams user data and +FiftyOne Enterprise v1.6.0 introduces Pluggable Authentication that provides +the Central Authentication Service (CAS). CAS is a self-contained +authentication system with two modes (`legacy` and `internal`). Legacy mode +uses Auth0. Internal mode eliminates the Auth0 external dependency and may run +in environments without egress to the internet. CAS provides a UI, REST API, +and JavaScript (JS) Hook mechanism to manage FiftyOne Enterprise user data and authentication. ## FiftyOne Authentication Modes @@ -19,10 +19,10 @@ The setting `FIFTYONE_AUTH_MODE` specifies the authentication mode `legacy` or ### Legacy Mode -In legacy mode, FiftyOne Teams uses Auth0 for user authentication and +In legacy mode, FiftyOne Enterprise uses Auth0 for user authentication and authorization. This mode requires an external connection to Auth0 endpoints. User data is eventually consistent (where changes are reflected across -FiftyOneTeams eventually). Auth0 contains the configuration for identity +FiftyOneEnterprise eventually). Auth0 contains the configuration for identity providers and the persistence of user data. Auth0 supports multiple providers (including SAML). For the supported IdPs, see [Auth0 Enterprise Identity Providers](https://auth0.com/docs/authenticate/identity-providers/enterprise-identity-providers). @@ -31,12 +31,12 @@ providers and the persistence of user data. Auth0 supports multiple providers ### Internal Mode -In internal mode, FiftyOne Teams the CAS replaces Auth0. FiftyOne Teams will -not require network egress to external services. User data is immediately -consistent (where changes are reflected across FiftyOne Teams instantly). -Directory data is immediately written to MongoDB, and organizations have the -autonomy to manage their Identity Provider Configuration. Internal mode -supports +In internal mode, FiftyOne Enterprise the CAS replaces Auth0. FiftyOne +Enterprise will not require network egress to external services. User data is +immediately consistent (where changes are reflected across FiftyOne Enterprise +instantly). Directory data is immediately written to MongoDB, and organizations +have the autonomy to manage their Identity Provider Configuration. Internal +mode supports [OpenID Connect (OIDC)](https://openid.net/developers/discover-openid-and-openid-connect/) and [OAuth2](https://oauth.net/2/). @@ -52,8 +52,8 @@ and [OAuth2](https://oauth.net/2/). ![Super Admin UI](/images/teams/cas/cas_api_docs.png) -The Super Admin UI contains FiftyOne Teams deployment wide configurations. When -logging into FiftyOne Teams as an admin, you are in the context of an +The Super Admin UI contains FiftyOne Enterprise deployment wide configurations. +When logging into FiftyOne Enterprise as an admin, you are in the context of an organization. Settings are scoped by organization and only apply to that organization. The Super Admin UI allows you to administer all organizations and global configurations (Identity Providers, Session timeouts, and JS hooks). @@ -121,7 +121,7 @@ API to ensure a comprehensive transfer of information. For each user, the migration involves several steps: -1. Creating a FiftyOne Teams user profile via `POST /cas/api/users`. +1. Creating a FiftyOne Enterprise user profile via `POST /cas/api/users`. 1. Assigning the user to the default organization through a membership entry. 1. Linking the user's account to the new authentication provider by creating an account reference via `POST /cas/api/accounts`. @@ -133,7 +133,7 @@ Mode, completing the migration process. ## Getting Started with Internal Mode -These steps are only required to run FiftyOne Teams in +These steps are only required to run FiftyOne Enterprise in [internal mode](#internal-mode). Please skip when using Auth0 in [legacy mode](#legacy-mode). @@ -168,10 +168,10 @@ These steps are only required to run FiftyOne Teams in ## Syncing with 3rd Party Directories (Open Directory, LDAP, and Active Directory) -Below is an example of how to use JavaScript hooks to sync FiftyOne Teams with -a corporate directory (such as Open Directory, LDAP, or Active Directory) via -an intermediary REST API or Identity Provider. The recommended setup is with -OAuth/OIDC claims, however the example below illustrates a more intricate +Below is an example of how to use JavaScript hooks to sync FiftyOne Enterprise +with a corporate directory (such as Open Directory, LDAP, or Active Directory) +via an intermediary REST API or Identity Provider. The recommended setup is +with OAuth/OIDC claims, however the example below illustrates a more intricate integration. This example specifically addresses a scenario in which additional actions are diff --git a/docs/source/teams/roles_and_permissions.rst b/docs/source/teams/roles_and_permissions.rst index 5b72a27396..c165df1069 100644 --- a/docs/source/teams/roles_and_permissions.rst +++ b/docs/source/teams/roles_and_permissions.rst @@ -5,27 +5,27 @@ Roles and permissions .. default-role:: code -FiftyOne Teams is built for collaboration, with the goal of making it as easy +FiftyOne Enterprise is built for collaboration, with the goal of making it as easy as possible for engineers, data scientists, and stakeholders to work together to build high quality datasets and computer vision models. -Accordingly, FiftyOne Teams gives you the flexibility to configure user roles, +Accordingly, FiftyOne Enterprise gives you the flexibility to configure user roles, user groups and fine-grained permissions so that you can safely and securely collaborate both inside and outside your organization at all stages of your workflows. This page introduces the basic roles and permissions available in -FiftyOne Teams. +FiftyOne Enterprise. .. _teams-roles: Roles _____ -FiftyOne Teams has four user roles: Admin, Member, Collaborator, and Guest. +FiftyOne Enterprise has four user roles: Admin, Member, Collaborator, and Guest. Admins can access user management features by clicking on their account icon in -the upper-right of the FiftyOne Teams App and navigating to the +the upper-right of the FiftyOne Enterprise App and navigating to the "Settings > Team > Users" page: .. image:: /images/teams/admin_team_users_page.png @@ -102,7 +102,7 @@ view other users of the deployment. Groups ------ -User groups in FiftyOne Teams allow organization admins to manage a collection +User groups in FiftyOne Enterprise allow organization admins to manage a collection of users as a single entity. This simplifies the process of assigning permissions to multiple users, making it more efficient to control access to datasets. @@ -139,9 +139,9 @@ ___________ Admins and users with the **Can manage** permission on a dataset can configure a dataset's permissions under the dataset's -:ref:`Manage tab ` in the FiftyOne Teams App. +:ref:`Manage tab ` in the FiftyOne Enterprise App. -In FiftyOne Teams, dataset permissions for a user are determined by both the +In FiftyOne Enterprise, dataset permissions for a user are determined by both the access they receive from their groups' permissions and individual permissions assigned to them. @@ -218,7 +218,7 @@ The following permissions are available to each user role: Authorized users can use the "Grant access" workflow to give **Can view** , **Can tag**, or **Can edit** access to a dataset to an email address that - is not yet user of a FiftyOne Teams deployment. + is not yet user of a FiftyOne Enterprise deployment. When the invitation is accepted, the user will become a Guest if the **Can view** permission is chosen or a Collaborator if a higher permission diff --git a/docs/source/teams/secrets.rst b/docs/source/teams/secrets.rst index 5122320845..ddb26d55f0 100644 --- a/docs/source/teams/secrets.rst +++ b/docs/source/teams/secrets.rst @@ -1,20 +1,20 @@ .. _teams-secrets: -FiftyOne Teams Secrets -====================== +FiftyOne Enterprise Secrets +=========================== .. default-role:: code -FiftyOne Teams provides a Secrets interface for storing sensitive information +FiftyOne Enterprise provides a Secrets interface for storing sensitive information such as API tokens and login credentials in a secure manner for use by your :ref:`Team's plugins `. -Managing secrets through the Teams App is a straightforward and secure way to +Managing secrets through the Enterprise App is a straightforward and secure way to configure connections to and integrations with external services and APIs such as GCP, OpenAI, CVAT, etc without the need to change the configuration or -environment variables of your FiftyOne Teams containers and restarting them. +environment variables of your FiftyOne Enterprise containers and restarting them. Instead, you can simply add or remove secrets using the -:ref:`Teams UI ` and they will immediately be available +:ref:`Enterprise UI ` and they will immediately be available to any plugins that require them. .. _teams-adding-secrets: @@ -22,7 +22,7 @@ to any plugins that require them. Adding secrets -------------- -Admins can add, configure, and remove secrets in the FiftyOne Teams App by +Admins can add, configure, and remove secrets in the FiftyOne Enterprise App by navigating to the Secrets Management page under Settings > Secrets: .. image:: /images/teams/secrets_page.png @@ -89,8 +89,8 @@ values of any environment variables whose name matches a secret key declared by a plugin. Therefore, a plugin written using the above pattern can run in all of the following environments with no code changes: -- A FiftyOne Teams deployment that uses the Secrets interface -- A FiftyOne Teams deployment that injects secrets directly as environment +- A FiftyOne Enterprise deployment that uses the Secrets interface +- A FiftyOne Enterprise deployment that injects secrets directly as environment variables -- A locally launched App via the Teams SDK +- A locally launched App via the Enterprise SDK - Open source FiftyOne diff --git a/docs/source/teams/teams_app.rst b/docs/source/teams/teams_app.rst index ae4d9abfb7..2ecdd4be19 100644 --- a/docs/source/teams/teams_app.rst +++ b/docs/source/teams/teams_app.rst @@ -1,24 +1,24 @@ .. _teams-app: -FiftyOne Teams App -================== +FiftyOne Enterprise App +======================= .. default-role:: code -The FiftyOne Teams App allows you to visualize, browse, and interact with your +The FiftyOne Enterprise App allows you to visualize, browse, and interact with your individual datasets like you can with the :ref:`FiftyOne App `, but with expanded features for organizing, permissionsing, versioning, and sharing your team's datasets, all from a centralized web portal. This page provides a brief overview of some features available only in the -FiftyOne Teams App. +FiftyOne Enterprise App. .. _teams-homepage: The homepage ____________ -When you login to the FiftyOne Teams App, you'll land on the homepage pictured +When you login to the FiftyOne Enterprise App, you'll land on the homepage pictured below. In the top bar of this page, on the left side, the gray number next to @@ -28,7 +28,7 @@ buttons at the bottom of the page to see different batches of datasets. .. note:: - You can return to the homepage from any page of the Teams App by clicking on + You can return to the homepage from any page of the Enterprise App by clicking on the Voxel51 logo in the upper left corner. .. image:: /images/teams/homepage.png @@ -126,7 +126,7 @@ description, and tags for the dataset: .. note:: - What next? Use the :ref:`Teams Python SDK ` to upload new + What next? Use the :ref:`Enterprise Python SDK ` to upload new samples, labels, and metadata to your dataset. A common approach is to automate this process via :ref:`cloud functions `. @@ -154,7 +154,7 @@ just as you would via the :ref:`FiftyOne App `. Managing a dataset __________________ -The FiftyOne Teams App provides a number of options for managing existing +The FiftyOne Enterprise App provides a number of options for managing existing datasets, as described below. You can access these options from the :ref:`Samples tab ` @@ -167,7 +167,7 @@ right hand side of a row of the dataset listing table and selecting .. note:: - Did you know? You can also use the :ref:`Teams SDK ` to + Did you know? You can also use the :ref:`Enterprise SDK ` to programmatically, create, edit, and delete datasets. .. _teams-dataset-basic-info: @@ -213,7 +213,7 @@ The "Danger zone" tab is only accessible to users with :ref:`Can manage ` permissions on the dataset. From this tab, you can select "Delete entire dataset" to permanently delete a -dataset from your Teams deployment. You must type the dataset's full name in +dataset from your Enterprise deployment. You must type the dataset's full name in the modal to confirm this action. .. image:: /images/teams/dataset_danger_zone.png diff --git a/docs/source/teams/teams_plugins.rst b/docs/source/teams/teams_plugins.rst index bc6289c9f4..47fc593b07 100644 --- a/docs/source/teams/teams_plugins.rst +++ b/docs/source/teams/teams_plugins.rst @@ -1,13 +1,13 @@ .. _teams-plugins: -FiftyOne Teams Plugins -====================== +FiftyOne Enterprise Plugins +=========================== .. default-role:: code -FiftyOne Teams provides native support for installing and running +FiftyOne Enterprise provides native support for installing and running :ref:`FiftyOne plugins `, which offers powerful opportunities -to extend and customize the functionality of your Teams deployment to suit your +to extend and customize the functionality of your Enterprise deployment to suit your needs. .. note:: @@ -17,7 +17,7 @@ needs. examples, then check out the `FiftyOne plugins `_ repository for a growing collection of prebuilt plugins that you can add to - your Teams deployment! + your Enterprise deployment! .. _teams-plugins-page: @@ -25,7 +25,7 @@ Plugins page ____________ Admins can use the plugins page to upload, manage, and configure permissions -for plugins that are made available to users of your Teams deployment. +for plugins that are made available to users of your Enterprise deployment. Admins can access the plugins page under Settings > Plugins. It displays a list of all installed plugins and their operators, as well as the enablement @@ -40,15 +40,15 @@ and permissions of each. Installing a plugin ___________________ -Admins can install plugins via the Teams UI or Management SDK. +Admins can install plugins via the Enterprise UI or Management SDK. .. note:: A plugin is a directory (or ZIP of it) that contains a top-level ``fiftyone.yml`` file. -Teams UI --------- +Enterprise UI +------------- To install a plugin, click the "Install plugin" button on the plugins page. @@ -90,10 +90,10 @@ the Management SDK: Upgrading a plugin __________________ -Admins can upgrade plugins at any time through the Teams UI or Management SDK. +Admins can upgrade plugins at any time through the Enterprise UI or Management SDK. -Teams UI --------- +Enterprise UI +------------- To upgrade a plugin, click the plugin's dropdown and select "Upgrade plugin". @@ -141,7 +141,7 @@ the Management SDK with the `overwrite=True` option: Uninstalling a plugin _____________________ -Admins can uninstall plugins at any time through the Teams UI or Management +Admins can uninstall plugins at any time through the Enterprise UI or Management SDK. .. note:: @@ -150,8 +150,8 @@ SDK. :ref:`enable/disable plugins ` rather than permanently uninstalling them. -Teams UI --------- +Enterprise UI +------------- To uninstall a plugin, click the plugin's dropdown and select "Uninstall plugin". @@ -179,10 +179,10 @@ the Management SDK: Enabling/disabling plugins __________________________ -Teams UI ---------- +Enterprise UI +------------- -When plugins are first installed into Teams, they are enabled by default, along +When plugins are first installed into Enterprise, they are enabled by default, along with any operators they contain. Admins can enable/disable a plugin and all of its operators by toggling the @@ -244,8 +244,8 @@ within them via any combination of the permissions described below: | | on a particular dataset. | +-------------------------------+----------------------------------------------------------------------------+ -Teams UI --------- +Enterprise UI +------------- To configure the permissions for an operator, first click on the plugin's operators link. @@ -319,8 +319,8 @@ By default, the initial permissions are: | Minimum Dataset Permission | Edit | +-------------------------------+---------------+ -Teams UI -^^^^^^^^ +Enterprise UI +^^^^^^^^^^^^^ Default operator permissions can be configured by navigating to the page at Settings > Security and looking under the Plugins header. Click the dropdown @@ -356,17 +356,17 @@ ____________________ FiftyOne's plugin framework that allows users to schedule tasks from within the App that are executed on a connected workflow orchestrator like Apache Airflow. -With FiftyOne Teams, your team can +With FiftyOne Enterprise, your team can :ref:`upload and permission ` custom operations that your -users can execute from the Teams App, all of which run against a central +users can execute from the Enterprise App, all of which run against a central orchestrator :ref:`configured by ` your admins. Why is this awesome? Your AI stack needs a flexible data-centric component that enables you to organize and compute on your data. With delegated operations, -FiftyOne Teams becomes both a dataset management/visualization tool and a +FiftyOne Enterprise becomes both a dataset management/visualization tool and a workflow automation tool that defines how your data-centric workflows like ingestion, curation, and evaluation are performed. In short, think of FiftyOne -Teams as the single source of truth on which you co-develop your data and +Enterprise as the single source of truth on which you co-develop your data and models together. What can delegated operations do for you? Get started by installing any of @@ -432,7 +432,7 @@ and their status. Setting up an orchestrator __________________________ -All delegated operations that have been scheduled by users of a FiftyOne Teams +All delegated operations that have been scheduled by users of a FiftyOne Enterprise deployment will remain queued until a connected orchestrator picks them up and executes them. @@ -443,7 +443,7 @@ executes them. development environment. Want to run delegated operations at scale? Contact your Voxel51 support - team to discuss adding a production-grade cluster to your FiftyOne Teams + team to discuss adding a production-grade cluster to your FiftyOne Enterprise deployment. To set up Airflow as an orchestrator to run delegated operations, you will need @@ -454,7 +454,7 @@ to: - Install `Apache Airflow `_ on the VM -- Install the appropriate version of the FiftyOne Teams SDK for the Teams +- Install the appropriate version of the FiftyOne Enterprise SDK for the Enterprise deployment that you are connecting to - Ensure that your :ref:`team's plugins ` are available to the Orchestrator, either by installing them on the same machine or by @@ -494,7 +494,7 @@ configurations, see :ref:`Configuring FiftyOne `. .. note:: Refer to :ref:`this section ` for more - information on media caching and access in FiftyOne Teams. Make sure that + information on media caching and access in FiftyOne Enterprise. Make sure that cloud storage permissions are configured if some operators will access media. @@ -648,7 +648,7 @@ the appropriate values for your deployment. export FIFTYONE_PLUGINS_DIR=... # eg /mnt/nfs/shared/plugins # - # Copy the values below from your Teams deployment + # Copy the values below from your Enterprise deployment # # Provide your encryption key so the orchestrator can access secrets @@ -700,7 +700,7 @@ still run a check and all runs should be green. Managing delegated operations _____________________________ -Every Teams dataset has a Runs page that allows users to monitor and explore +Every Enterprise dataset has a Runs page that allows users to monitor and explore delegated operations scheduled against that dataset. .. note:: diff --git a/docs/source/user_guide/config.rst b/docs/source/user_guide/config.rst index 4a09cb3b1c..ec949b93c5 100644 --- a/docs/source/user_guide/config.rst +++ b/docs/source/user_guide/config.rst @@ -63,7 +63,7 @@ FiftyOne supports the configuration options described below: | | | | | | | | | `latency` is the default, which uses a dynamic batch size to achieve a target latency | | | | | of `batcher_target_latency` between calls. The default changes to `size` for the | -| | | | FiftyOne Teams SDK in :ref:`API connection mode `, which targets | +| | | | FiftyOne Enterprise SDK in :ref:`API connection mode `, which targets | | | | | a size of `batcher_target_size_bytes` for each call. `static` uses a fixed batch size | | | | | of `batcher_static_size`. | +-------------------------------+-------------------------------------+-------------------------------+----------------------------------------------------------------------------------------+

FiftyOne Teams

FiftyOne Enterprise

FiftyOne