Service Portal User Criteria not working in domain separated instancesDescription<!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Symptoms Service Portal User Criteria applied at widget instance level are not honored. Release Any supported release Cause The User Criteria which is not honored is not in global domain or the domain in which the user is. User Criteria table is data separated and not process separated ( go to sys_dictionary table and notice that there is no sys_overrides column for user criteria table which confirms that the table is data separated). So the user will not have access to the parent domain's record. Because of this, if the User Criteria is in parent domain of the user, the user criteria gets evaluated to false and user can't see the widget instance. Resolution Move the User criteria to the global domain or the domain of the user. Additional Information https://docs.servicenow.com/csh?topicname=c_DomainSeparation.html&version=latest