Last updated
Last updated
First, note that we are in the Policies Tab of the Guardian interface, and we have the role of the Standard Registry since only the Standard Registry can create a new policy.
Second, you click on the blue Create Policy button!
Once we have created the Draft of the policy – notice the status field showing draft – click on the “Edit” link on the right.
The edit screen will open and you will notice two boxes on the right side of the screen. The top Policy box is static and offers the ability to add high-level “Policy properties.” You can edit the name, Policy Tag, etc. Note that you can also create custom roles that are specific to your policy.
The second Interface ContainerBlock is specific to the first workflow block. We will begin editing this block to build our policy!
Let’s start with “Permissions”
There are currently 3 permissions or roles with permissions configured that can be applied to a policy: 1. Standard Registry with the highest level of permissions, equivalent to an administrator of the policy, 2. User which is the entity applying to receive the Renewable Energy Credits from iRec, 3. Auditor as the entity that can view the “Trust Chain” or all of the important events that led to the creation of the Renewable Energy Credit
But in the Permissions we can choose only: policy roles, any role, no role, owner.
Then we select the “type” of UI we want to utilize. In our example, we choose the “Blank” template.
Programmatically you begin like this:
Programmatically you begin like this: