Himmat Singh Dulawat (4x Sitecore MVP)

Problem Statement: Due to certain business requirements, we create fields read-only or hide them from the author to avoid unnecessary confusion while ensuring business logic is implemented.  In Sitecore Content Hub, we create a field property from the Content-Type option, there is no way to hide it during the creation process. Solution: There are two types of members for content types: content members and detail members . Content members represent individual pieces of content and are editable on the content detail page. Detail members represent content metadata and can be hidden from the content detail page. To meet the above requirements, you can change the member type from content to detail by moving the member to the M.Content schema page. Next, you can update the entity details component to ensure this member does not appear on the page. Happy Sitecoreing  😊

In an organization, the Password Policy is key to securing the platforms, preventing unauthorized access, and protecting sensitive media and metadata etc. In this blog post, I will let you know how you can update your password policy in the Sitecore Content Hub product by enforcing users to reset their passwords every 90 days. Sitecore Content Hub provides the configurable option to enforce the organization's standard-based password policy.  You can configure the password policy from the security settings section of Manage Launchpad.  Click on the Manage Icon and choose the Settings option: From the left panel, search for Authentication or click on the Authentication under Portal Configuration: The default setting of the expired password is set to 2147483647 minutes, and other default values can also be seen in the other settings in the PasswordRules example: RequiredLength, RequiredLowercase, RequiredUpercase, RequiredDigit, etc. To c...