Associating security zones with other objects

To associate a security zone with a business object or group, specify the security zone in either a POST or a PATCH.

For example, the following request PATCHes BillingCenter account bc:101 so that it is associated with security zone bc:222.

PATCH /billing/v1/accounts/bc:101

{
  "data": {
    "attributes": {
        "securityZone": {
            "id": "bc:222"
        }
    }
  }
}

Similarly, the following request PATCHes BillingCenter group bc:555 so that it is associated with security zone bc:222.

PATCH /admin/v1/groups/bc:555

{
  "data": {
    "attributes": {
        "securityZone": {
            "id": "bc:222"
        }
    }
  }
}

As a result of the two queries in the previous examples, account bc:101 is now restricted to only users in group bc:555.

Support for security zones in Cloud API business objects

In order to associate a business object with a security zone, the corresponding Cloud API resource must have a securityZone field. For each InsuranceSuite application, there may be business object that can be associated with security zones, but the corresponding resource in Cloud API does not have a securityZone field. In these circumstances, you can extend the resource to include the securityZone field. For information, see the Cloud API Developer Guide.