Committee setup, rosters and engagement
Committee setup and maintenance
Committees are typically built as a combination of features rather than a single dedicated module: a community group plus forms, workflows, custom fields, tags, Smart Lists, tasks and portal access. The Committee Applications experience playbook shows the standard build: a committee application form collects the member's interests, the application is stored on the member's contact record, and a workflow notifies the reviewers you choose. Once a decision is made, the same workflow can send acceptance or waitlist communications and update tags, custom fields or access permissions automatically.
Inside the community group that hosts the committee, membership is managed with four roles: Owner, Admin, Moderator and Contributor. Owners and admins manage membership, including changing a member's role, so leadership roles such as committee chair can be reflected by assigning the group's Owner or Admin role. See Creating a Group for the setup steps.
Committee terms (start and end dates) could be tracked with custom fields, if desired. Committee rosters can be maintained as Smart Lists with configurable columns to show company affiliation or other contact details. Appointment, role-change and departure history can be retained through Notes that are attached to the contact record. Automated notes can be configured in workflows as part of access and removal automations.
Committee-specific and consolidated dashboards
JourneyCARE supports custom dashboards built from configurable widgets, and the documented widget set covers contacts, opportunities, emails, calls, conversations, payments, tasks and general metrics. You create a dashboard and add widgets from the Dashboard section. See Create a custom dashboard, and browse the available metrics in Dashboard widgets overview.
Committee-specific widgets are not currently a feature.
Group analytics are on the near term roadmap.
Configurable thresholds and flags
This would likely require custom fields and reports.
Committee views and shared resources
Members, chairs and staff engage through its community group, which can be private, use discussion channels with posts, comments and replies. Learning resources and events can be connected inside the group.
Role-based access controls what each person can do: group owners and group admins manage members and settings, while contributors can only post, comment and react to content. In a private group, join attempts require manual review, including requests made through an invite link; owners and admins review them under Members > Requested and approve or decline each one. See Make groups private in Communities and Manage community group members.
Committee files and agendas can be stored as posts inside the group or through a connected file library.
Communication and engagement
Committee members can communicate through group discussions, and the community sends email notifications, for example when a member is tagged in a post or comment. For staff-to-committee email, you can send bulk email to the contacts associated with a company record directly from the company record, with the same composing, scheduling, testing, tracking and reporting options as bulk email to contacts: see Send bulk email to associated contacts from Companies and Custom Objects.
For group administrators who do NOT have access to the full JourneyCARE back-end: an email notification about a post can occur by adding "@everyone" to the post (only administrators can do this).
For group administrators who have broader permission to the contacts/marketing capabilities of JourneyCARE, group participation is a searchable attribute and the group can be saved as a Smart List.
Community analytics are not yet available, but are on our roadmap for release soon.
Current rosters
If a Smart List is created for the group, you can configure the columns you wish to see, including details such as associated company, roles, terms and contact details.
All group membership changes take effect immediately and Smart Lists that are filtering on group assignment would reflect those updates with no manual reconfiguration required.