Create a portal
Create a portal for users to browse company resources, discover articles, and get help.
Before you begin
Role required: admin or sp_admin
Procedure
Navigate to All > Service Portal > Portals, then click New.
On the form, fill in the fields.
| Property | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Title | Name to define your portal. In the browser header and for bookmarks, the title appears as `| URL suffix | Value that appears appended to an instance URL when you access a portal. For example, if you use | sp, the instance URL for that portal would be <instance name>.service-now.com/sp. Ensure that this value is unique and is not the same as any other portal. Note: Avoid using reserved words in your URL to prevent errors when navigating to your portal page. Avoid words such as portal and cms. Also avoid any JavaScript protected terms.Homepage | Page that users see first after they sign in. | KB home page | Custom home page that users see when they go to a knowledge base. | Login page | Custom page to authenticate users. | Logo | Logo that appears in the page header. You can also configure the logo in the Branding Editor. | Icon | Icon that appears in the address bar for your portal. Each portal that you create can have a different icon. | Default | Portal to use as your main portal. | Application | Application scope of the portal. This field is uneditable and Global by default. | 404 page | Default page that your users see whenever a page cannot load properly. You can also define a default 404 page using the glide.service_portal.default_404_page system property. | Catalog home page | Custom page to represent the Service Catalog. | Catalog category home page | Page to display catalog categories in the portal. | Main menu | Reference to the menu in the Instances with Menu \[sp\_instance\_menu\] table that appears in the header. | Theme | Refers to a theme in the Themes \[sp\_theme\] table that defines the style and branding for the portal. The theme is the lowest level of style configuration. Any changes made in the Branding Editor or to specific portal components \(such as widget or container CSS\) override those styles. | Inactive | Turn off access to a portal that you no longer want users to visit and optionally redirect them to another portal. For more information, see Deactivate a portal. | Quick start config | Schema that defines configuration items in the Branding Editor. In JSON format, you can define the fields and records used to generate your branding options. ```json [{ "tagline": { "table" : "sp_instance", "sys_id" : "34fe3d96cb20020000f8d856634c9cf4", "field" : "title" }, "hero_background": { "table" : "sp_container", "sys_id" : "be98a8d2cb20020000f8d856634c9c63", "field" : "background_image" } }] ``` | CSS variables | Portal-specific Sass variables. You can overwrite existing theme variables here.Note: Use the CSS variables field to define CSS variables only. Use CSS Includes to define CSS rules. As of the Madrid release, Sass and LESS can be used within CSS Includes. | Hide portal name | Option to hide the portal name in the page title. | Support right-to-left languages | Option to mirror the direction of the portal when the session language is a right-to-left language, such as Hebrew. Selecting this option automatically generates the necessary CSS but you can also provide your own CSS for right-to-left languages that overrides the auto-generated CSS. To provide your own CSS for right-to-left languages, see Create a portal theme. For more information about support for right-to-left languages, see Styling for right-to-left languages in portals. | Use portal-specific authentication | Option to set authentication for each portal. Selecting this option configures and applies portal-specific authentication for a portal. For example, set an authentication method, such as OKTA, for an internal employee portal, and set a different authentication method for an external vendor portal without having to customize the authentication. | Enable local login | Option to enable a local login. | Portal Identity Providers | Identity provider options: Okta and Microsoft Azure. If both options are selected, then both login options are present in the login page. If only one portal identity provider is configured, the user is directed to the login page for that provider. | Enable favorites | Option to enable the My favorites functionality in the portal.- Displays the favorite icon ( Image omitted: favorite.png - Displays the My Favorites menu item in the portal header. This menu item displays a list of all catalog items or KB articles that are bookmarked for quick reference. favorite icon) for all catalog items and KB articles in the portal. Note:
AI Search | Enable AIS | Option to enable AI Search in your portal. For more information, see AI Search in Service Portal. | Search Application | Defines the search experience settings for your portal, such as the search engine, search results limit, and suggestions limit. For more information on defining a search application configuration, see Defining search application configurations. | Search Results Configuration | Defines how search results are displayed in the portal. For more information on defining a search results configuration, see Define a composite dataset. |
Parent Topic:Configuring Service Portal | ||