Understanding the Configuration Requirements for Collaborative Portals That Use Multiple Themes or Logos


The configuration of a Collaborative Portal that supports multiple SaaS Tenant groups with varying themes and logos is a multiphase process that requires the creation of tenant workspaces for each tenant group and a separate workspace for the content portal.

As a best practice, we recommend that you use the following workflow when creating a Multi-SaaS Tenant portal using symbolic IBFS paths.

  1. Have an administrator create the workspaces you will need.
    • You need a SaaS tenant workspace for each group that must use a different theme or logo.
    • You also need a separate workspace to contain the centralized portal that will be accessible to all tenant users.
    • For more information, see the How to Create a Workspace on the WebFOCUS Home Page topic in the Security and Administration technical content. 
  2. Have an administrator or group administrator assign a sample user to each security group.
    • Assign users in each tenant group to the workspace for that tenant. Assign users to the security group whose range of privileges most closely matches their responsibilities.
    • Assign all users to the same security group in the workspace that supports the portal.
    • For more information, see the How to Add a User to a Group topic in the Security and Administration technical content.
  3. Create a Portal Page and a CSS Theme file for each tenant workspace.
    • Create tenant-specific portal pages for each tenant group that requires them within each tenant workspace.
    • Create a file named tenant_theme.css that contains classes that define the unique theme for each tenant.
    • Enter the .bip-logo class in the tenant_theme.css file and identify the address of the tenant workspace logo file in the background-image property.
    • Save the tenant_theme.css file in the Hidden_Content folder of the tenant workspace.
  4. Assign a logo file to each tenant workspace.
    • In the Hidden_Content folder, create a sub-folder entitled Images.
    • Create a logo file for each tenant and place it in the Hidden_Content/Images folder for each tenant workspace.
  5. Create a centralized portal that includes a symbolic path for Tenant-Theme.css files.
    • Create the portal in a common workspace  available to all.
    • Enter the IBFS Symbolic Path to the tenant-theme.css file using the ##{WF_PrimaryGroup} variable in the Custom Theme CSS field of the centralized portal.
    • Ensure that the tenant_theme.css file identifies the location of the logo file for that workstation.
    • Because you are using IBFS paths that point to the same location in each different workspace, ensure that you use the same location and file name for the logo and theme files in each tenant workspace.
  6. Add Linked Tenant Portal Pages to the Centralized Portal.
    • Add any individual tenant pages to the centralized portal for those tenants that require them.
  7. Publish Content.
    • Publish the centralized portal and the workspace that contains it.
    • Publish all individual tenant workspaces.
  8. Test Portals.
    • Sign in as a user from each tenant group and run the portal.
    • Ensure that the logo, styling, and tenant-specific pages are appropriate.
    • Ensure that common pages are available and conform to tenant-specific styling.
  9. Have an administrator or group administrator assign all remaining users to security groups.
    • Assign all users in each tenant group to the workspace for that tenant. Assign users to the security group whose range of privileges most closely matches their responsibilities.
    • Assign all users to the corresponding security group in the workspace that contains the portal.
    • For more information about assigning or mapping users to groups, see the Security and Administration technical content.