Protection settings part 1

  • Use password encryption: Since InfoGlue 2.8.0 we have added a possibility to use encrypted passwords in the database.
  • Disable image editor: Not used at the moment.
  • Protect content types: Set to yes if you want to access control what content types users should see. Take care as when you switch to Yes you will have to go through all content types and set rights. If enabled none of the content types are usable by anyone by default.
  • Protect workflows: Set to yes if you want to access control what workflows users should see. Take care as when you switch to Yes you will have to go through all workflows and set rights. If enabled none of the workflows are visible to anyone by default.
  • Protect categories: Set to yes if you want to access control what categories users should see. Take care as when you switch to Yes you will have to go through all categories and set rights. If enabled none of the categories are visible to anyone by default.
  • Allow publication event filter: If set to yes the users are able to notify the publishers in their group about what they have sent to them. More on that feature in the user manual.
  • Hide restricted component properties: This setting allow you to state if the system should hide properties not editable by the user in the structuretool/component-editor.
  • Default publication event filter: Sets the default choice for the feature.
  • Protect working deliver: Set to yes if you want to force login to the working deliver. Usable to avoid people to authorized to peek at the working site.
  • Protect preview deliver: Set to yes if you want to force login to the preview deliver. Usable to avoid people to authorized to peek at the preview site.
  • Force identity check: States if the site should look if the user is logged into SSO even though the page does not require login.
  • Enforce content access check: Set that the site should enforce extra hard content access control. Some overhead but more checks for unauthorized reads.
  • Max rows shown on content search: How many found items should be shown after a search.
  • Allow submit to publish to propose other repositories pages and contents: If set to yes a user publishing a content or page are also suggested to publish items from other repositores as well.
  • Max rows shown on content search: How many found items should be shown after a search.
  • Default number of years before content/page expire: You can now control the default expire date jump which I proposed when you create new content/pages. Default is 50 years.
  • Enable datefield editing: You can choose to let users edit the publish/expire dates directly in the textfields as a complement to using the calendar. Useful sometimes.
  • Show content version first: When clicking on a content InfoGlue shows the master language version first instead of the content cover. If you don’t want this behavior set this to “No”.
  • Tree version: Allows you to change the tree implementation. Default the value is “html” but it can be “applet” as well.
  • Disable custom icons: Allows you to turn on/off the new feature which allows custom icons for each content type but is slow on some OS/Browsers. Defaults to true.
  • Show components first: By default InfoGlue shows the working version of a page when you click on a site node in the structure tool. If you rather want the page cover to be shown set this to “Yes”
  • Show all workflows: Set to Yes if you want the users to see all workflows even if they are not involved.
  • Enable edit on sight: No good reason to disable it completely but it’s possible here.



comments powered by Disqus