Your enterprise has workspaces on AWS, Azure, and Google Cloud. You want each workspace to see the right cloud security ruleset. Start with a property called cloud.
A property defines what you can record. A workspace value records the answer for one workspace. A ruleset condition checks that answer to decide whether the workspace can see the ruleset.
Open Settings → Properties and choose Add property. Set:
| Field | Example |
|---|---|
| Name | cloud |
| Type | Single select |
| Description | Which cloud provider hosts this workspace? |
| Values | aws, azure, google-cloud |
| Requirement | Optional |
| Who can assign values | Enterprise managers |
Use lowercase letters, numbers, and dashes for names and values. The description is optional, but a short question helps the person assigning a value.
Choose Create property. For an optional property, workspaces start with the value Not set. You can assign workspace values after creation or do that later.
For this example, set Payments to aws, Customer portal to azure, and Analytics to google-cloud.
You are choosing from the property's allowed values, not creating a separate property for every workspace. Changing Payments to azure changes Payments' answer; it does not rename the aws option or change another workspace.
In the example below, each cloud has a ruleset with a condition such as cloud is aws.
aws to azure. It now sees Azure security; the AWS count falls and the Azure count rises.One property, different workspace values
Sample data only. Nothing is saved.
awsazuregoogle-cloudThese are the allowed values. Choose one for each workspace below.
| Workspace | Property value | Visible ruleset |
|---|---|---|
| Payments | AWS security | |
| Customer portal | Azure security | |
| Analytics | Google Cloud security |
Ruleset visibility
Each ruleset checks the same cloud property.
| Ruleset | Condition | Matching workspaces |
|---|---|---|
| AWS security | cloud is aws | |
| Azure security | cloud is azure | |
| Google Cloud security | cloud is google-cloud |
The example uses sample data and updates immediately. In your workspace, review and save the assignment to apply the change.
Open AWS security → Edit. Under Enforcement → Workspaces, choose Edit to open Workspace scope:
Repeat with azure or google-cloud for the other cloud-specific rulesets. Defining or assigning a property alone does not restrict a ruleset; the ruleset must reference it in a condition.
For production workspaces on either AWS or Azure, combine environment and cloud using a group. The workspace visibility guide walks through that example interactively.
Single select fits cloud when each workspace has one provider. Use Multi select when a workspace can use several providers, or True/false for a true/false property such as internet-facing. The available ruleset operators follow the type.
Optional lets workspaces leave the property Not set. Required means every workspace must have a value for this property. Choose a default for a required property; it is automatically set for new workspaces. Review the impact before saving requirement changes.
Who can assign values controls who can set the property on workspaces. Choose Enterprise managers for centralized control, or Enterprise and workspace managers so workspace managers can also assign values on workspaces they manage. This setting does not grant permission to edit the property's allowed options.
Open the property’s Usage tab to see workspace assignments and ruleset conditions that reference it. This is useful before changing values or removing the property.
Archiving an option prevents new assignments and conditions from selecting it. Existing assignments and conditions keep working. Deleting a property removes its workspace values and referencing conditions; review the confirmation's workspace and ruleset impact before proceeding.
When deleting a connected property, the confirmation shows each ruleset's condition before and after deletion, along with which workspaces gain or lose visibility. Other conditions and their AND/OR logic stay in place. If no conditions remain, the ruleset becomes visible to all workspaces. Deleting these connections requires permission to approve ruleset changes as well as permission to manage properties.