The roles and their associated permissions used by AgilePress are very important to proper functionality. There are four roles: AgilePress Admin, AgilePress Developer, AgilePress User, and AgilePress Viewer. There are also a number of new capabilities.
Ideally, only the person or persons involved in AgilePress setup need to use the WordPress admin screens. AgilePress is designed so that those working on a product (or project) can move the sticky notes from column to column (in AgilePress vernacular, this is “transitioning tasks”) and product stakeholders can keep an eye on the progress all just by visiting your WordPress site.
We recommend that you install the User Role Editor plugin to make the process of administering roles and permissions easier.
As you might expect, this role has carte blanc over all AgilePress functionality; it should be reserved for only the person or persons responsible for the setup and configuration of AgilePress.
An AgilePress Developer is someone who is working on the tasks associated with your product/project. Generally speaking, this means that they will need to be able to make comments, to transition tasks (i.e. move them from column to column) or even create new tasks as necessary. In business software development, this role is likely what most or all of your development team would require.
By default, a person who has none of the four AgilePress roles listed here cannot even see a board. This provides a level of security in the event that you do not wish for your backlogs or sprints to be visible to everyone who has access to your WordPress site. The AgilePress Viewer role allows, as one might expect, the ability to see boards but do nothing to affect them (not even make comments).