> For the complete documentation index, see [llms.txt](https://docs.secoda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.secoda.co/integrations/data-visualization-tools/microstrategy-one.md).

# MicroStrategy One

An overview of Secoda's MicroStrategy One integration

## MicroStrategy Integration

Connect MicroStrategy to Secoda to discover your reports, dossiers, and datasets. This integration organizes your MicroStrategy content by project with dedicated folders for different content types, making it easy to search and understand your business intelligence assets.

### Overview

The MicroStrategy integration extracts and catalogs the following content types from your MicroStrategy instance:

* **Projects**: Main organizational units containing all other content
* **Reports**: Analytical reports and documents
* **Dossiers**: Interactive dashboards and visualizations
* **Datasets**: Data cubes and analytical datasets
* **Documents**: Supporting documentation and files

### Features

* **Project-based Organization**: Content is organized by MicroStrategy projects with dedicated folders for each content type
* **Comprehensive Discovery**: Automatically discovers all reports, dossiers, datasets, and documents
* **Metadata Extraction**: Captures titles, descriptions, modification dates, and ownership information
* **Hierarchical Structure**: Creates a logical folder structure within each project
* **Search Integration**: All content becomes searchable within Secoda

### Prerequisites

* MicroStrategy instance with REST API access
* Valid MicroStrategy user credentials
* Network connectivity between Secoda and your MicroStrategy instance

### Setup Instructions

#### 1. Configure Integration

1. Navigate to **Integrations** in your Secoda workspace
2. Search for "MicroStrategy" and click **Connect**
3. Fill in the required connection details:
   * **Base URL**: Your MicroStrategy instance URL (e.g., `https://your-instance.microstrategy.com`)
   * **Username**: Your MicroStrategy username
   * **Password**: Your MicroStrategy password

#### 2. Test Connection

Click **Test Connection** to verify your credentials and ensure Secoda can access your MicroStrategy instance.

#### 3. Configure Sync Settings

* **Teams**: Select which teams should have access to this integration
* **Sync Frequency**: Choose how often to sync data (recommended: daily)

#### 4. Start Sync

Click **Create Integration** to begin the initial sync process.

### Content Organization

The integration creates a hierarchical structure within Secoda:

\
├── Project 1\
├── Reports/\
├── Report A\
└── Report B\
├── Datasets/\
├── Dataset A\
└── Dataset B\
├── Documents/\
├── Document A\
└── Document B\
└── Dossiers/\
├── Dossier A\
└── Dossier B

└── Project 2\
├── Reports/\
├── Datasets/\
├── Documents/\
└── Dossiers/


---

# 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.secoda.co/integrations/data-visualization-tools/microstrategy-one.md?ask=<question>&goal=<user_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.