Supervisely
AboutAPI ReferenceSDK Reference
  • 🤖What's Supervisely
  • 🚀Ecosystem of Supervisely Apps
  • 💡FAQ
  • 📌Getting started
    • How to import
    • How to annotate
    • How to invite team members
    • How to connect agents
    • How to train models
  • 🔁Import and Export
    • Import
      • Overview
      • Import using Web UI
      • Supported annotation formats
        • Images
          • 🤖Supervisely JSON
          • 🤖Supervisely Blob
          • COCO
          • Yolo
          • Pascal VOC
          • Cityscapes
          • Images with PNG masks
          • Links from CSV, TXT and TSV
          • PDF files to images
          • Multiview images
          • Multispectral images
          • Medical 2D images
          • LabelMe
          • LabelStudio
          • Fisheye
          • High Color Depth
        • Videos
          • Supervisely
        • Pointclouds
          • Supervisely
          • .PCD, .PLY, .LAS, .LAZ pointclouds
          • Lyft
          • nuScenes
          • KITTI 3D
        • Pointcloud Episodes
          • Supervisely
          • .PCD, .PLY, .LAS, .LAZ pointclouds
          • Lyft
          • nuScenes
          • KITTI 360
        • Volumes
          • Supervisely
          • .NRRD, .DCM volumes
          • NIfTI
      • Import sample dataset
      • Import into an existing dataset
      • Import using Team Files
      • Import from Cloud
      • Import using API & SDK
      • Import using agent
    • Migrations
      • Roboflow to Supervisely
      • Labelbox to Supervisely
      • V7 to Supervisely
      • CVAT to Supervisely
    • Export
  • 📂Data Organization
    • Core concepts
    • Project and Dataset
      • Create
      • Data Structure
      • Define Classes & Tags
      • Gallery & Table views
      • Collections
      • Quality Assurance & Statistics
        • Practical applications of statistics
    • MLOps Workflow
    • Team Files
    • Disk usage & Cleanup
    • Operations with Data
      • Data Filtration
        • How to use advanced filters
      • Pipelines
      • Augmentations
      • Splitting data
      • Converting data
        • Convert to COCO
        • Convert to YOLO
        • Convert to Pascal VOC
    • Data Commander
      • Clone Project Meta
  • 📝Labeling
    • Labeling Toolboxes
      • Images
      • Videos 2.0
      • Videos 3.0
      • 3D Point Clouds
      • DICOM
      • Multiview images
      • Fisheye
    • Labeling Tools
      • Navigation & Selection Tools
      • Point Tool
      • Bounding Box (Rectangle) Tool
      • Polyline Tool
      • Polygon Tool
      • Brush Tool
      • Mask Pen Tool
      • Smart Tool
      • Graph (Keypoints) Tool
      • Frame-based tagging
    • Labeling Jobs
      • Labeling Queues
      • Labeling Consensus
      • Labeling Statistics
    • Labeling Performance
    • Labeling with AI-Assistance
  • 🤝Collaboration
    • Admin panel
      • Users management
      • Teams management
      • Server disk usage
      • Server trash bin
      • Server cleanup
      • Server stats and errors
    • Teams & workspaces
    • Members
    • Issues
    • Guides & exams
    • Activity log
    • Sharing
  • 🖥️Agents
    • Installation
      • Linux
      • Windows
      • AMI AWS
      • Kubernetes
    • How agents work
    • Restart and delete agents
    • Status and monitoring
    • Storage and cleanup
    • Integration with Docker
  • 🔮Neural Networks
    • Overview
    • Inference & Deployment
      • Overview
      • Supervisely Serving Apps
      • Deploy & Predict with Supervisely SDK
      • Using trained models outside of Supervisely
    • Model Evaluation Benchmark
      • Object Detection
      • Instance Segmentation
      • Semantic Segmentation
      • Custom Benchmark Integration
    • Custom Model Integration
      • Overview
      • Custom Inference
      • Custom Training
    • Solutions
      • Temporal Action Localization with MVD
    • Legacy
      • Starting with Neural Networks
      • Train custom Neural Networks
      • Run pre-trained models
  • 👔Enterprise Edition
    • Get Supervisely
      • Installation
      • Post-installation
      • Upgrade
      • License Update
    • Kubernetes
      • Overview
      • Installation
      • Connect cluster
    • Advanced Tuning
      • HTTPS
      • Remote Storage
      • Single Sign-On (SSO)
      • CDN
      • Notifications
      • Moving Instance
      • Generating Troubleshoot Archive
      • Storage Cleanup
      • Private Apps
      • Data Folder
      • Firewall
      • HTTP Proxy
      • Offline usage
      • Multi-disk usage
      • Managed Postgres
      • Scalability Tuning
  • 🔧Customization and Integration
    • Supervisely .JSON Format
      • Project Structure
      • Project Meta: Classes, Tags, Settings
      • Tags
      • Objects
      • Single-Image Annotation
      • Single-Video Annotation
      • Point Cloud Episodes
      • Volumes Annotation
    • Developer Portal
    • SDK
    • API
  • 💡Resources
    • Changelog
    • GitHub
    • Blog
    • Ecosystem
