Workspaces

Collaborative SDV Studio workspaces for connected-vehicle engineering — built for OEM engineering teams, and the students and educators training tomorrow's automotive engineers.

Log in

No account?

Members of

EmailRole

A role change takes effect on the member's next request — the cached role is dropped in the same call, not left to expire.

Asset

Overview

Type
Owner
Availability
Your access
Sharing

Versions a published version is never rewritten

VersionContentPublished

Where it is installed in your workspaces

WorkspaceVersionAddedContent

Removing it from a Workspace takes the content out of that Workspace only. The Asset, its versions and everyone else's copies are untouched.

Add to workspace

Required components the pinned versions this Flow needs in order to run

NodeTypeVersionClass ContentRunnable

Run readiness the check the backend runs before any run

Checks that you may view the Flow, read every node it depends on, and hold a licence for every paid one. Nothing is dispatched and nothing runs — this answers "would a run be allowed?", not "did it run".

Access

Suggestions are people you already share a workspace with. Sharing with a workspace gives each member no more than their own role there allows, and sharing never changes the owner.

WhoKindLevel
Advanced
Asset ID
Owner principal ID
asset_type
classification
permission

Versions

VersionVersion IDGit commit

Access

WhoPrincipal IDLevel

Offers

ForOffer IDStatus

Record a version number without content

A catalogue entry only — it cannot be added to a workspace. Publish from a workspace to release content.

Duplicate

The copy is a new asset that you own, private on arrival. Free shareable dependencies come with it; paid ones stay references and still need their own entitlement to run — buying a Flow's node is not the same as being handed it.

Workspace details —

About

Type

Description

Workspace ID

Identifies the Workspace resource.

…

Workspace Principal ID

Use this ID when sharing Assets with the Workspace, or when issuing a Team licence to it.

…

Run log retention

How long this Workspace keeps execution logs, and how much storage they may use. Older logs are removed automatically; the run history record of each execution always remains.

Usage: —

Container registry access

The credential this Workspace's cluster namespace pulls container images with. Private images (for example under ghcr.io/autonxt-ai) need one; without it, deployments fail with ImagePullBackOff.

—

For ghcr.io, a token with the read:packages scope. It is checked against the registry before it is saved, and never displayed again.

Archive

It disappears from your active list and anyone it was shared with loses access immediately. Published versions, licences already sold and the audit trail are all kept — this is not an erase.

Confirm purchase