Managing apps and features

Managing apps and features

Understand what Apps & Features controls   

Open community Settings and go to Apps & Features to control which modules and capabilities are available in your community.

This section helps a superhost shape the overall product experience for members. Instead of showing every possible module or feature, you can decide what the community actually needs and keep the experience focused, relevant, and easier to adopt.

This is especially useful when you want to:

  • Simplify the interface for members

  • Roll out only the modules your community actively uses

  • Hide unused features to reduce confusion

  • Control how members enter and navigate the platform

  • Decide when new features should become visible

 

 Enable or disable community apps   

Start with Manage Apps to choose the modules your community needs.


Feeds and Spaces are foundational to the product, so they remain enabled by default. Other modules can be enabled or disabled anytime, such as:

  • Dashboard

  • Events

  • Forums

  • Gamification

  • Ideas

  • Manuals

  • Tasks

  • Town Hall

This gives a superhost direct control over the scope of the community. If a module is not relevant to your current use case, you can disable it and keep the interface more focused for members.

For example:

  • Disable Forums if the community does not need long-form discussions

  • Disable Tasks if project tracking is not part of the community use case

  • Enable Manuals when you are ready to publish help or knowledge content

This makes Manage Apps an important section for keeping the product experience aligned with the actual purpose of the community.


 Choose the default landing page   

Within Manage Apps, you can also choose the community’s default landing page.

You can decide whether members should land on Feeds or Dashboard.

This setting determines what members see first after they log in.

Choose Feeds when you want members to enter directly into ongoing activity and conversations.

Choose Dashboard when you want members to first see a broader summary view of the community.

Notes
If Dashboard is not enabled, Feeds becomes the landing page by default.

For a superhost, this is a useful way to guide user attention toward the most important starting experience.

 

Set default views inside modules   

You can also configure the default view inside supported modules such as:

  • Feeds

  • Forums

  • Manuals


This means that when a member opens one of these modules, they can land on a specific section within that module rather than the general top-level view.

This helps a superhost guide navigation more intentionally. Instead of just enabling a module, you can also decide what part of that module should greet users first.

This is useful when:

  • A specific feed view is more relevant than the general feed wall

  • One forum section is more important than the rest

  • A particular manual's view is the preferred starting point for knowledge browsing

Enable or disable feature-level capabilities   

Open Manage Features to control individual capabilities inside the community.

This is different from Manage Apps. While Manage Apps controls full modules, Manage Features controls specific feature-level experiences.

From here, you can enable or disable features such as:

  • Broadcast

  • Video Conference

  • Private Conversation

  • Report Spam

  • Timesheet

This helps a superhost fine-tune how members interact inside the platform.

For example:

  • Disable Private Conversation if you want discussions to stay in visible community spaces

  • Disable Broadcast if live streaming should not be used in this community

  • Enable Report Spam if moderation support needs to be stronger

This makes Manage Features useful for controlling the depth of functionality without turning off entire modules.

Restrict newly released features   

Hosts also have access to Restrict New Features inside Manage Features.

This option lets you prevent newly released features from appearing to members immediately after rollout. You can then enable them whenever you are ready.

This is especially useful for a superhost when:

  • You want to review a new feature before exposing it to members

  • You want to avoid confusion from sudden UI changes

  • You want to introduce changes in a more controlled way


Notes
This restriction applies only to newly released features. It does not block enhancements or bug fixes made to existing features.
This gives a superhost more control over how product change reaches the community.

Next: After deciding which apps and features should be available, continue with Renaming modules and reordering apps in Zoho CommunitySpaces to customize how modules are labeled and arranged for members.