Assigning access to a service

Procedure to assign access to multiple namespaces of a service.

Procedure

  1. In the navigation bar, click Library > Services. The Manage service library is displayed.
  2. In the overflow menu of the service, click Assign access.
  3. In the Assign access dialog box, select the namespaces. You can select a single or multiple namespaces to which the user has access.
  4. Click Assign.

Scenarios

  • You can set or change a single or multiple valid namespaces to a service. The valid namespaces are those which the user has access to.
  • A change in service namespace reflects in all its versions too.
  • A service with multiple namespaces can be deployed only in any of the user accessible namespaces to which a service belongs.
    • Example: A service S belongs to namespaces N1, N2, and N3. User U has access to N2, N3, N4. Allowed namespaces for deployment are N2 and N3.
  • For a service, removal (multiple namespaces), change (single namespace) or add (Global to single or multiple namespaces) is allowed if the namespace of the associated service instance is present in the new namespace list.
    • Example 1: If service S1 (globally accessible) is deployed in namespaces N1 and N2 (one service instance in N1 and one in N2) then you can allow to update the namespaces of S1 only if it includes N1 and N2. That is, S1 can be updated to N1 and N2 but not to N2 and N3.
    • Example 2: If a service instance SI of service S is deployed in namespace N2, then service S won't be allowed to change namespaces from N1, N2, and N3 to N1 and N3, removing N2 until service instance SI is deleted.
  • Cloud connections, shared parameters, and templates should either be global in nature or of a namespace to which a service belongs (service instance, in the case of SMTP connection).

Note: It is recommended to avoid composing a service with multiple namespaces that has templates or cloud connections from multiple namespaces. Even though the service belongs to multiple namespaces, it can be deployed in only one namespace and the activities by using or belonging to other namespaces fail.