📂Use Ellipsis Drive to ingest client data

Ellipsis Drive can be used as a controlled ingestion layer for external or client-owned spatial data.

This enables users or customers to upload, manage, and use their own datasets within your application or platform for visualisation, data fusion, and analytics.

You can implement this in two ways:

• by Connecting Ellipsis Drive to your platform

• or by using Ellipsis Drive as a white-labelled data management layer with your own UI/UX

---

Recommended implementation structure

A common implementation pattern is to structure data per client or user using folders.

Step 1: Create a folder per client

Create a dedicated folder for each client or user.

Store the corresponding folder IDs in your backend to manage access mapping.

---

Step 2: Generate access tokens per session

When a user logs in, generate an access token scoped to the relevant folder(s).

Choose an appropriate access level based on the required permissions.

Access levels are documented separately.

---

Step 3: Use the API to interact with data

Pass the token and folder context to your application to enable operations such as:

• uploading datasets

• listing folders and layers

• displaying spatial data

• managing client-specific content

---

Integration vs platform connection

You can either:

• Integrate Ellipsis Drive into your backend → full control over authentication, logic, and data flows

• Connect Ellipsis Drive to your platform → leverage existing UI components and reduce implementation overhead