-
-
How to install and use JetBrains IntelliJ Gateway as a Citrix published application
-
Use Citrix Secure Access and Citrix Secure Developer Spaces with VS Code
-
Configure AI Gateway routing in Citrix Secure Developer Spaces
-
Configure external MongoDB with X.509 authentication in Citrix Secure Developer Spaces
-
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Workspace templates
This article describes workspace templates in Citrix SecurSpaces™ Flex: what they are, how they work, and how to create and manage them. For workspace size options and credit consumption, contact your Citrix sales team.
What is a workspace template?
A workspace template is the primary deployment artifact in Citrix SecurSpaces Flex. It defines the environment that a developer receives when they start a workspace.
A workspace template includes:
- Container image — The base Linux container image with preinstalled tools, runtimes, and configuration.
- Preinstalled tools — Languages, SDKs, CLIs, and development tools baked into the image.
- Resource limits — Maximum vCPU and RAM the workspace is allowed to consume (separate from the workspace size profile; used to set hard limits within a compute tier).
- Access controls — Which users or user groups can launch workspaces from this template.
- Startup scripts — Scripts that run at workspace initialization: cloning repositories, configuring dotfiles, mounting secrets, or running setup commands.
What the customer owns
The customer owns and hosts the container image. Citrix does not provide or manage the container image content. The customer is responsible for:
- Building and maintaining the container image.
- Hosting the image in a container registry accessible from the Citrix SecurSpaces execution plane (for example, Azure Container Registry, Docker Hub, or a private registry).
- Patching and updating the image as needed.
Citrix scans the container image for known vulnerabilities when a workspace is launched. Scan results are surfaced to the administrator in the Citrix SecurSpaces console.
Decoupled size and template
Workspace size and workspace template are configured independently. A single template can be paired with any workspace size (Light, Medium, or Heavy) on demand. This means:
- You do not need a separate template per compute tier.
- Developers can switch workspace sizes without requiring a new template.
- Platform engineering teams can standardize on a small number of templates and let workspace size vary by workload.
Create a workspace template
To create a workspace template, you must have the Administrator role in the Citrix SecurSpaces console.
- Sign in to your SecurSpaces environment at your organization’s access URL (for example,
https://yourcompany.flex.sds.citrix.com). - Go to Administration > Workspace Templates.
- Select Create template.
- Complete the template configuration:
| Field | Description |
|---|---|
| Name | A descriptive name for the template (for example, backend-java-21 or data-platform). |
| Description | Optional. A short description shown to administrators. |
| Container image | The full image reference including registry, image name, and tag (for example, myregistry.azurecr.io/dev-image:latest). |
| Resource limits | Optional. Maximum vCPU and RAM limits for workspaces created from this template. |
| Startup script | Optional. A shell script that runs at workspace initialization. |
| Access | The users or groups permitted to launch workspaces from this template. |
- Select Save to create the template.
The template is now available for workspace creation and is listed on the Workspace Templates page.
Update a workspace template
Updating a template changes the configuration for new workspaces created from it. Existing running workspaces are not affected until they are restarted.
- Go to Administration > Workspace Templates.
- Select the template you want to update.
- Edit the relevant fields.
- Select Save.
Note:
If you update the container image tag (for example, from
v1.0tov1.1), new workspaces will use the updated image. Developers with running workspaces must stop and restart their workspace to pick up the new image.
Template versioning
Workspace templates support versioning. Each saved version of a template is recorded. Administrators can:
- View the version history of a template.
- Roll back to a previous version if a new image or configuration causes issues.
Delete a workspace template
Deleting a template removes it from the available template list. Existing running workspaces that were created from the deleted template continue to run until they are stopped.
- Go to Administration > Workspace Templates.
- Select the template you want to delete.
- Select Delete.
- Confirm the deletion in the dialog.
More information
- Platform Flex credit consumption
- Network connections
- Technical security overview
- Workspace templates in Citrix SecurSpaces (self-hosted) — for workspace template concepts that apply to both deployment models
Share
Share
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.