What are private channels in a community platform?
Private channels in a community platform are role-gated channels visible only to members with the correct role or explicit access. They are structurally separate from public channels, where all members can read and post. CommunitiesOS includes unlimited private channels on every plan for boards, committees, and working groups.
Does CommunitiesOS support private channels for committees?
Yes. CommunitiesOS includes unlimited private channels on every plan — Foundation at $97 per month, Growth at $297 per month, and Authority at $497 per month. Private channels are not a paid add-on. Every plan supports role-based access control, persistent channel history, and unlimited channels with no member caps.
How many private channels can I create in CommunitiesOS?
CommunitiesOS supports unlimited private channels within a single community. Organizations can create a dedicated private channel for every committee, working group, task force, and subgroup — all within the same platform, all managed from the same admin dashboard, with no channel caps on any plan.
Why is email a poor choice for committee communication?
Email silos committee knowledge in individual inboxes. When a committee chair changes, discussion history goes with them or stays in a former volunteer's personal account. There is no persistent record, no role-based access, and no way for new committee members to onboard by reviewing prior discussion without forwarded email threads.
How does role-based access work for private channels in CommunitiesOS?
In CommunitiesOS, admins assign roles — Owner, Admin, Channel Manager, Contributor — and configure which roles can see and post in each private channel. A board channel is invisible to general members. A volunteer channel is invisible to board members. Access is structural and role-driven, not manual and member-by-member.
Can new committee members see previous discussion history in a private channel?
Yes. CommunitiesOS private channel history is permanent and searchable. When a new committee member joins, they can read back through the entire discussion history — no forwarded email threads required, no separate onboarding documents to maintain. Institutional knowledge lives in the platform and transfers automatically with every new appointment.
Can CommunitiesOS automatically grant access to a committee channel when a member role changes?
Yes. CommunitiesOS workflow triggers can automatically grant or revoke access to private channels based on membership status, role changes, or other defined triggers. When a new committee appointment is made and the member's role is updated, channel access adjusts automatically — no manual admin intervention required.