Managing spaces

Navigate to the space list by clicking Spaces in the main menu. This shows a list of all the spaces in the environment, listed in a tree.

You can click the space name or edit button image0 to navigate to the details page for the space, or click the add button image1 to add a new space as a child of that space.

Adding a space

To add a new space, do one of the following:

  1. On the space list page, find the parent of the new space and click the image2 button beside its name.
  2. On the space page for the parent, click the “Add child space” button.

Both these methods lead to the form for creating a space as a child of the selected space. Complete the form on the Space tab and click “Save”. When creating a new space, only the Space tab is shown. After saving the space, the other tabs are shown.

Take care to create spaces under the correct parent. Existing spaces cannot be moved to a new parent.

Viewing or updating a space

To view or update a space, navigate to the list page and click the name of the space or the image3 button beside its name. This opens the space page with these tabs:

  • Space: core fields about the space, including the name, key, and settings that control whether the space is allowed to use resources such as aggregators and QoS profiles from its parent.
  • IPs: IP networks allocated by this space or delegated to this space from its parent
  • Private WAN: inbound and outbound traffic rules for this space, used only if private WAN is enabled
  • Branding: options controlling the appearance of the web application for users in this space
  • Support: technical support contact information shown to users in child spaces
  • Statistics: information about this space, including how much downtime has been prevented by SD-WAN, growth rates, and historical charts
  • Node setup: offers links to customized ISOs and offers options for generating the customized ISOs

Space fields

Users assigned to a space can view this information about their space if they have the “view space” permission, but cannot edit it even if they have the “change space” permission. Only users assigned to the parent space or another ancestor can change the fields on this tab for a given space.

Name

The name of the space—usually the name of the partner company, reseller, or end-user company.

Key

A short string that uniquely identifies the space (1-6 lowercase alphanumeric characters). This is used in node hostnames, ISO filenames, and other places where a short descriptor with only alphanumeric characters is needed.

CRM ID

An optional identifier or URL for this customer from the managing partner or reseller’s customer relationship management software

Use QoS profiles from parent space

If checked, bonds in the space can be assigned to any QoS profile in the parent space. If this is not checked when the space is created, a default QoS profile is created in the space.

Use classification profiles from parent space

If checked, bonds in the space can be assigned to any classification profile in the parent space.

Use flow collectors from parent space

If checked, bonds in the space can be assigned to any flow collector in the parent space.

Use aggregators from parent space

If checked, bonds in the space can be assigned to any aggregator in the parent space. If this is not checked, an aggregator must be created within this space before any bonds can be created.

This field should be enabled for spaces for end-user companies that don’t host their own aggregators, and disabled for spaces for large resellers or end-user companies that host their own aggregators.

Use mobile providers from parent space

If checked, mobile broadband legs on bonds in the space can be assigned to any mobile broadband provider profile in the parent space.

Use routing groups from parent space

If checked, aggregators and private WAN routers in the space can be assigned to routing groups in the parent space. If this is not checked when the space is created, a default routing group is created in the space.

This field should be enabled for spaces for resellers that use the same datacentres as those used by their parent space, and disabled for spaces for large resellers or end-user companies that have their own datacentres.

Create ISOs

If checked, ISOs used for provisioning nodes are created for the space. If this is unchecked for a space, nodes can still be provisioned in the space but they will need to use the ISOs made for an ancestor space, and the default root passwords will match that of the space whose ISO was used to provision the nodes.

Deleting a space

To delete a space, navigate to its page and click the Delete button. Accept the confirmation and say “goodbye” to the space.

Spaces can be deleted only if they have no bonds, aggregators, routing groups, child spaces, or other resources.