Powered by GitBook
On this page
  • Teams and Workspaces
  • Projects and Datasets
  • Version Control

Was this helpful?

  1. Data Organization
  2. Project and Dataset

Data Structure

This article explains the Data structure in Supervisely, including how Projects, Datasets, and Files are organized in Team and Workspace. Learn how to navigate, manage, and structure your data.

PreviousCreateNextDefine Classes & Tags

Last updated 15 hours ago

Was this helpful?

Teams and Workspaces

1. Automatic Creation at Registration

When a user registers on the Supervisely platform, one Team and one Workspace are automatically created in their account. By default, this workspace is named First Workspace.

2. Team & Workspace Structure Rules

Each Team must always have at least one Workspace, although it doesn't have to be the original one created at registration.

3. Creating & Managing Teams

A Member with the Admin role can invite other Members to their Team, as shown in the scheme above of Member 2 and Member 3. In addition to their default Team, a Member can also create new Teams to collaborate on separate projects or with different groups.

4. Switching Between Teams

To manage or switch between Teams, click the arrow next to the name of your current Team. A menu will appear with a list of all Teams you are a member of (not necessarily the ones you created) along with other settings.

Projects and Datasets

Inside a Workspace, a Member can create an unlimited number of Projects. Each Project can contain multiple Datasets, which store the actual data and annotations.

This flexible structure allows Members to organize data in a way that fits their workflow, as shown in the scheme above of Member 2 and Member 3.

Furthermore, a Member can create additional Workspaces inside any Team where they have the Admin role. Inside a Dataset, you can create Sub-Datasets, enabling flexible and deeply nested data structures — just like folders and subfolders on your computer. There are no limitations on nesting depth, so you can organize your data in whatever hierarchy makes sense for your workflow.

Let’s repeat an important rule: at the Project level, you cannot store files directly — only Datasets can exist there. Files and Sub-Datasets can only be added inside a Dataset.

You can think of Datasets as folders and Sub-Datasets as subfolders. This allows you to recreate complex directory structures exactly the way you organize data on your local machine or in your company’s cloud storage. It’s especially useful if you’re working with a shared storage system that already follows a specific hierarchy — you can mirror that same structure inside Supervisely without restrictions.

To create a sub-dataset inside an existing dataset:

  1. Click the Add button

  2. Select Create New Dataset Then, you can navigate into the newly created sub-dataset and upload your files there.

Great! Your sub-dataset with files is now ready.

Version Control

The platform includes version control features, allowing your team to track changes and revisions to documents, ensuring transparency and accountability.

Project versions are created automatically when training tools are run, but you can also create versions manually at any time.

Every Member with is always a part of at least one Team — the personal Team created during registration. A member may leave or delete a personal Team, provided that they remain associated with at least one Team that includes at least one Workspace at all times. This structure is illustrated in the scheme for Member 1.

When you to your Team, make sure you have the correct Team selected as active. The invitations will be sent specifically to the currently active Team that you created.

📂
Full-scope Permission
invite other Members