> ## Documentation Index
> Fetch the complete documentation index at: https://learn.playlab.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Centralized org monitoring and flags

> How org admins review activity, flagged messages, and member detail across all workspaces in their organization.

An organization-level view collects activity and flags from every workspace into one place. From the org dashboard, an admin sees usage across every workspace, the centralized flagged messages list, and member detail pages that span the org. This page covers what the view shows and how to use it.

<Warning>
  **Access requirements**

  Org-level monitoring is visible to org admins. Workspace owners and facilitators see their own workspace's activity. Members see their own conversations. The roles are described in [Org permissions and roles](/features/Org%20Permissions%20and%20Roles).
</Warning>

<Frame caption="Walkthrough: reviewing activity across your organization as an org admin.">
  <iframe src="https://drive.google.com/file/d/1MCRb6zI5rXVLiqCBtElSVqFF3RjJmyQ9/preview" frameborder="0" allow="autoplay" allowfullscreen="" style={{ width: "100%", maxWidth: "720px", aspectRatio: "16 / 9", margin: "1.5rem auto", display: "block" }} />
</Frame>

## Org-level monitoring

The org dashboard shows aggregate usage across every workspace, app, and member in your organization. Filter by workspace, by app, by member, or by date range. The same view feeds the partnership reports we share with Learning Partners.

The aggregate view is the starting point. From any row, click through to the workspace, app, or member for details. Playlab staff accounts are excluded from these member and moderated-user lists, so you only see members of your own organization.

## Flagged messages dashboard

The flagged messages dashboard surfaces every flag from every workspace in one list, with severity, date, member, and the app where the flag came from.

For each flag, you can:

* Read the full conversation in context
* Open the member's detail page to see their other activity
* Open the app to review prompt and references
* Mark the flag reviewed or escalate further

For escalation paths, the [Escalating Flagged Conversations](/features/Escalating%20Flagged%20Conversations) doc describes the next steps. The dashboard makes finding what to escalate faster.

For a walkthrough of filtering down to moderated and flagged messages, see [Safety and moderation updates](/features/Safety%20and%20Moderation%20Updates#responding-to-a-moderation-email).

## Member detail across workspaces

When a flag or activity pattern raises concern about a single member, the member detail page collects their activity across every workspace they belong to in the org.

Click a member from any view to open their detail page. The org-scoped version shows:

* All apps used in any workspace, segmented by workspace
* Conversations across all workspaces
* All flagged messages
* Apps the member has built

For the workspace-scoped version (the owner and facilitator view), see [Workspace member detail](/features/Workspace%20Member%20Detail).

## App-specific activity

For drilling into a single app's usage, the app-level view lets you set goals and success criteria, review individual conversations, and analyze patterns. App-level insights are now available to builders, with cross-workspace aggregated metrics rolling out. See [App-level insights for builders](/features/Org-Level%20Insights#app-level-insights-for-builders).

## Best practices

Habits that have worked for admins:

Set a weekly review cadence. Open the flagged messages dashboard every Friday and clear flags that have been resolved. Patterns are easier to see when the list is current.

Watch for cross-workspace patterns. A single student showing up in multiple workspaces' activity in unusual ways is more useful than reviewing each workspace separately.

Use date filtering to keep views manageable. Last 7 days for monitoring, last 90 days for partnership reports.

When a flag warrants escalation, use member detail first. The conversation in context is more useful than the flag in isolation.

## Key points

<Info>
  * Org dashboards show usage across every workspace from one view
  * Centralized flagged-messages list surfaces safety issues across the org
  * Member detail spans every workspace a person belongs to
</Info>

## FAQ

<AccordionGroup>
  <Accordion title="Can I export the data?">
    Yes. The dashboards have export buttons for the visible data range. CSV is the default. JSON export is available for the org-level view.
  </Accordion>

  <Accordion title="Are there role-based limits?">
    Org admins see all of it. Workspace owners and facilitators see their workspaces only. Members see their own. The role matrix is in [Org permissions and roles](/features/Org%20Permissions%20and%20Roles).
  </Accordion>

  <Accordion title="When does cross-workspace aggregation ship?">
    Org-level insights with cross-workspace aggregation are rolling out — check the [product changelog](/changelog/Product%20Changelog) for current status. In the meantime, the dashboards show usage but advanced aggregations are limited.
  </Accordion>

  <Accordion title="What is the difference between this and the workspace activity view?">
    Workspace activity is scoped to one class. Org monitoring sees every workspace in the org and surfaces flags across the network. Use workspace activity for day-to-day teaching. Use org monitoring for trust and safety, partnership reports, and cross-class patterns.
  </Accordion>

  <Accordion title="How long is the data retained?">
    For the lifetime of the organization. Archived workspaces retain history. Deleted workspaces' activity stays visible to org admins for compliance purposes.
  </Accordion>

  <Accordion title="Are flagged messages reviewed automatically?">
    Playlab's safety system surfaces messages that match concerning patterns. A human admin still reviews each one. We don't auto-resolve.
  </Accordion>

  <Accordion title="Can I customize what gets flagged?">
    The default safety rules cover most cases. Org-level customization is on the roadmap. For specific concerns, contact [support@playlab.ai](mailto:support@playlab.ai).
  </Accordion>

  <Accordion title="What happens to flags after I review them?">
    Mark a flag as Reviewed and it moves to your archive. The conversation stays visible. You can revisit any flag later.
  </Accordion>
</AccordionGroup>

***

Last updated: 06-22-2026

Contact us at [support@playlab.ai](mailto:support@playlab.ai)