How-to's


Creating Tenant-Specific Theme CSS Files for Designer Portals

The tenant_theme.css file contains any additional customizations that alter the look and feel of the default portal frame and features.

To ensure that the symbolic IBFS Path in the main portal connects to the tenant_theme.css file for every tenant, you must save it in the Hidden_Content folder of each tenant workspace and include this folder in the full symbolic IBFS path. You must also use the same name for each tenant workspace theme file, tenant_theme.css.

You can use the text editor to create a .css file and enter the classes you wish to add or modify directly.

Assigning Customized Logos to Tenant Workspaces for Designer Portals

The symbolic path defined in the Logo field of the centralized portal directs the call for a logo image to a customized logo file in the workspace of the user who issued the request to run the portal.

In order for this link to work successfully, each tenant workspace must contain its own logo file in the Images subfolder of the Hidden_Content folder within the tenant workspace.

Each logo image file must use the same name as the logo file identified in the Logo field of the centralized portal, “logo."

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.

Publishing Content

When the portal is ready and all tenant workspaces and tenant workspace groups are prepared, you must make the portal and related workspaces available by changing them to Published status to make the portal and its contents available to all users with their appropriate level of access.