Roles and permissions in Boards

Boards provides a variety of roles to ensure users have access to the features they need to carry out their assigned tasks.

Boards includes committee-level roles and application-level roles.

Committee-level roles

Every user must be assigned a role before they can access the documents, reports, and other book content in a committee. For more information about user and committee management, see Overview of User management .

A description of each committee-level role and permissions is below:

Role Description Permissions
Administrator The Administrator is a critical role. This person oversees all book content and related tasks. They work closely with committee members to prepare, organize, and execute board meetings.

Administrators can:

  • Create books by adding documents and organizing content into folders.

  • Manage book access and visibility.

  • Delete and archive outdated books.

  • Review documents, including board and committee materials.

  • View committee composition and each member's roles.
Coordinator The Coordinator is responsible for all committee attributes, such as the committee name and members' roles and permissions. The person in this role may not be a board member. Typically, they provide internal support to the organization and board.

Coordinators can:

  • Assign users to committees and edit their roles.

  • Change the committee's name.

  • View committee composition and each member's roles.
Director The Director is a role for primary users that need complete access to a book to prepare for meetings. This person is a board member, and they can be members of one or multiple committees.

Directors can:

  • Review documents, including board and committee materials.

  • Add bookmarks and annotations, such as notes, highlights and other markups.

  • View committee composition and each member's roles.
Executive An Executive is a non-board member with senior leadership status. They contribute to book composition and organization, and they are often required to review and approve information before the board meeting.

Executives can:

  • Review documents, including board and committee materials.

  • Add bookmarks and annotations, such as notes, highlights and other markups.

  • Export the book in whole or in part, including annotations and notes.

  • View committee composition and each member's roles.
Reader The Reader is a limited role for guests or occasional users, who need to contribute to or access specific book content. The person in this role may not be a board member, but they are a significant contribution to the organization.

Readers can:

  • Review documents, including board and committee materials.

Application-level roles

Every organization must have users responsible for managing application settings as well as user authorization. For more information about settings management, see Overview of Settings management .

A description of each application-level role and permissions is below:

Role Description Permissions
User manager A User manager is responsible for all committee and user management operations in Boards. This person can add, authorize, and remove users. They can see every users' roles and permissions across all committees. They can also create and delete committees, as needed.

User managers can:

  • Authorize and remove user access to Boards.

  • Manage all user attributes and enablement.

  • Manage committee names, ranking order, and access.

  • Create or remove committees in Boards.
Settings manager The Settings manager is responsible for the security and functional settings of Boards. The person in this role oversees organizational properties. They also control book and document visibility, as well as notification frequency.

Settings managers can:

  • Manage security settings, including alerts and client app enablement.

  • Oversee display and other preferential properties for the entire organization.

  • Control feature access and functionality in Boards.