Product documentation
Citrix SecurSpaces™
View PDF

Concepts

August 19, 2026

Citrix SecurSpaces™ is arranged as four nested levels. Almost everything in this documentation — permissions, resources, security settings — is defined at one of them and applies to everything beneath.

Platform
└── Organization
    └── Project
        └── Workspace
<!--NeedCopy-->

The four levels

Level What it is Who works at this level
Platform The deployment as a whole, and the baseline for everything in it Platform administrators, security officers
Organization A group of projects, usually a business unit or customer Organization owners
Project A team, with its members, resources, and security rules Project owners
Workspace A single containerized development environment Developers

Why the nesting matters

Two things follow from the hierarchy, and they explain most of what you will see in the interface.

Settings are inherited. A setting made at a broader level applies to everything beneath it. A narrower level can usually override it, unless the broader level enforces the value. Some settings work the other way: remote development over SSH must be allowed at every level above, so a project owner cannot enable it if the platform has it switched off. See Workspace policy.

Roles are project bound. The same person can hold a different role in each project they belong to. What they can see and change depends on the role they hold there, not on a single account-wide setting. See Roles and permissions.

If a page, button, or setting described in this documentation is not visible to you, the usual reason is one of these two: your role does not carry the permission, or a broader level has fixed the setting.

Concepts
August 19, 2026
August 19, 2026

In this article

Site feedback | Your privacy choices footer linkYour Privacy Choices | Privacy and legal terms | Cookie preferences | Consent settings | docs.cloud.com
© 1999- Cloud Software Group, Inc. All rights reserved.