Boards, Roles & Governance

Create board templates, define the roles within them, and control which roles grant admin permissions at each level of your organization.

The Governance page is found under ORGANIZATION → Governance in the admin sidebar. Boards are collections of named roles (President, Vice President, Secretary, etc.) that can be assigned to organizations. Each role can optionally carry admin permission flags that grant the holder management access at a specific scope.

Admin Panel ORGANIZATION Org Chart Governance Administrators Governance Manage board templates and role definitions Board Templates + Board Executive Board 4 roles Edit ROLE CLUB ORG LOCAL ORDER President 1 Vice President 2 Secretary 3 Treasurer 4 + Add Role Chapter Board 6 roles Edit Regional Board 3 roles Edit Admin Permission Levels Club Full site-wide admin — can manage all settings, all orgs, all members. Org Org-level admin — can manage the assigned org and all sub-orgs beneath it. Local Local admin — can manage only the specific org they are assigned to.
The Governance page — board templates with expandable role lists and admin permission toggles for each level. The info box at the bottom explains each permission level.

Board Templates

A board is a named collection of roles that can be assigned to an organization. When you create a new organization, it automatically gets the default board associated with its component type (as configured on the Organization Structure page).

Common board templates include:

  • Executive Board — for the top-level organization (President, VP, Secretary, Treasurer)
  • Chapter Board — for local chapters (Chapter President, Road Captain, Sergeant-at-Arms, etc.)
  • Regional Board — for regional containers (Regional Director, Regional Secretary)

Creating a Board

  1. Click the + Board button at the top of the Board Templates section.
  2. Enter a name for the board template (e.g., "Chapter Board").
  3. Click Create. The new board appears in the list, ready for you to add roles.

Defining Roles

Each board contains one or more roles. Roles represent positions within the organization's leadership — the titles that members hold. Expand a board by clicking its row, then add roles within it.

Role Properties

  • Name — the title of the role (e.g., "President", "Road Captain")
  • Order — the display order within the board (lower numbers appear first)
  • Admin Permission Flags — optional toggles that grant the role holder admin access (see below)

Adding a Role

  1. Expand the target board by clicking its row.
  2. Click the + Add Role button at the bottom of the role list.
  3. Enter the role name and set the display order.
  4. Toggle the admin permission flags as needed (Club, Org, Local).
  5. Click Save to add the role.

Admin Permission Flags

Each role can carry zero or more admin permission flags. These flags determine what level of admin access a member gains when they hold this role at a specific organization. The three levels are:

  • Club — grants full site-wide admin access. The role holder can manage all settings, all organizations, and all members across the entire site. Typically reserved for the top-level President or a designated Site Admin role.
  • Org — grants org-level admin access. The role holder can manage the organization they are assigned to and all sub-organizations beneath it in the hierarchy. A Regional Director with the Org flag can manage all chapters within their region.
  • Local — grants local admin access. The role holder can manage only the specific organization they are assigned to. A Chapter President with the Local flag can manage their own chapter but not other chapters or the region above.
Tip

A role can have multiple flags enabled. For example, you might want the Chapter President to have both Org and Local flags — Local for managing their own chapter, and Org if they also oversee sub-groups within the chapter. However, most setups only need one flag per role.

Good to know

Admin permissions are granted through roles, not assigned directly to members. This means that when a member's role changes (e.g., they step down as President), their admin access is automatically revoked. No manual cleanup required.