Project-level isolation
The workspace is tied to a specific specialist and project rather than shared as a general-purpose environment.
Secure cloud workspace
Keep external CAD work inside a controlled project environment.
The selected specialist gets the licensed CAD applications and your project files in one controlled environment, with restricted transfer paths — so production work happens in that workspace rather than on a personal machine.
Each secure cloud workspace is tied to a specific project and specialist, with managed identity, restricted file movement and a controlled output path.
PROJECT-SPECIFIC CAD ENVIRONMENT
Secure cloud workspaceLicensed applications and project files stay inside the controlled environment
Managed identityControlled file movementEphemeral lifecycleControlled delivery
THE SHORT ANSWER
How does the secure cloud workspace reduce file and access risk?
The specialist works inside a project-specific cloud desktop instead of downloading CAD data to a personal device. Applications, identity, session records and output delivery are managed around the project, creating a narrower and more consistent path for external production work.
Verified controls
Concrete safeguards, built into the workflow.
These controls shape how specialists access applications, use project data and return completed outputs.
Controlled file movement
Direct local file transfer, outbound file uploads and clipboard transfer between local and remote environments are disabled.
Ephemeral lifecycle
The cloud workspace follows an ephemeral lifecycle, with new specialist credentials generated for subsequent sessions.
Session-linked identity
Each session is tied to a user, project, start time and end time using per-session specialist credentials.
Encrypted storage and transport
Project data is encrypted at rest and in transit, with U.S.-based project storage and isolated backups.
Customer access roles
Organization Owner / Admin and Project Owner roles support customer-side access governance.
Data flow
One path in, one path out, and a record of both.
Normal internet access remains available for work, while direct outbound uploads and local transfer paths are blocked. Delivery is handled through the project workflow.
Client sourceApproved project input
Secure workspaceProject-isolated execution
Client outputControlled delivery
Workspace lifecycle
Access follows the project from qualification to delivery.
1Project qualified
2Identity assigned
3Workspace provisioned
4Session recorded
5Outputs delivered
6Workspace lifecycle ends
Security designed around the project
Know the data path before production starts.
The project setup aligns files, applications, access roles and delivery with the actual CAD workflow, so the selected specialist starts in the right environment from day one.
PROJECT SETUP COVERS
Source and output delivery paths
Application and version requirements
Customer-system access, where needed
Project roles and workspace configuration
FAQ
Security and the secure cloud workspace.
Where are project files stored?+
Project files are stored in the United States, encrypted at rest and in transit, with isolated backups. Project configuration is confirmed during scoping.
Can a specialist download files to a personal computer?+
Direct local file transfer is disabled. Production takes place inside the secure cloud workspace and outputs follow the controlled project delivery path.
Is internet access disabled?+
No. Internet access remains available for normal work, while direct outbound file uploads and local file-transfer paths are blocked.
Can the secure cloud workspace access our PDM or PLM?+
Where technically and commercially feasible, controlled access may be configured using an assigned project identity. Specific system compatibility is qualified before it is promised.
How are project-specific controls confirmed?+
During scoping, Giga Techspace confirms the source and output paths, application requirements, workspace roles and any customer-system access needed for the package.
READY WHEN YOU ARE
Keep the project, CAD tools and delivery path together.
Define one real production task and see how it can run inside a project-specific secure cloud workspace.