Introduction: In Navision, user security can be achieved by assigning different permission sets to users. Permissions can be assigned to users according to their role. A collection of database permissions for one or more objects in the Microsoft Dynamics NAV database that you can assign to one or more users is known as a Permission Set. In this article, we will be creating a user who will have access to Items, Customers and Sales Orders only. Everything else present in the UI will be hidden from this user. Prerequisite: Microsoft Dynamics Navision 2017 Purpose of the setup: Our goal is to create a user with limited permissions. This user will have access to only Items, Customers and Sales information. Steps: Create new permission sets which includes access to only those objects i.e. tables, pages, reports, codeunits, etc. which the user has access to. A new user is created. The newly created permission sets are then assigned to this user. This will ensure that the user does not have permissions to access any other tables, pages, reports or any other objects which are not mentioned in the above newly created permission sets. Now these UI elements which the user does not have access to should not be visible to the user. Microsoft Dynamics NAV can be configured to show and hide user interface (UI) elements based on the license or the user’s permissions to the underlying tables. All elements, fields, actions, and page parts, can be removed from the user’s view of Microsoft Dynamics NAV. Depending on the setting in theUI Elements Removal field in the Microsoft Dynamics NAV Server Administration tool, only UI elements on objects in the license or on objects that the user has permissions to will appear in the user interface. LicenseFileAndUserPermissions should be selected for the UI Elements Removal field in the NAV Server Instance. This ensures that a UI element is removed if the related object is not included in the license file and the user does not have permissions to the object as defined in the AccessByPermission property for the related UI element. To make full use of theLicenseFileAndUserPermissions option in the UI Elements Removal field, it is recommended that you assign the special permission set, FOUNDATION, along with the relevant permission sets that define which application objects the user will access. AccessByPermissionproperty can be used to remove the element which should not be visible to the user. This Property Applies to Fields in tables (affecting all related fields on pages), Fields on pages, Actions on pages, MenuSuite items, Page parts, such as a Lines FastTab. To remove a UI element ‘Permission set’ from the visibility of the above created sales user, go to the MenuSuite. Navigate to the ‘Permission Sets’ under General section of Administration in the MenuSuite. Go to the properties of ‘Permission Sets’ Select the ‘Access By Permissions’ property. Choose the AssistEdit button in the Value field. The fields which are required to be selected are: Object Type – Specify the type of object to which permission is required for the UI element to be visible. Object ID – Specify the object to which permission is required for the UI element to be visible. Read – Specify if Read permission is required for the UI element to be visible. Insert – Specify if Insert permission is required for the UI element to be visible. Modify – Specify if Modify permission is required for the UI element to be visible. Delete – Specify if Delete permission is required for the UI element to be visible. Execute – Specify if Execute permission is required for the UI element to be visible. Hence, ‘Permission Sets’ will be visible to the user in the front end only if he has access to read the Permission Set table. In this scenario, Permission sets will not be visible to the user. Conclusion: Thus, using UI elements removal feature and Access By Permissions property, UI elements can be hidden from the user’s visibility. Different permission sets can be created for different users with limited permissions.

Introduction In this article, we customized our dashboard by creating a new Role Centre consisting of Sales Cue, Purchase Cue and Production Cue, business chart and including list of items. A Cue is a tile on a page in the Microsoft Dynamics NAV client that provides a visual representation of aggregated business data. Cues are designed to give users with a quick status of their daily activities, which acts as a prompt them to take action. We typically add Cues on Role Centre pages so that they are readily available to users. Prerequisites Microsoft Dynamics NAV 2017 with a developer license. The Role Centre consist of the following: Table 36, Sales Header, Table 38 Production Header Page 9301, Sales Invoice List, Page 9305 Sales Order List, Page 9307 Purchase Order List Role Centre Page Purpose of the Setup The purpose of this setup is to customize the front end of NAV 2017 by getting the sales, purchase and production Cue placed on one role centre. Steps Create a table with sales, purchase and production fields with data type as integers Set the Fieldclass property to Flowfields and give the CalcFormula and Select Editable field to No. Repeat the same procedures for other fields. Create a CardPart Page and select group to CueGroup A Cue is a tile on a page in the Microsoft Dynamics NAV client that provides a visual representation of aggregated business data, such as the number of open sales invoices or the total sales for the month. Add CueSetup Codeunit in the Global Variables and also create an Action item for the same. Create a Page with Role Center Area as container Container and add the cuepage created, business charts, list of customers, items etc. Create Action Containers for reports and the home items and run the page. Select the setup Cues option and customize the threshold and the range. Color is assigned to various ranges Standard -None (uses the background color of cue) Favorable – Green Unfavourable – Red Ambiguous – Yellow Subordinate – Grey Conclusion The Sales, Purchase and Production Cues designed give the users a quick status of their daily activities, which acts as a prompt them to take action.  

