> For the complete documentation index, see [llms.txt](https://features.scnd.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://features.scnd.com/v2.0/superadmin/platform-subscriptions/subscriptions.md).

# Subscriptions

## Introduction

The Subscriptions Dashboard presents subscription details using cards, which display when a user subscribes to a plan.

## Dashboard menu

### Export

At the top of the dashboard, administrators can export all details from the Plans Dashboard in CSV format. This functionality enables data analysis using third-party software.

<figure><img src="/files/wOfUpYNUTVoccB14dSZR" alt=""><figcaption></figcaption></figure>

### Sort

The administrator also has the option to sort all the cards in the dashboard by the **date of the update** and the **creation date**.

<figure><img src="/files/TM8fyFRfCNxXClAEiYDV" alt=""><figcaption></figcaption></figure>

### Filters

At the top of the dashboard, users can filter subscription plans based on two criteria: **Created At** and **Updated At**.

* **Created At**: A selected date allows the administrator to filter subscription plans created within the chosen time frame.
* **Updated At**:  A selected date allows the administrator to filter subscription plans updated within the chosen time frame.
* **Status**: The administrator can filter the subscriptions using the following statuses
  * Active
  * Inactive
  * Payment error
  * Paid&#x20;
  * Canceled

## Subscriber card

Each subscription generates a unique subscriber card, enabling the administrator to oversee details related to each user's subscription. Each card provides access to the following information:

* Subscriber name and associated subscription plan
* Subscription status
* Subscription start date
* Assigned subscription roles
* Subscription ID
* Subscription price

<figure><img src="/files/fn2BAQUzwMjgs6HIkDW2" alt=""><figcaption></figcaption></figure>

When the mouse hovers over the right side of the card, an edit icon appears, enabling the administrator to access the user's subscription details.

<figure><img src="/files/xsj9tlDSSzMOAV6GbUGv" alt=""><figcaption></figcaption></figure>

### Subscription details

Accessing a user's subscription details provides an overview of the subscription, displaying the same information found in the subscription card. Additionally, administrators can view all transactions associated with the subscription, along with their respective periods.

<figure><img src="/files/Eu8YQsOMASMQdmJBl2Jh" alt=""><figcaption></figcaption></figure>

The payment information consists of the payment details and the user's registration status in Stripe.

{% hint style="info" %} <mark style="color:blue;">Subscriptions are available only when Stripe is configured as the payment service provider and can be paid exclusively using a credit card.</mark>
{% endhint %}

On the left side of the subscription edit page, the administrator has access to the following information and actions:

* User UID
* User Name
* Subscription Creation date
* Subscription most recent update date

<figure><img src="/files/BFuI71iOOSTvwOU2WdCM" alt=""><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://features.scnd.com/v2.0/superadmin/platform-subscriptions/subscriptions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.