Use one active scope
The Community Scope Header shows either Whole community or the selected Circle, plus route-specific context. It stays stable while scrolling and avoids a carousel of competing scopes.
Create smaller member groups for cohorts, chapters, teams, mentorship, cities, or private participation without splitting the community.
Cohorts and chapters often need their own people, conversations, events, and spaces, but a separate platform or account for each one breaks community continuity. Circles introduce a visible scope within the same community shell, preserving whole-community participation while giving smaller groups the context they need.
The Community Scope Header shows either Whole community or the selected Circle, plus route-specific context. It stays stable while scrolling and avoids a carousel of competing scopes.
The selected Circle can shape feeds, Spaces, Members, and Events wherever the current route supports circle context. The scope bar makes the active group explicit rather than relying on hidden filters.
Eligible members can see and request appropriate Circles, while managers review pending membership and manage Circle membership according to current role gates.
Community managers can create a Circle with its purpose and selected administrators. Circle-level management remains narrower than full community administration.
Per-Circle unread badges appear in the chooser and aggregate unread context appears in the header, excluding the Circle that is already active.
Open the community scope chooser and select Whole community or an accessible Circle.
The header and context bar identify the active Circle and route.
Use the scoped feed, spaces, people, and events available to the Circle.
Switch scope and return content to the top while the community shell remains consistent.
Create a Circle name, description, and initial administrators through the current manager flow.
Approve or reject Circle requests and manage active Circle members.
The entire Circle system is hidden when Circles are disabled and follows the community’s plan and role permissions.
Circles are free for every community. The chooser appears only when the feature is enabled and the signed-in member has relevant scope options.
A Circle is primarily a smaller member scope. A Space is a focused content destination. A Circle can carry scoped access to several surfaces, including Spaces.
No. Circle visibility, membership, requests, and management follow the current access and role rules.
No. Whole-community semantics include only activity that is explicitly eligible to be shared to the main feed.
Yes. The active scope is shown in a persistent header and related context controls rather than hidden in a background filter.