Use Advanced Community Analytics in Batoi Flex

Who should use this article

This article is for Workspace Owners, Workspace Admins, Community managers, and authorized analysts. Community analytics routes are manager-only and require the Advanced Community Analytics capability. Members and read-only participants should not receive manager analytics merely to view their own activity.

Before you begin

• State the operating question first, such as whether profiles need review, introductions are stalled, or editorial content is ready to publish.
• Confirm that the workspace plan includes Advanced Community Analytics and that your role permits manager access.
• Know the Community settings and moderation policy. A pending count can be expected when approval is required.
• Use the analytics views as current-state summaries. The current implementation does not calculate historical trends, conversion rates, response times, sentiment, retention, or forecasts.
• Verify every cause and consequential action in the underlying member, post, meeting, or content record.

Workflow overview

Choose the right analytics view

Understand each measure

Overall Community measures

• Members counts active Community member profiles. It does not count every workspace user.
• Posts counts all active networking post records, regardless of published, pending, draft, or hidden state.
• Meeting Requests counts all active meeting request records.
• Published News counts published news and announcement records.
• Published Events counts published event and opportunity records.
• Needs Review adds draft or pending posts to pending meeting requests. It does not include pending profiles or editorial items in review.

Member measures

• Profiles counts active Community profile records.
• Visible counts profiles whose directory-visible flag is enabled. Record visibility and access rules still determine what another person can see.
• Pending counts profiles awaiting approval.
• Categorized counts distinct profiles with at least one active category mapping.
• Custom Fields counts active profile schema fields. It does not measure how many profiles completed those fields.

Workflow status measures

• Networking groups posts into published, pending, and hidden. The Pending value combines draft and pending states.
• Meeting analytics charts pending, accepted, declined, and completed requests. Canceled requests remain part of the total Requests card but are not a separate chart category in the current implementation.
• News separates published, draft, review, and unpublished records.
• Events compares published events with published opportunities. The Upcoming card currently counts published event or opportunity records that have a start time. It does not test whether that time is later than the current date.

Complete the workflow

1. Frame one operating question. For example, ask whether pending profiles require review, whether meeting requests are unresolved, or whether content is ready to publish.
2. Open the narrowest relevant view. Start with Community Analytics only for orientation, then move to Members, Networking, Meeting Requests, News, or Events Analytics.
3. Read the cards before the chart. Confirm the population and the states included in each number. Note whether a combined card omits another queue, such as pending profiles.
4. Use the chart for composition. Compare statuses within one workflow. A high pending count may reflect new activity, an approval policy, or delayed review, so it is not automatically negative.
5. Read the AI Summary cautiously. The current implementation displays a view-specific explanation of what the analytics area is intended to show. It is not a workspace-specific diagnosis and does not calculate a cause from the displayed values.
6. Verify source records. Open the related member, networking, meeting request, news, event, or moderation register. Check age, ownership, state, visibility, duplicates, and policy context.
7. Assign proportionate action. Approve, return, publish, follow up, correct settings, or leave the state unchanged. Record an owner and review date when the action cannot be completed immediately.
8. Recheck the view. Confirm that the intended records moved to the correct state and that no unrelated Community records were changed.

Turn signals into actions

Verify the result

• The selected view answers the stated question and its metric definition is understood.
• The chart categories reconcile with the related source register for the same workspace and active-record scope.
• No current count has been described as a trend, rate, forecast, or causal explanation.
• Any excluded state, such as canceled meeting requests, is considered before interpreting the total.
• The action is supported by record evidence, Community policy, role authority, and a named owner.
• A later review can determine whether the operational backlog or readiness issue was resolved.

Troubleshooting and recovery

Safety and governance

• Limit manager analytics to people who need them for Community operations.
• Do not rank members by posting or meeting volume. More activity is not automatically more valuable.
• Document metric definitions and known exclusions when using the numbers in a report or decision.
• Follow applicable privacy, retention, participation, and employee or member monitoring requirements.

Use Batoi Intelligence safely

Next step

Return to Manage a Member Community in Batoi Flex for the operating workflow, or continue through the Batoi Flex Product Guide.