Set up restriction policies to prevent editing of selected fields and sections<\/h3>\n
In this release, you\u2019ll find a new administration tool for Restriction policies<\/strong><\/a>. We designed this tool so that administrators can make more granular decisions about which parts of event forms<\/a> and profile forms<\/a> people can edit. Previously this could only be set directly via someone\u2019s role<\/a>, which was limited to giving access on a form by form basis. Now you can apply restriction policies to roles, and then assign that restriction policy to individual questions and sections within a form.<\/p>\n In this example we\u2019re looking at an event form used to collect a brief summary of a new injury. We\u2019ve assigned a restriction policy called Physio Policy<\/strong> to the Physio Details<\/strong> section of the form, which means only people with a role that includes this policy will be able to edit the fields in this section. The policy would be assigned to a role for physiotherapists, so the athlete and other staff members couldn\u2019t update this section of the form. A similar restriction policy could be set up for a coaching role, so only coaches could edit the Coach Details<\/strong> section.<\/p>\n As part of ongoing enhancements to password management, we\u2019ve added two new configuration options when managing password policies<\/a>. Now you can upload lists of custom patterns and passwords, which will stop people from creating insecure passwords. In addition to the option to ban common patterns<\/strong> like 12345 and qwerty<\/em>, the custom patterns<\/strong> option lets you add items of your choice, so, for example, you can prevent people from using your organisation\u2019s name or their team name in their password.<\/p>\n When you ban passwords<\/strong>, only the exact items that you\u2019ve included in the file will be banned; people can still use these items as a part of their password or with different capitalisation. For example, if you add Pineapple!!<\/em> as a banned password, someone would still be permitted to use Pineapple!!1<\/em>, pineapple!!<\/em> or Pineapple!<\/em> when setting up their password.<\/p>\n System notifications commonly appear when you complete an action or an error occurs when you\u2019re using Smartabase in your browser. We received feedback that system notifications sometimes interfered with navigating through Smartabase, and it wasn\u2019t clear that clicking on a notification would close it. As part of this release, we\u2019ve moved system notifications to the bottom right-hand corner of the screen, which keeps the rest of your screen clear to use other Smartabase tools. We\u2019ve also added a close icon to the notification box, so it\u2019s even easier to dismiss the message once you\u2019ve seen it.<\/p>\n We\u2019ve also added the ability to customise the message duration. If you\u2019d like to change the default notification duration time<\/strong> on your site, please get in touch with your Fusion Sport representative.<\/p>\n Like the enhancements to system notifications, this update focused on improving the look and feel of Smartabase. Now when you log out of your account you will be automatically taken back to the log-in screen, instead of having to click to reload the page.<\/p>\n In the last release notes, for Smartabase version 6.6, we announced:<\/p>\n![\"A](\"https:\/\/learn.fusionsport.com\/help\/wp-content\/uploads\/2020\/11\/restriction-policy-event-form-property-1024x676.png\")
<\/p>\nBan specific passwords and password patterns<\/h3>\n
![\"A](\"https:\/\/learn.fusionsport.com\/help\/wp-content\/uploads\/2020\/11\/password-policy-example.jpeg\")
<\/p>\nQuickly view and dismiss system notifications<\/h3>\n
![\"A](\"https:\/\/learn.fusionsport.com\/help\/wp-content\/uploads\/2020\/11\/new-notification-format-example.png\")
<\/p>\nCome back to Smartabase more easily<\/h3>\n
General improvements and bug fixes<\/h3>\n
\n
Highlights from your last Smartabase release notes<\/h3>\n
\n