To produce and use a Policy Enforcer profile, starting off in DocAve administrator and expand the scope tree lower to the stage where you need to apply your profile. For that purpose of this demonstration, we’re likely to use the profile to begin collection level.
Next, visit the Policy Enforcer tab at the very top and click on ‘create or apply profile.’ Then provide the profile a reputation and optional description and scroll lower to ‘add rules.’ Rules are things that you could monitor for or prevent through Policy Enforcer.
Let’s imagine, we’re developing a Policy Enforcer profile which will prevent users – even individuals with owner-level permission — from breaking inheritance through the site collection. You need to do this by visiting the safety tab and choose ‘event-driven break inheritance prevention.’ Then click okay.
Next, we have to configure the rule. Start by hitting its name deciding on which level you’re worried about permission inheritance being damaged — let’s imagine we’ll select ‘all.’
Then, scroll lower and you will see where one can setup notifications that people get an email in situation anybody does make an effort to violate the rule, such as the site collection managers (or anybody you decide to target). Then click ‘okay.’
Then, should you scroll lower, you are able to specify the origin collection policy. This is when we get out there and really evaluate the information essential to verify whether someone is trying to break the rule. We provide the collection policy a reputation as well as an optional description.
Should you recall, we did event-driven inheritance breaking so that’s the main one we have to target here. Click save.
Now we have the rule and also have it configured, so we have told Policy Enforcer how it’s getting the data — within this situation it’ll monitor real-time — we are able to produce a report when we decide to and also have that sent on the specific schedule and lower at the end we are able to use the rule, meaning it’ll begin monitoring or apply and immediately run now.
The reasons you obtain that option is because at this time it doesn’t know that we’re establishing a real-time rule. When we were establishing something to become scanned, ‘run now’ would tell it to visit scan at this time.
Next, we’ll just click ‘apply,’ and Policy Enforcer has become monitoring that website collection, and also, since we’re carrying out a real-time rule, it’ll prevent anybody within that scope from having the ability to perform that action and you’re all set!