Skip to main content

Hidden, Inactive, and Test Chapter Status

  • Updated
This article describes hidden, inactive, and test chapter status.

In the chapter dashboard, we can find the Chapter Status Section, which includes four different settings we can edit:

  • Active or Inactive Status Chapter
  • Hidden Chapter
  • Test Chapter
  • Sub-chapters

In this report, we’ll include information about what implications each of the three first settings has and how it affects different functionalities in the platform, such as analytics, and cohosted events.

Chapter settings can be edited based on your team role. Contact your community administrator with questions. 

Chapter Status: active or inactive

Chapters can be set as active or inactive. The main difference between these statuses is that inactive chapters are only accessible by admins or users that are part of the chapter team.

Inactive Chapter implications

  • They are only accessible by admins or users that are part of the chapter team
  • These chapters cannot be added as collaborators in cohosted events
  • Events published in inactive chapters are only accessible by admins or users that are part of the chapter team.

Note that the data collected from inactive chapters is still present in the analytics tabs, included by default. It is possible to exclude the data from inactive chapters if required by using the Chapter Status filter.

The reason the inactive chapters are included in analytics is that active chapters could have been moved to inactive, but all the activities that happened in that chapter can still provide valuable information for the account.

Usage for Inactive Chapter status

The inactive status is usually used for chapters that were active at some moment, and now are no longer in use. For example, a chapter that lost its chapter team due to external reasons could be moved to "inactive" since no one will be hosting events or maintaining it.

Another case could be that a new chapter is created, but there are still a few things that need to be worked on. This chapter could be set as inactive so no one can access it except the chapter team members that need to work on making it ready to go live.

Hidden Chapters

Chapters can be set as hidden to prevent users from finding them. The hidden chapters are totally functional, the only difference between a hidden and an unhidden chapter is that the hidden chapter cannot be found unless the user accesses them with a direct link to the page. The same happens with Hidden Events.

Hidden Chapter implications

  • All the events hosted in hidden chapters are hidden by default, and it’s not possible to make them visible.
  • The data from the hidden chapter will still be added to all the analytics as normal.
  • The Hidden Chapters have the cohosted functionality
    • If a hidden chapter is added as a collaborator to a hidden event, the user will be able to find the cohosted event in the upcoming event section of the chapter. They will be redirected to register to the main event page.
    • If a hidden chapter is hosting a cohosted event, the users that access the event page will see the “This is a hidden event” pop-up when they are redirected to the event page from the collaborator chapter.

Usage for Hidden Chapters

Chapters are set as hidden when you want a limited group of chapter members. For example, if you want to have a Chapter in Google for all the organizers, you can create a hidden chapter.

Test Chapters

A chapter can be set as Test Chapter to prevent the data to being included in the analytics. The test chapters function the same way as the non-test chapters, except for the data analysis portion.

This means that unless we use the test option with the hidden or inactive setting, the test chapter will be visible to any user, but they will never be visible in the Analytics sections.

Usage for Test Chapters

You are already familiar with the Gotham and Central City chapters, which are created by default from Bevy, so we can run tests in your instance without affecting any of the data collected in any other chapter. These chapters are, by default, test chapters.

Additionally, you can create test chapters to run tech tests with your team or to enable your team members how to use the platform before adding them to their corresponding chapter team.