Workspace visibility

Say you have an AWS security ruleset. Your AWS workspaces should see it; your Azure and Google Cloud workspaces should not. A workspace property lets you make that distinction.

New to properties? Start with the hands-on Properties guide to see how workspace values connect to rulesets.

1. Describe your workspaces

In Settings → Properties, create a single-select property named cloud with three options: aws, azure, and google-cloud. Assign the appropriate value to each workspace.

The property is the question: which cloud does this workspace use? Its value is the answer: aws, for example.

2. Choose who can see the ruleset

Open the ruleset and choose Edit. Under Enforcement → Workspaces, choose Edit to open Workspace scope. Choose Matching conditions and set the condition to cloud is aws.

A condition checks a workspace’s property value. In this case, AWS workspaces match; the others do not.

Try it

Change the cloud provider below and watch the matching workspaces update. These are sample workspaces, so you can experiment freely.

Workspace scope

2 of 6 workspaces match
WorkspacecloudenvironmentAvailability
PaymentsawsproductionAvailable
Payments sandboxawsdevelopmentAvailable
Customer portalazureproductionNot available
Portal sandboxazuredevelopmentNot available
Analyticsgoogle-cloudproductionNot available
Analytics sandboxgoogle-clouddevelopmentNot available

3. Combine conditions with a group

Now imagine a ruleset for production workspaces on AWS or Azure. You need two things to be true:

  • The workspace’s environment is production.
  • Its cloud is either AWS or Azure.

In the example above:

  1. Change the first condition to environment is production.
  2. Choose Add → Group.
  3. Set the group’s rows to cloud is aws and cloud is azure.
  4. Keep the outer AND and the group’s OR.

The outer AND requires both the production condition and the group to match. Inside the group, OR accepts either cloud provider.

Try changing the group to AND. With AWS and Azure selected, the result is zero: a single-select cloud property cannot have both values at once. Switch back to OR to accept either one.

That is what groups are for: combining an either/or choice with another requirement.

In the real editor, Add → Condition adds a check, and Add → Group adds a group. Use Add condition inside a group to place a check in that group.

4. Preview, then save

Open Preview in the editor to inspect your actual workspaces. Search by name or filter matching and non-matching results. Complete every condition before interpreting the count: an unfinished condition shows zero until it can be checked.

Choose Save changes when the results look right. Editing conditions does not change visibility until you save.

To make the ruleset visible everywhere, choose All workspaces. No conditions are needed. Removing individual conditions can expand or narrow visibility depending on how they are combined, so preview again before saving.

Visibility controls where a ruleset is available. Enforcement is a separate setting: an Optional ruleset can be turned on or off by a workspace where it is visible, and a Required one is always on there.