# Roles

{% hint style="info" %}
**GitBook tip:** your product docs aren't just a reference of all your features, use them to encourage folks to perform certain actions and discover the value in your product.
{% endhint %}

## Prelude & Interlude roles

While the DAO is in the early stage it's necessary to find RIGHT people and spend energy on nurturing them, hence, to have a transparent roles breakdown.

<table><thead><tr><th width="180">Role</th><th>Description</th></tr></thead><tbody><tr><td>Gatekeeper</td><td>Can accept new DAO members</td></tr><tr><td>Arena Gladiator</td><td>Player - Rust Developer</td></tr><tr><td>Early Member</td><td>Genesis community members, OGs that joined in early days</td></tr><tr><td>Rust Dev</td><td>Contribute through working groups, play &#x26; playtest</td></tr><tr><td>Frontend Dev</td><td>Contribute through working groups, play &#x26; playtest</td></tr><tr><td>Growth</td><td>Developers acquisition, partnerships, marketing-related ops</td></tr><tr><td>Designer</td><td>Contribute to working groups</td></tr></tbody></table>