User Interface Impact

This article contains the following topics:
casm1401
This article contains the following topics:
Installing the multi-tenancy feature changes the user interface, depending on the authorization and tenant access that is associated with the user role. The changes affect both tenant users and service provider users.
Tenant Users
If the role of a user is restricted to a single tenant and the user is not an administrator, substitute a custom tenant logo for the default CA Technologies logo on all pages. Substitution depends on whether a logo is defined on the Tenant Detail page for the tenant.
For non-administrator tenant users, the user interface menu items or buttons allowing update or edit are suppressed for public objects. The tenant users are not authorized to update the public object.
Tenant Administrators
List pages for these objects automatically include a Public column specifying whether the list row is public data. In addition, the first element in the search filter is a Public Data drop-down list containing the following selections:
  • Include (default)
  • Exclude
  • Only
A tenant administrator with access to multiple tenants sees a Tenant column on list pages for any tenanted object. This column takes the place of the Public column in lists of tenant optional tables.
Users with View access to a Tenant Group
A user role allows view access to multiple tenants.
  • Untenanted objects
    Untenanted objects contain only public data. The service provider user is allowed to create or update an untenanted object only if their role has Update Public authorization. If not, the UI suppresses menu items or buttons allowing update or edit, such as the Edit button itself, or the Create New button on a list page. Tenant users cannot update public objects, and these users never see an Edit or Create New button on a list page for an untenanted object.
  • Tenant-required objects
    Tenant-required objects contain only data associated with a particular tenant. List forms for these objects automatically include a Tenant column after the last link column. In addition, the search filter contains a tenant selector allowing the user to restrict a list to a single tenant.
  • Tenant-optional objects
    Tenant-optional objects contain both public and tenant-specific data. List forms for these objects automatically include a Tenant column (a blank tenant indicates a public object). In addition, the search filter contains both a tenant selector and a Public Data drop-down list (the same one seen by tenant administrators).
If tenant required tables incorrectly contains untenanted data in a multi-tenancy system, a public data drop-down list appears in tenant required tables. The following message: “AHD05358 is displayed. There were untenanted active xxx objects at Service Desk startup.”
Users with Update Access to Multiple Tenants
If a user role allows access to multiple tenants, or a service provider user role has Update Public authorization (typical for an analyst that works for a service provider), detail pages change as follows:
  • Untenanted objects
    Untenanted objects contain only public data. There are no changes to their detail pages for a service provider user with Update Public authorization. If the user is in a role without Update Public authorization, or does not belong to the service provider, read-only pages for untenanted objects are with no Edit button.
  • Existing Tenant-required objects
    Tenant-required objects contain only data that are associated with a particular tenant. Detail pages for existing tenant-required object show the object tenant as part of the standard page header.
  • Tenant-optional objects
    Tenant-optional objects contain both public and tenant-specific data. The detail page for these objects depends on whether the user belongs to the service provider and is in a role with Update Public authorization:
    • If a service provider user role has Update Public authorization, the detail page is the same as that for tenant-required objects.
    • If the user role does not have Update Public authorization, or the user does not belong to the service provider, detail pages for public objects do not have an Edit button. Other detail pages are the same as those for tenant-required objects.