# Help Scout update

**Note**: Upon setting this up on GitHub as a pull request, images need to be properly formatted to HTML, not MD.

### Address Book ---

<p>
The Address Book app makes it easy to assign human-readable names to Ethereum addresses.
</p>

<p>
<b>Disclaimer</b>: The Address Book application is designed to act as a new Identity Provider for Aragon Organizations, so you can assign a name to an Ethereum address and have that name be displayed in all of your Aragon apps in place of the address. This requires <a href="https://github.com/aragon/aragon.js/pull/391" target="_blank">an enhancement to aragonSDK</a>, which is scheduled for an upcoming release. We will remove this note once it’s fully available, but until then you can begin naming and categorizing addresses.
</p>


<h4>
New entity
</h4>

<p>
To add a new address to your Address Book, click the "New entity" button.
</p>


<p>
Once you have filled out all of this information you can click the “Submit entity” button to complete the action, if you have permission.
</p>


<h4>
Remove entity
</h4>

<p>
To remove an existing entity, click on the menu icon associated to the entity you want to remove and click “Remove”.
</p>


### Allocations ---

<p>
The Allocations app is used to manage multi-recipient financial allocations that are budget-controlled.
</p>


<h4>
Budgets
</h4>

<p>
Budgets represent a spending limit that is imposed upon an allocation category for the accounting period. For each budget, you can see the budgeted amount for a given allocation period, how much has been allocated already, and a percentage for the remaining. Budgets do not hold any value (they don't actually hold funds). The default accounting period is 30 days. At the moment, this accounting period can only be changed using the command line tools.
</p>


<h4>
New budget
</h4>

<p>
To create a new budget, click on the "New budget" button. In the panel, define a name and an amount. If you ever need to edit this budget in the future, it is possible, but only the name and value can be updated - the token cannot. A budget needs to be created before an allocation can be created.
</p>


<h4>
Allocations
</h4>

Allocations are multi-recipient fund transactions effectuated from budgets. In the Allocations history table, each allocation is listed along with the enactment date, budget category, recipient addresses, description, status, and total amount.


<h4>
New allocation
</h4>

<p>
To create a new allocation, click on the context menu from one of your budgets and choose the "New allocation" action.
</p>


<p>
In the panel, input a description, an amount and the recipients. Make sure that the amount is not larger than your available funds, which are either the remains of your budget, or your vault's funds, if the latter is smaller than what you have as budgeted. Also, make sure that the recipients are valid Ethereum addresses. If you don't have funds in your vault, navigate to Finance and <a href="https://help.aragon.org/article/20-finance#new">make a deposit</a>.
</p>


<p>

</p>

<p>
Once the transaction has been submitted, it'll be forwarded to Dot Voting for voting, which we cover in the Dot Voting documentation. Once the allocation has been approved and enacted from Dot Voting, it will be visible in the Allocations app.
</p>


<h4>
Budget detail view
</h4>

<p>
For budget-specific information, click on any of your budgets to enter a budget detail view with a specific set of metrics and allocation history.
</p>


<h4>
Additional notes
</h4>

<p>
In our previous version of the Allocations app, the recipients could be populated using the Address Book. This required a tightly coupled relationship between the Address Book, Allocations and Dot Voting apps, which is not ideal for the long-term sustainability of the apps.
</p>

<p>
We also had many user requests for the ability to use the Address Book in applications beyond the Open Enterprise suite. To achieve both of these goals, we developed enhancements to aragonSDK although <a href="https://github.com/aragon/aragon.js/pull/391" target="_blank">the code still needs to be reviewed and merged upstream</a>. As soon as that occurs, the Address Book will be able to be integrated into the Allocations app.
</p>

<p>
In the near-term, the recipients field in the Allocations app is integrated with the custom labels feature.
</p>

### Dot Voting ---

<p>
The Dot Voting app is used to participate in multi-option dot votes, including allocations and issue curations.
</p>


<h4>
Filters
</h4>

<p>
Dot votes are sorted into open and closed votes, and can be filtered by Status, Outcome, App and date range. By status, you can filter dot votes as open and closed. By outcome, you can filter dot votes as enacted, passed, or rejected. And by app, you can filter dot votes by use case, either to only view dot votes from Allocations (multi-recipient allocations) or from Projects (issue curations).
</p>


<h4>
Dot votes
</h4>

<p>
You can see information about your dot votes in the main view, before going more into detail on one particular vote. For each vote, you can see the app it's forwarded by, the description, up to two leading options, how much time there's left to vote (or if closed, the outcome of the vote). Once you've voted on a dot vote, you'll see a checkmark icon on the vote card.
</p>


<h4>
Issue curations
</h4>

<p>
In issue curations, you're voting to set priorities amongst a set of issues. Going into a curation dot vote, you can see the number of issues involved, the vote's status and current participation versus the threshold. Vote duration and participation settings are configured during installation. If a vote is currently active, you can click on a "Vote" button and set your dots on your preferred issues, and "Submit". You can change your vote as long as there's time remaining.
</p>


<h4>
Allocations
</h4>

<p>
In allocations, you're voting to determine how much funds to disburse amongst a set of recipients. Instead of seeing the number of issues involved as in a curation, in this case you see the total amount that's being allocated, and in the results you can see the percentages converted also into their representative amounts. To vote, click on "Vote", set your dots to represent your preferred allocation of funds, and "Submit". You can change your vote as long as there's time remaining.
</p>


### Rewards ---

<p>
The Rewards app is used to compensate token holders with dividends, which can either occur on a one-time or recurring basis.
</p>


<h4>
Overview
</h4>

<p>
The Overview tab is composed of two components: a set of metrics on all the rewards in your organization, and a table with more contextual information per reward. On the metrics, you can see the average claimed reward, as well as a monthly average and the annual total of how much rewards have been disbursed since the start of the year.
</p>


<p>
In the All Rewards table, you can see your rewards' description, type, frequency and total amount to be disbursed at the next payout date.
</p>


<h4>
My rewards
</h4>

<p>
In the My Rewards tab are some metrics specific to rewards related to your address, as well as a table to keep track of the rewards that you can claim over time.
</p>


<p>
In the metrics component, you can see if you have any unclaimed rewards, as well as how much funds you've obtained throughout the past year and all-time.
</p>


<p>
In the table, you can see a list of your rewards, including a description, the disbursement date, the reward status, and how much you're being rewarded.
</p>


<p>
To claim the reward or to view more information, you can click on the context menu on the right and select the action.
</p>


<h4>
New reward
</h4>

<p>
To create a new reward, click on "New reward" in the top-right area, and in the panel, give your reward a description, specify the reference asset and define the type of reward you want to create. If your reference asset is a custom token, remember that it has to be an ERC-20 clonable token (MiniMe). For more information on each type of reward, click on the Help icon next to "Type".
</p>

<p>
<b>Note:</b> All reference dates must take place prior to the reference asset's creation date in order to be valid.
</p>


<h4>
One-time dividend
</h4>

<p>
If your dividend is a one-time dividend, you have to specify a total amount and a reference date. The reference date is the date where the reference asset must have been held by a token holder to be eligible for the reward. Remember to keep the total amount of your reward under your available funds.
</p>


<h4>
Recurring dividend
</h4>

<p>
If your reward is a recurring dividend, you have to define an amount per disbursement, the start and end date for when you want your reward to be active, and how often you want the reward to be disbursed.
</p>


<h4>
One-time merit
</h4>

<p>
If your reward is a one-time merit, you have to specify the total amount for your reward, and a start and end date for when the reference asset is being evaluated. Merits only work with non-transferable tokens.
</p>