--- sourceDocument: Australia ServiceNow AI Platform user interface sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/platform-user-interface Release : - australia ft:locale : - pt-BR ft:publication_title : - Australia ServiceNow AI Platform user interface ft:clusterId : - platux bundleId : - platux workflow : - Platform --- # Understanding Service Portal # Understanding Service Portal {#ariaid-title1} * Versão de lançamento: Australia * * Atualizado 12 de mar. de 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 min. de leitura Service Portal provides a modular user interface framework for quick and easy building of application portals and dashboards for the platform. It helps developers and non‑technical administrators create attractive and engaging user experiences that drive employee adoption of critical enterprise applications. ## How to use Service Portal Service Portal is an application included in the platform UI, however it includes a visual layer for you to do most of your configuration. In the application navigator, navigate to Service PortalService Portal Configuration to view the configuration page. The Service Portal configuration page provides a unique, intuitive way of viewing all the pieces of your portal and how they interact with one another. The configuration page allows you to take advantage of a real-time preview, while configuring portal settings. Use each of the tiles on the configuration homepage to assemble the different components of your portal. If you prefer the platform layout for configuring Service Portal, you still have the option of creating your portal components within the platform UI. The two options are not separate. Everything you create in the Service Portal configuration page also appears in a table in the platform UI. ## Who can use Service Portal Several different kinds of users can configure a portal. * Limited coding: Service Portal was designed so that even users with limited coding ability or knowledge of the platform UI could set up a portal. * ServiceNow Experts: Users with an understanding of the ServiceNow platform can create portals, set up URL redirects, and view all the components of the portal in a table. Most portal configuration takes place in the Service Portal configuration page, but in specific circumstances, Service Portal administrators may need to do additional configuration directly within the platform. * Developers: Advanced customizations and new widget creation are tasks for a developer or someone who understands AngularJS and Twitter bootstrap. {#sp-what-to-know__ul_oll_jwd_px}In all cases, the user configuring a portal must have the admin or sp_admin role. ## Basic concepts You should have a basic understanding of all the following components that make up a portal: * [Themes](https://servicenow-prod.fluidtopics.net/8lcdXFi9wuLOjNeWdh~uAg "Use Branding Editor to give your portal its own look and feel."): Themes define the look and feel of the whole portal, but can be overridden by other style configurations. * [Pages](https://servicenow-prod.fluidtopics.net/Fs2XfXm2XHkX3npnfXKG1A "Use pages to organize content, ensure responsive mobile optimization, and design meaningful portal user experiences for your customers. A page houses containers and rows, which then contain widgets. By manipulating the layout of the page, and the widgets within it, you can construct your desired user experience."): Pages control where and how you store portal content. Pages do not have a defined relationship to portal records, they simply exist. * [Widgets](https://servicenow-prod.fluidtopics.net/W9_MSEWHe6KEEdlruATUrQ "Widgets are what define the content of your portal pages. You can use the base system widgets provided with Service Portal, clone and modify widgets, or develop custom widgets to fit your own needs."): Components in Service Portal are called widgets. You can use HTML templates, CSS, client scripts, server scripts, and any JavaScript dependencies to define what a widget does. From an AngularJS standpoint, widgets are essentially a superset of an Angular directive. * Most of the data in Service Portal is managed in different locations throughout the system.For example, if you are building a knowledge portal, the data exists 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. Take time to understand which tables contain and control the data you are working with in Service Portal. {#sp-what-to-know__ul_st3_pb1_jx} ## Before you begin {#sp-what-to-know__section_y3y_ll3_xz} 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](https://developer.servicenow.com/app.do#!/api_doc?v=istanbul&id=c_MobileGlideForm_API), so you may need to make some changes. {#sp-what-to-know__ul_nvf_zyf_2w} ## Additional resources {#sp-what-to-know__section_j3d_mwq_mz} Service Portal is built using several well known technologies. Use the following websites as resources to help you understand and configure your portal: * [Twitter Bootstrap](http://getbootstrap.com/css/#grid) * [CSS 3 Flexbox](https://css-tricks.com/snippets/css/a-guide-to-flexbox/) * [AngularJS](https://docs.angularjs.org/guide) {#sp-what-to-know__ul_tv1_xkw_xy} * **[Service Portal core concepts](https://servicenow-prod.fluidtopics.net/wGJ1KoRj~HpfHsiS7s2XOA)** Service Portal contains two parts: a framework and a portal. The framework is composed of a set of APIs, Angular services, directives, and tools that help to build portals. The portal is a group of pages linked by page IDs. * **[Service Portal configuration page](https://servicenow-prod.fluidtopics.net/8RHFJnSifKU~xfOjLTaIfA)** Most Service Portal configuration is accessible through the Service Portal configuration page landing page. * **[Page navigation in Service Portal by URL](https://servicenow-prod.fluidtopics.net/a5745y67OslXjx_OTpbpoQ)** You can navigate to a portal or a page in Service Portal using a URL. * **[Content Management and Service Portal](https://servicenow-prod.fluidtopics.net/i76i33ynZ~~_PTvGeAv25w)** Service Portal is a compelling alternative to the Content Management System (CMS) with a refined user experience. It does not duplicate CMS or platform UI functionality. Users who have sophisticated experiences delivered through CMS may need to invest time into transitioning to Service Portal, especially if the CMS implementation includes complex and customized Service Catalog forms.