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

The configuration of a Designer 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 enterprise 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 tenant workspace.
   • You need one sample user assigned to the top-level security group for each tenant workspace. The tenant workspace group must be defined as the primary group for each user.
   • Each sample tenant user must also be assigned to the Advanced Users 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 CSS Theme file for each tenant workspace.
   • Create a file named tenant_theme.css that contains classes that define the unique theme for each tenant.
   • 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.
   • Publish the Images folder and the logo file.
5. Create any required tenant-specific portal pages for each tenant workspace.
   • Develop all content for the tenant-specific portal page within the tenant workspace. The use of content or data sources contained in other workspaces adds an extra group to the configuration that conflicts with the ability of the product to work with ##{WF_PrimaryGroup}.
   • Create and publish tenant-specific portal pages for each tenant group that requires them within their tenant workspace.
   • Create a shortcut for each portal page within the tenant workspace.
6. Create a centralized portal that includes a symbolic path for tenant-theme.css files and logo image files.
   • Develop all content for centralized portal pages within the centralized portal workspace. The use of content or data sources contained in other workspaces adds an extra group to the configuration that conflicts with the ability of the product to work with ##{WF_PrimaryGroup}.
   • Create the portal in a enterprise workspace available to all.
   • Enter the IBFS symbolic path to the tenant_theme.css file using the ##{WF_PrimaryGroup} variable in the Theme field of the centralized portal.
   • Enter the IBFS symbolic path to the logo image file in the Logo field of the centralized portal.
   • Because you are using IBFS paths that point to the same location in each different workspace, ensure that you use the same location for the logo file and theme file in each tenant workspace.
7. Add Linked Tenant Portal Pages to the Centralized Portal.
   • Copy and paste the shortcuts of tenant-specific pages that you created earlier to the centralized portal workspace.
8. Publish Content.
   • Publish the centralized portal and all of its contents.
   • Ensure that content in all individual tenant workspaces is published.
9. 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.
10. Have an administrator or group administrator assign all remaining users to security groups.
    • Assign the users in each tenant group to the top-level security group for that tenant workspace.
    • Assign all users to the same security group in the workspace that supports the portal.
    • For more information about assigning or mapping users to groups, see the Security and Administration technical content.