Feature Request - Gating Community Post Categories

tldr; ability to apply feature-gate or "lock" to certain categories of conversations, similar to application of feature-gate or "lock" to certain Classroom modules.

We have an ascension offer in place, it looks roughly like this:

Program #1 + 90 days 1-1 coaching - $x,000

Program #1 + 12 mo 1-1 coaching & advanced course modules - $x,000 * 2

The purpose of the extra modules is that certain information is counterproductive for students that aren't conceptually on a certain level yet. i.e., going from $0 to $100,000 is different than going from $100,000 to $1,000,000. More focus on hiring & KPIs, processes, scalable pricing models, paid acquisition, client onboarding & retention, etc.

Walk before you crawl type of thing.

While its clearly possible to restrict certain Classroom modules to those members, it doesn't seem possible to restrict certain Community discussion categories to those members.

Meaning, if Student A makes a post on an advanced topic we haven't trained Student B on, Student B can become very confused and dejected fairly quickly.

The request here is to apply access controls on the Community discussions.

The only other solution (which is maybe just the way it SHOULD be) is to create another Skool instance. The downside of that is naturally that the "best" students may end up only talking in that group, lowering the quality of discussion in the primary group.

2 comments