--- title: "Customizing the Team Portal Look and Feel" slug: "customizing-the-virtual-portal-look-and-feel-2-1-1" tags: ["Portal"] updated: 2026-11-09T08:12:14Z published: 2026-11-09T08:12:14Z canonical: "kb.ctera.com/customizing-the-virtual-portal-look-and-feel-2-1-1" --- > ## Documentation Index > Fetch the complete documentation index at: https://kb.ctera.com/llms.txt > Use this file to discover all available pages before exploring further. # Customizing the Team Portal Look and Feel If you want to change the portal look and feel you can do the following: - Change the color scheme for an individual team portal. - Customize the portal skin by changing objects in the default skin. Customizing a skin should only be performed with CTERA support. After a skin has been customized you can upload it to the portal and set it as the default skin. ## Managing the Portal Colors You can define the portal colors for both the administration and end user views for a specific portal in the view for that portal. You can change the color scheme for both the portal administration view and end user view. **Note** You cannot define the colors for a team portal in the team portal administration. **To define the portal color scheme:** 1. For a specific team portal, in the view for that team portal, select **Settings > Palette Generator** in the navigation pane. The **Palette Generator** page is displayed. ![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-7XVLQY2F.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A34%3A36Z&se=2026-11-11T05%3A34%3A36Z&sr=c&sp=r&sig=aUQHTt5Qa%2F7EDpQaQ0tcu7pvu5VtIq67hATugLNY9h0%3D) The color scheme is separated into the following areas under both the **Administration Palette** and **End User Palette** views: In addition, the **Grid Colors** option, which determines table colors, is displayed in the **End User Palette** view. Clicking an item in one of these areas displays the current color in an editable format and to what the item applies to. - **Brand Colors**, which determine the color for the main menu items in the navigation menu, as well as action icons and buttons. - **Additional Colors**, which determine message colors. - **Layout Colors**, which determine the general page layout colors. - **Text Colors**, which determine the text colors. 2. Choose the view to change: **Administration Palette** or **End User Palette**. 3. Click the item to change the color and enter the HTML color code you want for that item. 4. Click **Preview** to preview the new color scheme. ![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-JK05FRNQ.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A34%3A36Z&se=2026-11-11T05%3A34%3A36Z&sr=c&sp=r&sig=aUQHTt5Qa%2F7EDpQaQ0tcu7pvu5VtIq67hATugLNY9h0%3D) Click **Cancel** in the preview and then if you do not like the changes, click **Reset to defaults** in the **Palette Generator** page to undo all your changes. 5. Once you are satisfied with the color scheme, click **Download**. **Note** If you leave the **Palette Generator** page after making a color change, you will no longer be able to reset it to the default colors. For the **Administration Palette**, a *config.json* file is downloaded. For the **End User Palette**, a *skins.css* file is downloaded. Use the file as part of the skin for your portal, as described in [Managing a Portal Skin](/v1/docs/customizing-the-virtual-portal-look-and-feel-2-1-1#managing-a-portal-skin). ## Managing a Portal Skin You can upload a default skin for all the portals in the global administration view or for a specific team portal in the view for that portal. **Note** You can get a basic skin from CTERA support. The skin file has an extension **.skin**. **To change a skin to include a new color scheme:** 1. Create the file with the desired color scheme as described in [Managing the Portal Colors](/v1/docs/customizing-the-virtual-portal-look-and-feel-2-1-1#managing-the-portal-colors). 2. Change the extension of the **.skin** file you want to use to **.zip** 3. For the administration view, replace the *config.json* file in the zip with downloaded *config.json* file. 4. For the end user view, replace the *skins.css* in the endUser/css folder in the zip with the downloaded *skins.css* file. 5. To upload the updated skin file, first change the zip file's extension back to **.skin**. 6. Upload the skin file to the portal and set it as the default. **Note** You must **not** change the name of the skin file. In coordination with CTERA support you can make other changes to the skin as described in [CTERA Portal Customization Guidelines](/v1/docs/ctera-portal-customization-guidelines). **To upload a skin to the portal:** 1. For all portals, in the global administration view, or for a specific team portal, in the view for the team portal, select **Settings > Skins** in the navigation pane. The **Skins** page is displayed. For example, in the global administration view: ![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-89VJOBC5.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A34%3A36Z&se=2026-11-11T05%3A34%3A36Z&sr=c&sp=r&sig=aUQHTt5Qa%2F7EDpQaQ0tcu7pvu5VtIq67hATugLNY9h0%3D) 2. Click **Upload skin** and browse to the skin received from CTERA support. 3. Select the file with the extension **.skin** and click **Open**. The selected skin is uploaded. ![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-K43ZKQPB.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A34%3A36Z&se=2026-11-11T05%3A34%3A36Z&sr=c&sp=r&sig=aUQHTt5Qa%2F7EDpQaQ0tcu7pvu5VtIq67hATugLNY9h0%3D) **Note** You can also download a skin from the portal to make changes. CTERA recommends only doing this in coordination with CTERA support. **To make a skin the default skin:** 1. For all portals in the global administration view, or for a specific team portal, in the view for the team portal: Select **Settings > Skins** in the navigation pane. The **Skins** page is displayed. 2. Select the row of the skin to use as the default and click **Set as Default**. ![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-9GC8V3WL.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A34%3A36Z&se=2026-11-11T05%3A34%3A36Z&sr=c&sp=r&sig=aUQHTt5Qa%2F7EDpQaQ0tcu7pvu5VtIq67hATugLNY9h0%3D) The selected skin becomes the default skin. `Default Skin` is displayed under the skin name and the icon changes to ![image.png](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-UR5YJ5N9.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A34%3A36Z&se=2026-11-11T05%3A34%3A36Z&sr=c&sp=r&sig=aUQHTt5Qa%2F7EDpQaQ0tcu7pvu5VtIq67hATugLNY9h0%3D). 3. Refresh the portal page. The default skin cannot be deleted. **To remove a skin from being the default:** 1. For all portals in the global administration view, or for a specific team portal, in the view for the team portal: Select **Settings > Skins** in the navigation pane. The **Skins** page is displayed. 2. Select the row of the default skin and click **Remove Default**. 3. Refresh the portal page. **To delete a skin that is not the default skin:** 1. For all portals, in the global administration view or for a specific team portal, in the view for the team portal, select **Settings > Skins** in the navigation pane. The **Skins** page is displayed. 2. Select the row of the skin to delete and click **Delete**. A confirmation window is displayed. 3. Click **Delete** to confirm. The skin is deleted.