> For the complete documentation index, see [llms.txt](https://docs.nested-knowledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nested-knowledge.com/account-management/organization-management/activity.md). # Activity View activity for nests and users across your Organization. **Activity** helps you monitor review work at the nest or organization level. Use a nest's activity view to investigate one review. Use an organization report to compare work across organization-owned nests. All activity reports are only available to admins. ### Choose an Activity View * **Nest activity** shows detailed contributions, progress, agreement, and engagement for one nest. * **Organization activity** exports summarized activity across every organization-owned nest. ### Nest Activity Open **Nest Home** → **Activity** to review one nest. This view includes activity trends, user contributions, screening agreement, workflow progress, and engagement.
Nest Activity view showing the activity graph, user contributions, screening agreement, workflow, and engagement panels.

The Nest Activity view shows activity and progress for one nest.

#### Activity Graph and Contributions Choose the last week, month, year, or all time. Use the module dropdown to narrow the graph; all are selected by default. The **User Contributions** table lists each user's actions in abstract screening, full-text screening, tagging, and critical appraisal. Contribution figures count actions, not studies. For example, `Tagged: 960` means users applied 960 tags. It doesn't mean 960 studies were tagged. #### Screening Agreement When **Dual Screening** is active and multiple reviewers have screened, **Screening Agreement** appears beside **User Contributions**. It shows overall agreement, Cohen's kappa with a confidence interval, and each reviewer's include and exclude decisions. Use **Other Reviewers** to compare a reviewer pair. In **Dual Two Pass Screening**, choose abstract or full-text agreement. Check agreement before relying on screening results.
Screening Agreement panel showing agreement metrics and reviewer include and exclude decisions.

Screening Agreement compares decisions from two reviewers.

#### Workflow The **Workflow** panel shows how studies move through the review. **Study Flow** shows counts and percentages. **Completion** shows exact awaiting and complete counts for each stage. Select a segment or count to open matching studies in [Study Inspector](/review-workflow/study-inspector.md). Workflow counts studies, unlike the contributions table. #### Engagement For nests with public outputs, **Engagement** shows views for **Synthesis Home**, qualitative and quantitative **Synthesis**, the manuscript, and the dashboard. These counts only apply when outputs are public. See [Set up Synthesis outputs.](/review-workflow/synthesis/set-up-synthesis-outputs.md) #### Download Contributions Download an `.xlsx` file when you need a dated contribution record. 1. Set the date range and module filter. 2. In **User Contributions**, select **Download**. The export uses your selected filters. Without filters, it includes all time and modules. The **Daily** sheet lists activity by user and date. The **All** sheet lists totals for the selected period. Both sheets count actions, not studies. The export covers the current nest only.
User Contributions table with the Download button for exporting contribution activity.

Download the contribution record from the User Contributions table.

### Organization Activity Organization activity reports summarize work across organization-owned nests. Use them to review workload, activity, and progress across your organization. #### Choose an Activity Type * **User Activity** lists each member's name, email, active hours, last access date, screening decisions, tags applied, and metrics extracted. Use it to review individual workload. * **Nest Activity** lists each organization-owned nest's creation date, last access date, screening decisions, tags applied, and metrics extracted. Use it to compare activity across projects. Organization reports combine activity into screening decisions, tags applied, and metrics extracted. Use a nest's contribution export for per-user, per-day details, see above. #### Generate a Report To generate a report: 1. From **Organizations**, select your organization. 2. Select **Activity**. 3. Choose **User Activity** or **Nest Activity**. 4. Select the date range. 5. Choose to include or exclude nest copies. {% hint style="info" %} Reports exclude nest copies by default. A copy includes the original nest's contents, so including both can double-count inherited work. Select **Include copies** when independent work happens in a copy. This includes copies as separate rows in nest reports. It also counts activity completed in copies. {% endhint %} 6. Generate the report.
Organization Activity report setup with activity type, date range, and copy inclusion options.

Set the report type, date range, and copy options before generating an organization activity report.

### See Also
:users-gear:
Organization Management		Create and manage your organization and its shared resources.Organization Management
:users:
Member Management		Manage organization members and their access levels.Member Management
:gears:
Organization Settings		Manage organization details, members, templates, and billing.Organization Settings
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.nested-knowledge.com/account-management/organization-management/activity.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.