Service Portal User Criteria or Catalog 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; } --> Service Portal User Criteria or Catalog User Criteria that are defined in different domains as the current users' domain are not honoured.Release or EnvironmentAll releasesCauseThe User Criteria which is not honoured is not in the global domain or the domain in which the user is. The User Criteria table is data-separated and not process-separated (from sys_dictionary, notice that there is no sys_overrides column for the 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 the parent domain of the user, the user criteria gets evaluated as false and the user can't see the item.ResolutionMove the User criteria to the global domain or the domain of the user.