Set up Service Portal

Set up a site for your users using Service Portal.

Requirements

Configuration for Service Portal takes place in the Service Portal Configuration page. You can access this page by navigating to Service Portal > Service Portal Configuration.

Role required

admin or sp_admin

Before you begin

Take the following into consideration before configuring Service Portal:
  • Who are you building your site for and why?
  • What information do you want to include in your site?
  • What do you want the mobile experience to be for users?
  • Which platform applications do you plan to use in your portal?

    You can use parts of the platform, such as knowledge articles and catalog items, as the content for your portal.

    For example, if you are building a knowledge portal, the content displays in Service Portal, but the knowledge articles are authored and managed in the Knowledge application. The same is true for any other type of content you plan to leverage. It is important to take time to understand the table structure of data to become acquainted with content.

  • How customized is your service catalog? Catalog client scripts and UI policies only work in Service Portal if they use the mobile GlideForm API, so you may need to make some changes.

What to do

Create a portal
A portal is the engine that houses all of the references to content for your site. The portal record defines the URL extension for a site, as well as things like the knowledge base, catalog, and homepage. You can also use the portal record to define the header menu and the portal branding.
From the Service Portal configuration page, click the New Portal tile. Use the fields on the form to associate pages to the portal.
Create a page
Pages are the centerpiece of the end user experience. Page definitions not only control the layout of the content, they craft the experience for the user. Pages also help define mobile responsiveness, which is a key component in the user experience.
Use any existing page included with Service Portal as an example for your own creation.
Use the Service Portal Designer to create pages, assign layouts, and add widgets.
Create a widget
Widgets are the power behind the portal. Widgets are highly customizable and can be used to provide an endless variety of experiences for your users. Anytime you add a widget to a page it becomes an instance of itself. That widget instance has its own record so you can configure it specifically for each use. For example, you can add several Icon Link widget to a page, configure them to link to different areas and with different icons, and none of them will be affected by the others.
You can start by cloning an existing widget and making changes to your cloned version. Developers or people with an advanced understanding of AngularJS can create widgets from scratch.
Create a portal homepage
When a portal is referenced by the URL suffix it lands on a home page. This homepage is often labeled index in website language. The home page is probably the most important page of your portal as it houses the major information and actions that your users see.
Configure the header menu
The header menu in a portal is actually comprised of two separate widgets: a header widget, which determines the style of the header, and the menu widget, which determines the actual items that appear in the header. You need to configure both before a header menu can appear and act like a header menu in your portal.
Configure the branding for the portal
The Branding Editor allows you to configure the styles and theme of your portal in a view with real time updates. You can see how your portal will appear to users with the click of a button. More advanced users still have the option of creating CSS stylesheets for the portal theme, however they will not be able to take advantage of the real time update that the Branding Editor provides. Any changes made in the Branding Editor or to specific components of the portal (such as a widget or a page container) override any customizations made to the theme.

Next steps