Basics about policies
Technically speaking, policies grant or limit access to something already controlled by a role/circle (i.e. a domain). Since domains give exclusive control, policies are needed to further refine who and/or how someone may impact a domain.
Domains and policies always go together. Always. So, to really understand policies, first you need to understand domains — what they are and how they work (read this article on domains).
Most policies are created during Governance meetings. However, if you have a domain on your role, then you can create and update policies related to that domain at any time, without the need for a Governance meeting.
So, a useful way to think about policies is to start by thinking about what your role/circle controls. You can’t govern what you don’t control. Example: You want to limit what roles can change the website, your first question should be, “Does my role control the website?”
Pre-requisites: To add a policy on a role, a domain must be defined.
How to create a policy during a Governance meeting?
To create a policy when processing a Governance agenda item, the secretary would select Add evolution, Policy and click on New Policy
The secretary then enters all of the information in the requested fields and click on Save, then Validate.
The policy is now created and can be viewed under the Policies section of the circle page.
How to create a policy on a Role's domain
If a role owns a domain, then any role-filler can add a policy on that domain.
As role holder:
On the role's page, under the Accountabilities section, click on the icon "+". Clicking on it will allow the role-filler to add a policy on that domain.
Fill in the title and description and select the domain on which you want to add a policy.
Upon clicking on Add a reason, you will be able to share your tension with the circle's members.
Click on Validate
Now the policy will appear under the Policies section. You can edit the policy or read it by clicking on it.
The changes can be viewed in the Activities feed.