Introduction In this article we send emails on releasing and posting of purchase order, sales order and journal. We send emails with attachments in .pdf format to the respective users. For Purchase order the email is sent to the respective Vendor regarding the successful posting of orders. For Sales order email with attachment is sent to customers and in General journal the email is sent to the users. Prerequisites Microsoft Dynamics NAV 2017 with a developer license. Page 42 Sales orders, page 50 Purchase order, Page 39 General Journal  Codeunits 400 for SMTP Mail setup, codeunit 419 File management Table 409 For SMTP Mail, Table 91 user setup. Purpose of the Setup The purpose of this setup is to send emails with attachments on releasing and posting of purchase and sales order and on Posting of General journal in NAV 2017. Steps Configure the SMTP mail setup. Enter the sender’s email id in the USERID and password of the sender in the password field. The authentication is basic. Enter the appropriate SMTP server and port number. Write a codeunit for sending email with attachment Here SendEmailWithAttachment is a function in the codeunit. This codeunit Fetches the Customer email address. Using SMTP Mail it attaches the attachment in .pdf format and then sends the email. In the Respective Page, Call the codeunit in the Post and Release action button using the following command. In the NAV front end create a new sales order and post it. This send the email to the respective customer. The same procedure is applied for Purchase order and General Journal. Conclusion The Email automatically is send to the customer, vendor or user with the attachment on Posting and on release action.  

Introduction: Electronic payment to vendors can be done using Navision 2017. This reduces manual work and also errors that can be caused during payment. After specifying the payment details in the payment journal, the file can be exported. This file then has to be transmitted and uploaded to the bank to process the payment. Once it is confirmed that the payment is received and processed by the bank, it has to be posted. The details of the exported file are visible in Credit transfer registers. This helps to find what has been exported and by whom. In this article, we will be demonstrating steps required for doing Electronic Payment to vendors. Prerequisite: Microsoft Dynamics Navision 2017 Purpose of the setup: Our goal is to do Electronic payment to Vendors for their unpaid Invoices in Navision. Steps: Electronic Payment to Vendors basically consists of the following steps: Setup Setup the bank account Bank account needs to be setup to do payments. In order to be able to use credit transfers with this bank account, SWIFT code and IBAN should be valid. Payment export format should be SEPACT. Setup the vendor along with appropriate bank account details Go to bank accounts of the vendor. Make sure valid Swift code and IBAN is assigned. Choose preferred bank account for this vendor. Generate Electronic payment We will be creating a new General Journal Batch. Bal. account type should be ‘Bank Account’. Bal. Account no. is the Account from which payment will be done to the vendor. Allow Payment export should be selected. Select the newly created batch as the ‘Batch Name’. ‘Applies to Doc. Type’ should be selected as ‘Invoice’. When ‘Applies to Doc. No.’ is clicked, a list of all the unpaid invoices for this vendor will be displayed. The invoice for which Electronic payment has to be done is selected. Export Electronic payment When you are ready to post payments to your vendors using the payment journal, you can export a file with the payment information on the journal lines. Transmit Electronic payment The bank payment file is exported to the location that you specify, and you can proceed to upload it to your electronic bank account and make the actual payments. When you receive confirmation that the payments are successfully processed in the bank, you can post the exported payment journal lines. Post Electronic payment Payments should not be posted until it is confirmed from the bank that the payment is received. Once it is posted, check the vendor ledger entries of the vendor for which the payment is made. Select the payment which is made and click on applied Entries. The vendor invoice for which this particular Electronic payment is done will be displayed and vice versa is applicable. The GL Entries for this particular vendor will be visible by selecting the Payment and then clicking on ‘Navigate’ in the ribbon. The amount has been deducted from our bank account and added to the vendor bank account. In the credit transfer register, the details of the exported file will be visible. Conclusion: Thus, Electronic payment is a very beneficial way of doing payments to vendors since it makes the entire process of doing payment easier and faster. Also, all the exported files history can be viewed anytime as it gets saved in the Credit transfer registers.  

