Skip to content
All documentation

Documentation - Features

Community

How the LiteHQ community works: the workspace feed and the member portal feed, events, groups across your operator, and the moderation queue.

6 min readReviewed 2026-11-11 by LiteHQ

LiteHQ has two community surfaces. Your workspace community holds the feed, events, groups and a moderation queue for the operator. Members of a tenant company get the portal community, a feed that shows their own company's posts. This guide covers both surfaces, who can do what in each, and how groups and moderation actually behave today.

Two community surfaces

The workspace community sits under the operator's workspace, with tabs for the Feed, Groups and Events. A Moderation tab appears for workspace admins. This is where operator staff see the community across the companies and locations under the operator.

The portal community is the member-facing feed inside a tenant company's portal. It reads posts scoped to the caller's tenant company, so a member sees their own company's posts and nothing from any other company.

The two surfaces read the same posts table. A post written in the workspace feed is filed under the workspace company, and the portal feed is filtered to the viewer's tenant company.

  • Workspace community: the operator's view, with feed, events, groups and moderation.
  • Portal community: the tenant company's own feed, limited to that company's posts.

Community is a feature of the workspace, not a separate product. The feed, events and groups are already wired to real data; nothing on this page describes a pending or proposed capability.

The community feed

The workspace feed lists recent posts, newest first, with the author, the time it was posted, the like count and the comment count. Each post carries a like action and a comment thread that opens under the post.

Posting, liking and commenting are reserved for members of the workspace's own company. Operator staff who do not belong to that company can read the feed, and they see a note explaining that posting, liking and commenting are reserved for members rather than a composer.

In the portal, a member writes a post from the composer at the top of the feed and it is filed under their tenant company. The feed shows the like and comment counts read-only there; the interactive like and comment controls live in the workspace feed.

  • The workspace feed lists the 50 most recent posts.
  • The event sidebar beside the feed lists the next 20 upcoming events.
  • A like or comment is stored against the post and the person who made it.

Events

Events are listed and each has a read-only detail page.

The list separates upcoming events from past ones and shows up to 100 events. Each row carries the event's title, its start time and, when the event has a location, the location's name.

The detail page shows the title, the start time, and where they are set, the location name and the description.

Groups

Groups are scoped to the operator rather than to a single tenant company. Every company under the operator shares one set of groups, so a group can bring together people from different companies that book through you.

A public group is open to members of any company under the operator: it appears in the group list and anyone eligible can join it. A members-only group is limited to the people on its roster, and it stays out of sight for everyone else. Opening a group you cannot see returns a not-found page rather than revealing that the group exists.

Each group page shows the group's details and its member roster. A member can leave a group they belong to, and a moderator can remove someone from the roster.

Host members and LiteHQ platform staff can create groups. Tenant company admins cannot: groups are an operator-level construct, so the create control is limited to host roles.

  • Public group: visible and joinable by members of any company under the operator.
  • Members only: visible to the people on the group roster.
  • Group creation: host members and platform staff.
  • Group detail: the group's metadata and roster, with join, leave and roster removal.

Moderation

The Moderation tab appears for workspace admins only: host admins, tenant company admins and LiteHQ platform staff. It lists the workspace's posts, newest first, each with its moderation status.

Hide and restore record an audit entry and strike the post through on your screen only. They do not change the post or what members see.

Remove permanently deletes the post, along with its comments and likes. Host admins, tenant admins and platform staff can remove any post in their workspace.

Every decision writes a row to the post moderation log, so the queue leaves a record of who acted and when.

  • Moderation queue: the workspace's posts, newest first.
  • Hide and restore: audit entry only, with no change to the post itself.
  • Remove: permanent deletion of the post with its comments and likes.

Frequently asked

Who can post in the community?

Members of the workspace's own company can post, like and comment in the workspace feed. Operator staff from outside that company can read the feed but not write to it. Tenant members post to their own company feed in the portal.

What is the difference between the workspace community and the portal community?

The workspace community is the operator's view, with the feed, events, groups and moderation. The portal community is the tenant company's feed, limited to that company's posts. Both read the same posts table, scoped differently.

Do members of one company see another company's portal posts?

No. The portal feed is scoped to the caller's tenant company, so a member sees their own company's posts and nothing from another company.

Can a tenant admin create a community group?

No. Groups are scoped to the operator, so group creation is limited to host members and LiteHQ platform staff. Tenant company admins cannot create groups.

What happens when a moderator removes a post?

Remove permanently deletes the post, along with its comments and likes, and writes an audit entry to the post moderation log. Hide and restore only record an audit entry and strike the post through on the moderator's screen; they do not change the post or what members see.

Related