---
title: "Rocket Chat App Info Panel Guide"
slug: "app-info-panel-overview"
description: "Explore the Rocket Chat app info panel. Access app details, manage secure integrations, and optimise collaboration within your platform."
updated: 2026-10-20T14:57:07Z
published: 2026-10-20T14:57:07Z
canonical: "docs.rocket.chat/app-info-panel-overview"
---

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

# App Info Panel Overview

The **App Info** interface is a centralized section that provides detailed information and configuration controls for each Rocket.Chat app installed on your workspace, whether [installed via the Marketplace](/v1/docs/rocketchat-marketplace) or [manually uploaded under Private Apps](/v1/docs/rocketchat-private-apps).

This document covers the entire **App Info** UI and its functional components, helping you manage your apps more effectively, troubleshoot behavior, and fine-tune their configuration.

## Accessing the App Info page

To access the **App Info** page for an app:

1. Click the **Marketplace** ![](https://cdn.us.document360.io/6ae79a05-7252-45d0-96e8-8f375e07b1b2/Images/Documentation/Screenshot 2025-12-23 130453.png) > **Explore**.
2. Select any of the options from the left-hand menu:
  1. **Explore** to discover various apps available on the Rocket.Chat Marketplace.
  2. **Premium** to find apps available exclusively to the [premium plans](/v1/docs/our-plans).
  3. **Installed** to view apps installed from the marketplace.
  4. **Requested** to view app requests from your workspace users.
  5. **Private Apps** to view manually uploaded apps.
3. Click on any app in the list to open its **App Info** page.

> [!NOTE]
> To learn more about each Marketplace section, visit the [Rocket.Chat Marketplace guide](/v1/docs/rocketchat-marketplace).

## App Info page overview

At the top of an app’s **App Info** page, the following information is displayed:

- App name and short description.
- An **Install** button to install the app in your workspace. Some apps are subscription-based, and you must purchase them before installing.
- The installed app status which indicates whether it is `Enabled` or `Disabled`.
- A kebab menu from where you can install the app, enable or disable it, view logs, and uninstall it.
- The app developer and publisher.
- The **Premium** label indicates that the app is exclusively available for [premium plans](/v1/docs/our-plans).
- The current app version and when the app was last updated.

The **App Info** page is divided into the following main tabs:

### Details

The app **Details** tab displays high-level information about the app, including:

- **Description**: A brief overview of the app’s purpose.
- **Categories**: Tags used to classify the app (e.g. `Bots`, `Omnichannel`).
- **Contact Info**: Author site and support links.
- **Documentation**: A link to app-specific or public Rocket.Chat documentation.
- **APIs (for API-based apps)**: Endpoints exposed by the app for integration purposes, shown with example curl requests.

### Requests

The app **Requests** tab is visible for installed apps and is used to display app installation or access requests submitted by workspace members. This feature supports approval workflows in environments where users are not permitted to directly install or enable apps.

If your workspace uses request-based permissions, any pending requests will appear here, showing details such as the requester and request time. If no requests have been submitted, the tab will display **No requests** message.

### Security

The app **Security** tab is available for installed apps and provides detailed information about the app’s permissions and usage policies. It helps administrators assess the scope of access an app requires within the workspace.

The tab contains the following sections:

- **Privacy Summary:** Displays Rocket.Chat’s data usage terms, which vary depending on the type of deployment (SaaS or self-managed). This summary outlines how user data may be collected or processed by the app or service provider.
- **Permissions**: Lists all permissions requested by the app. These may include access to:
  - Server data (e.g., room info, user info, settings)
  - Livechat resources (e.g., visitor data, departments)
  - Internal systems (e.g., scheduled jobs, slash commands, HTTP endpoints)
  - UI interaction or message handling

This list helps administrators evaluate the app’s security impact and compliance with internal policies.

- **Policies:** Includes links to:
  - Terms of use
  - Privacy policy

### Releases

The app **Releases** tab on installed apps displays the version history of the app along with release notes and corresponding release dates. Each version entry is collapsible and may include a summary of changes, improvements, or fixes introduced in that release.

### Settings

The app **Settings** tab allows administrators to configure app-specific settings exposed by the app developer. These settings are grouped into sections and rendered dynamically based on how the app was built.

> [!NOTE]
> If you are developing an app using Apps-Engine, learn how these settings are defined and how different input types are configured by referring to the [Apps Settings guide](https://developer.rocket.chat/docs/app-settings).

### Logs

The app **Logs** tab provides a real-time, searchable view into the internal operations of any installed app. It is an essential tool for administrators and developers to debug, audit, and trace app behavior. It displays event-level logs for the app, such as when settings are updated, the app is enabled or disabled, or when other system-level method calls are executed. Additionally, Rocket.Chat automatically redacts potentially sensitive field values from app logs before they are displayed or exported.

Each log entry includes the following information:

- **Timestamp:** The exact time the event occurred.
- **Event name:** The app method or lifecycle hook that was triggered.
- **Severity level:** The log level (`debug`, `info`, or `warning`).
- **Caller:** The origin of the call (e.g., `constructor`, `anonymous`).
- **Execution result:** The output of the method, typically `true`, `false`, or `null`.

Log entries are collapsed by default to present a concise view. You can:

- Click the arrow (▾) next to a log entry to expand it and view detailed execution data.
- View the full JSON-formatted log when expanded, including fields such as `instance`, `events`, `timestamp`, and more.
- Click the **Expand all** button to expand every log entry currently visible on the page.
- Click the **Collapse all** button to collapse every expanded log entry currently visible on the page.
- Click the **Refresh logs** button to update the log feed with the latest events, useful when testing or validating recent changes.
- Use the **Export** button to download the currently filtered view of logs. When exporting, you can:
  - Select between **JSON** and **CSV** formats.
  - Choose to export the **most recent 2000 logs**, or specify a custom limit.
- Control how many logs are shown per page (25, 50, or 100 entries) using the pagination controls. This helps manage large log volumes without impacting interface performance.

> [!NOTE]
> From 8.4, to protect sensitive information, certain field values within log entries may appear as `[redacted]`. This applies to fields that could contain authentication tokens, credentials, API keys, or personal data passed through app methods. Redaction is applied automatically before logs are stored and cannot be disabled. This also applies to exported log files. For example, the app logs can look something like this:
> 
> ```json
> {
>   "_id": "69ef430bc49503b2874e1bbb",
>   "appId": "54588e04-e779-45b4-85de-eb6d186fc859",
>   "method": "api:simple:post",
>   .....
>   "x-user-id": "rocketchat.xyz.abc.test",
>   "x-auth-token": "[Redacted]",
>   "content-type": "application/json",
>   .....
>   "query": {
>      "access_token": "[Redacted]",
>      "query": "[Redacted]"
>     },
>   .....
> }
> ```

#### Filtering options

The app log viewer supports four filtering controls to help narrow down results:

- **Event:** Select a specific app lifecycle event to view. Available options include `app:initialize`, `app:setStatus`, `app:onEnable`, and `app:construct`. Choosing **All** will display logs for all event types. This includes both standard lifecycle events and custom events defined by the app, which may vary between different apps.
- **Time:** Filters logs based on when the events occurred. You can choose predefined ranges such as **Last 5 minutes**, **Today**, or **This Week**, or define a custom time window.
- **Instance**: Filters logs by app instance ID. This is particularly useful if the workspace server has been restarted at some point. A workspace running on a single instance might show more than one instance ID here.
- **Severity:** Filters log entries by severity level. You can apply only one severity filter at a time. All filters affect both the on-screen log display and any exported data. Available options include:
  - **Debug**: Low-level internal messages, typically useful during development.
  - **Info**: Standard operational logs.
  - **Warning**: Potential issues or unusual conditions.

> [!NOTE]
> If you are developing an app using Apps-Engine, refer to the [App Development Lifecycle](https://developer.rocket.chat/docs/app-development-lifecycle) document to learn about the available events and how you can modify this behavior.

### Instances

If your workspace runs on multiple instances, the **App Info** page shows an **Instances** tab. Each instance runs its own copy of the app in its own Apps-Engine, so the app can have a different status on each instance.

The **Instances** tab lists:

- **Workspace instance**: The instance ID, for example `2201496f-a04a-4adf-a266-306b778e3d02`.
- **Status**: The app's status on that instance.

To view the logs for an instance, click the kebab menu (⋮) next to it and select **View logs**. The **Logs** tab opens with the logs filtered to that instance.

#### Mixed status

**Mixed status** means the app doesn't have the same status on every instance. For example, the app can be running on most instances but not on one. Users connected to that instance are affected, while users on other instances aren't.

> [!WARNING]
> Restarting an instance resets the app's status on it. Find the affected instance and export its logs before you restart anything.

To find the affected instance:

1. Open the app's **App Info** page and select the **Instances** tab.
2. Find the instance whose status is different from the others.
3. Click the kebab menu (⋮) next to it and select **View logs**.
4. Click **Export** to download the logs for that instance.

> [!NOTE]
> To learn how to scale your workspace with multiple instances, see the [Running Rocket.Chat with Multiple Instances](/v1/docs/running-multiple-instances) article.