Introduction: The NAV 2017 has a new feature that uses OCR technology with added item line capture functionality to automate the data entry process for vendor invoices. OCR is an abbreviation for Optical Character Recognition. Lexmark ICS (Invoice Capture Service) provides OCR Services in NAV 2017. The OCR Service feature enables the user to take a picture of a vendor invoice document, sends it to Lexmark ICS Corp. and then imports the invoice back into NAV with the captured details. This saves a lot of time spent on manual entry of data into the system. In this article, we will see how to set up and implement OCR Services in NAV 2017 in three different ways. Prerequisite: Microsoft Dynamics NAV 2017. Lexmark ICS login credentials. Purpose of the Setup: Our goal is to setup and implement the three different ways of using OCR Services in MS Dynamics NAV 2017. Steps: OCR Service by Manual Process: The User will click on Incoming Document option or type ‘Incoming Documents’ to open the Incoming document page. User will have to upload the Document(PDF/Image) that is to be used in the OCR Service by clicking on ‘Create from File’ option which will upload the file to the ‘Main Attachments’ of the Incoming Document in   NAV. To Send the document to the OCR Service the user will have to click on the Send to ‘OCR Service’ option. After waiting for some time till the document processing is completed, User will click in the Receive form OCR Service. On receiving the OCR Service, the Financial Details gets updated in Incoming Document. User will Check if the Financial Details received are correct or not If yes, then user will have to click on Create Document option to create purchase Invoice. If no, then user will have to click on Correct OCR Data option and make changes to the required fields and then on Click Send OCR Feedback to correct the OCR Service from making similar errors on future incoming documents. User will the create the purchase invoice by clicking on create document option. Image 1.1 Process from uploading to sending the document using OCR Service in NAV Image 1.2 Process of receiving to creating the document using OCR Service in NAV OCR Service Using NAV Phone Application: In this case of using OCR Service the User uses a camera application instead of manually receiving the document. The User takes a picture of the Invoice Document. (‘Office Lens’ is a The User will upload the document file(Image) into the Incoming Documents in the NAV mobile app. User will then click on Send to OCR Service option once the document is successfully uploaded. After waiting for some time till the document processing is completed, User will click in the. On receiving the OCR Service, the Financial Details gets updated in Incoming Document. User will Check if the Financial Details received are correct or not If yes, then user will have to click on Create Document option to create purchase Invoice. If no, then user will have to click on Correct OCR Data option and make changes to the required fields and then on Click Send OCR Feedback to correct the OCR Service from making similar errors on future incoming documents. User will the create the purchase invoice by clicking on create document option. Image 2.1 Process of Sending Document in OCR Service using NAV Phone Application Image 2.2 Process of Receiving Document OCR Service using NAV Phone Application OCR Service using Email Feature OCR Services can also be performed by sending an Email. Over here the user Emails the softcopy of the Invoice Document as an attachment to the Lexmark ICS Corp. (Note: the user in this case send the email to Lexmark corp. on the email address provided by Lexmark when the user completes the registration on the Lexmark website.) An Incoming document is automatically inserted into the Incoming Document Page once it is processed by Lexmark Corp. (OCR Service Provider) in NAV. The incoming document is already processed when it is created. So User needs to Click on Receive from OCR Service. On receiving the OCR Service, the Financial Details gets updated in Incoming Document. User will Check if the Financial Details received are correct or not If yes, then user will have to click on Create Document option to create purchase Invoice. If no, then user will have to click on Correct OCR Data option and make changes to the required fields and then on Click Send OCR Feedback to correct the OCR Service from making similar errors on future incoming documents. User will the create the purchase invoice by clicking on create document option. Conclusion: The OCR Service in NAV 2017 has benefited by reducing the amount of time spent in the manual work of data entry. The more the OCR Service system is trained the more accurate results can also be obtained. The best use of OCR Service in NAV 2017 is capturing of line items in the document sent to OCR Services.  

Introduction: The OCR Service technology with added line item capture functionality can be used in the Dynamics 365 for Financials. OCR stands for Optical Character Recognition which enables the user to scan the invoice document and send it to Lexmark Invoice Capture Service(ICS) for OCR Services. This helps the user to reduce a lot of manual work of entering data into the system and also automates the process of obtaining Vendor invoice data. In this article, we will see how to set up and implement OCR Services in Dynamics 365 for Financials. Prerequisite: Microsoft Dynamics NAV 2017. Lexmark ICS login credentials. Purpose of the Setup: Our goal is to setup and implement OCR Services in MS Dynamics 365 for Financials. Steps: Setting up OCR Services in Dynamics 365 Financials The User will have to click the search option Button to the Top Right of the Web Client window. In the search box, the user has to type OCR Service Setup to open the OCR Service Setup page. Fig 1.1 Opening the OCR Service Setup page using search option In the OCR Service Setup page the user will have to will have to enter in the user name, password and authentication key which will be provided to the user once the user has registered to Lexmark Invoice Capture Service(ICS). Once this is done the user will have to test the connection by selecting the Test Connection button. A dialog box will appear once the connection is tested stating whether the connection is successfully established or not. The user has to finally check the Enable checkbox to enable the OCR Services for MS Dynamics 365 for Financials. Fig 1.2 Setting up Credentials for the OCR Service Setup Setting up Line Items In order to capture the line items into purchase invoices in MS Dynamics 365 for Financials the mappings need to be updated by the following steps In Dynamics 365 for Financials, open the Data Exchange Definition page The user will have to save a backup of the OCRINVOICE existing mapping by selecting the ‘Export Data Exchange Definition’ option. After taking a backup of the existing mapping, delete the OCRINVOICE map. Download the new mapping file by using the following link http://docs.readsoftonline.com/store/mapping/NAV_DataExchangeDef_OCRINVOICE_v1102.xml The user has to import the new mapping file by selecting the ‘Import Data Exchange’ option. Fig 2.1 Setting up Line items by changing the mapping of the OCR Service in the Data exchange Definition page Using OCR Services in MS Dynamics 365 for Financials The User will click on Incoming Document option or type ‘Incoming Documents’ to open the Incoming document page. User will have to upload the Document(PDF/Image) that is to be used in the OCR Service by clicking on ‘Create from File’ option which will upload the file to the ‘Main Attachments’ of the Incoming Document in MS Dynamics 365 for Financials. To Send the document to the OCR Service the user will have to click on the Send to ‘OCR Service’ option. After waiting for some time till the document processing is completed, User will click in the Receive form OCR Service. On receiving the OCR Service, the Financial Details gets updated in Incoming Document. User will Check if the Financial Details received are correct or not If yes, then user will have to click on Create Document option to create purchase Invoice. If no, then user will have to click on Correct OCR Data option and make changes to the required fields and then on Click Send OCR Feedback to correct the OCR Service from making similar errors on future incoming documents. User will the create the purchase invoice by clicking on create document option. Fig. 3.1 Uploading the PDF Document of the Invoice into the Incoming Documents Page Fig. 3.2 Sending the Incoming Document to the OCR Service. Fig. 3.3 Receiving Financial Information from the OCR Service. To create a purchase invoice, record the user clicks on the ‘Create Document’ option to generate a purchase invoice record of the OCR read Incoming Document. Fig. 3.4 Creating Document (i.e. Purchase Invoice) of the OCR read Incoming Document Conclusion: The OCR Service option in MS Dynamics 365 for Financials helps to speed up the process rapidly of processing invoices more accurately and gives a better result. The OCR Service provided by Lexmark Invoice Capture Service automates the entire process and saves a lot of time that goes in manually entry of data into the system.  

Prerequisite Internet facing Domain controller (if it’s an On-Prem DC) Setup the ADFS Role in our Domain Controller [Which will act as a IdP] Dynamic CRM online 2016 and CRM Portal Setting Up ADFS Open the ADFS Management in the server manager [Tool > AD FS Management] In AD FS Management tool, select Service > Claim Descriptions. SSO configuration for CRM Portal Step 1: Add Claim Description Click on Add Claim Description Add Display name as “Persistent Identifier” Add Claim Identifier as “urn:oasis:names:tc:SAML:2.0:nameid-format:persistent” Check the “Publish this claim description in federation metadata as a claim type that this Federation Service can accept” Check then “Publish this claim description in federation metadata as a claim type that this Federation Service can send” Click on Save. Step 2: Add Relying Party trust Go to Trust Relationships >Relying Party Trust Click on Add Relying Party Trust Click on Start Select “Enter data about the relying party manually” and then Click Next Enter “Display Name” then Click Next Select “AD FS Profile” then Click Next In configure Setup Leave the setting as it is and just click Next. In Configure URL Select “Enable support for the SAML 2.0 WebSSO protocol” and add URL https://YourPrortalURL/Signin-saml2 [Append the “Signin-saml2” to your portal URL it’s an CRM portal internal URL which will internally manage the SAML Authorization]. In Configure Multifactor Authentication Just click Next as here we are not focused on multifactor authentication. In Choose Issuance Authorization Rules, select “Permit all users to access this relying party”, click Next In Ready to Add Trust, Click Next. Finally Click Close. When we close it open another dialog for setup the claim rule. Click On “Add Rule” In claim rule template select “Transform an incoming Claim” Select Incoming Claim Type as “Window Account Name” Select Outgoing Claim Type as “Name ID” Select Outgoing Name ID format “Persistent Identifier” [ created in 1st step] Select “Pass through all Claim Values” Then click on Finish. Setting in CRM Portal (Site Setting) Login to CRM Using admin OR Customizer role, then go to Portal Site setting as Shown below, In site setting add below 4 records to enable SSO using AD FS, before that make sure Authentication/Registration/ExternalLoginEnabled is set to “True”. Add New Site setting as “Authentication/SAML2/ADFS/MetadataAddress” where value of this setting will be https://adfs_domain/FederationMetadata/2007-06/FederationMetadata.xml Just append the “FederationMetadata/2007-06/FederationMetadata.xml” to your AD FS domain name also make sure your AD FS has “Https” “Authentication/SAML2/ADFS/AuthenticationType” where value of this setting will be https://adfs_domain/adfs/services/trust Just append the “adfs/services/trust” to your AD FS domain name “Authentication/SAML2/ADFS/ServiceProviderRealm” where the value will be your portal URL. “Authentication/SAML2/ADFS/AssertionConsumerServiceUrl” where value will be “https://portalURL/signin-saml2” After this setting just restart you CRM Portal, then you can use SSO in Your Portal.

Azure Active Directory B2C is a cloud identity management solution for your consumer-facing web and mobile applications. It is a highly available global service that scales to hundreds of millions of consumer’s identities. Built on an enterprise-grade secure platform, Azure Active Directory B2C keeps your applications, your business, and your consumers protected. Azure Active Directory B2C offers developers a better way to integrate consumer identity management into their applications with the help of a secure, standards-based platform and a rich set of extensible policies. When you use Azure Active Directory B2C, your consumers can sign up for your applications by using their existing social accounts (Facebook, Google, Amazon, LinkedIn) or by creating new credentials with username and password and called as “local accounts.” Get started To build an application that accepts consumer sign up and sign in, you’ll first need to register the application with an Azure Active Directory B2C tenant. Step 1: Sign into Azure subscription and get access to Azure AD B2C. Step 2: Create an Azure AD B2C tenant Use the following steps to create a new Azure AD B2C tenant. Currently B2C features can’t be turned on in your existing tenants. Sign in to theAzure portal as the Administrator. Click New > App Services > Active Directory > Directory > Custom Create. Choose the Name, Domain Name and Country or Region for your tenant. B2C directories are not yet available in the selected country/region so select region or country B2C is available. Check the option that says This is a B2C directory. Complete. Your tenant is now created and will appear in the Active Directory extension. You are also made a Global Administrator of the tenant. You can add other Global Administrators as required. Step 3: Navigate to the B2C features blade on the Azure portal Navigate to the Active Directory extension on the navigation bar on the left side. Find your tenant under theDirectory tab and click it. Click theConfigure tab. Click theManage B2C settings link in the B2C administration section. The Azure portal with the B2C features blade showing will open in a new browser tab or window. Note: It can take up to 2-3 minutes for your tenant to be accessible on the Azure portal. Retrying these steps after some time will fix this. Easy access to the B2C features blade on the Azure portal Pin this blade to your Starboard for easy access. Sign into the Azure portal as the Global Administrator of your B2C tenant. If you are already signed into a different tenant, switch tenants (on the top-right corner). Click Browse on the left-hand navigation. Click Azure AD B2C to access the B2C features blade. Azure AD B2C to access the B2C features blade – How to add application in Azure AD B2C After adding application, you need to share application ID with developing team for further coding to redirect to sign up and sign in page. This is ‘renaissancesvcb2c.onmicrosoft.com’ your tenant ID and ‘https://www.contoso.com’URL will be required for configuring with Identity providers to sign up and sign in. After configuring your tenant ID and URL with Identity providers it will provide Client and secret ID. Add Identity Provider Use that ID and Key in Azure AD and try to Sign up and Sign in. After Adding Identity providers. Next step – Add sign up polices as per your requirement. Adding sign in policies is easier then sign up policies.  

Introduction User security can be achieved by assigning different permission sets to users. Permissions can be assigned to users as per their role. A permission set is a collection of database permissions for one or more objects in the Microsoft Dynamics NAV database and Dynamics 365 Financials that you can assign to one or more users. This article summarizes User security capabilities and differences in Navision 2017 and Dynamics 365 Financials. And can be used as guide when evaluating which platform to select for an implementation, when you have specific security requirements. We have implemented User Security for our Client Titan Labs. You can read its case study here. The following is a Scenario for a Sales User: Administrator User having Super permissions creates a Sales user who will have access to only Sales, Customers and Items. Other information on Finance, Purchase etc. should be hidden from this Sales user. Prerequisite: 1. Microsoft Dynamics Navision 2017 2. Microsoft Dynamics 365 Financials. User Security in NAV 2017 In Navision 2017, Administrator user having Super Permissions creates a new permission sets which include access to only those objects i.e. tables, pages etc. which the user should access. E.g. A sales user can access sales orders, sales quotes etc. The new permission set created is assigned to the user. This will ensure that the user does not have permissions to access any tables, pages or any other objects regarding finance, purchase etc. Depending on the setting in theUI Elements Removal field in the Microsoft Dynamics NAV Server Administration tool, only UI elements on objects in the license or on objects that the user has permissions to will appear in the user interface. LicenseFileAndUserPermissions is selected for the UI Elements Removal field in the NAV Server Instance. This ensures that a UI element is removed if the related object is not included in the license file and the user does not have permissions to the object as defined in the AccessByPermission property for the related UI element. A copy of permission sets can be created and edited. Dynamics 365 Financials In Microsoft Dynamics 365 Financials, the Administrator user having super permission can create users in the Admin centre but only the default permission sets available in Dynamics 365 Financials can be assigned to the users, it is not possible to edit or add to the existing Permission Sets. Permissions Sets are assigned to each user in the User Card either by directly adding them or by associating a User Group which has Permissions sets assigned. It is suggested to give D365 BASIC permission set to all users. This will allow users to get into Dynamics 365 for financials and open the home page without permission errors. It does give READ (but not INSERT, MODIFY, or DELETE) access. Sales User is assigned a Predefined User group D365 Sales. This user has following permissions D365 BASIC D365 CUSTOMER EDIT D365 CUSTOMER, VIEW D365 ITEM, EDIT D365 ITEM, VIEW D365 SALES DOC, EDIT D365 SALES DOC, POST D365 DYN CRM MGT, LOCAL After assigning D365 Sales User Group to the Sales User, the Role Centre displays information with respect to the User group assigned i.e. D365 Sales but the User will still have access to Information like Finance, Purchase etc. when he tries to find it using the search bar which actually should be disabled. A copy of permission sets cannot be created. Permission error is displayed. Error displayed while creating new permission set. Note: The above error was raised at Dynamics 365 Business edition community, and we received a response from Microsoft employee that the functionality to fine-tune permissions for users will be added in a future update. Conclusion Microsoft Dynamics Navision 2017 allows an Administrator user to create Users with limited permissions by creating new permission sets and assigning it to the User. Dynamics 365 Financials allows an Administrator user to create Users but is not allowed to create new permissions sets. The default permissions sets can only be assigned to the User.  

This blog is intended to showcase capabilities of Dynamics CRM portals to accommodate custom CSS for UI changes. For adding any custom CSS for the portal, we need to add bootstrap.min.css as a child file of “Home page” on the portal. Steps for adding CSS file on portal Step 1: Create a custom bootstrap.min.css having required changes for the UI of the portal. You can create custom CSS using below references: a. https://bootswatch.com/ b. http://getbootstrap.com/customize Step 2: Login into the Portal with credentials having Administrator security role. Step 3: Navigate to Home page. Step 4: Add a new Child file to Home page using “Administrator” panel on the upper right side of the screen. Step 5: Browse the updated bootstrap.min.css. Name and partial URL fields will be auto-filled. You can choose to hide the child file from the Site map. Step 6: Click on Save. By performing above steps, you can have custom UI changes on the Portal. Note: In some cases, changes are not reflected immediately on the portal. For this, kindly restart the portal and check.