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

# Becoming a Strategy Distributor

> Understand how to surface strategies and manage the user portfolio lifecycle.

A strategy distributor offers Glider strategies to users through an
application. The distributor selects the strategy, manages the user and wallet
experience, and connects the user to Glider's portfolio lifecycle.

The distributor does not control the strategy's allocation or schedule unless
it is also the strategy provider. Glider creates the user portfolio and smart
accounts, then runs the permitted automation.

## What a distributor manages

* Select and present strategies to users.
* Associate each user with the correct wallet.
* Request and submit user-signed enrollment and withdrawal authorizations.
* Guide users through funding their portfolio smart accounts.
* Surface portfolio status, positions, performance, and operations.
* Communicate material strategy changes to enrolled users.

One company can be both the strategy provider and the distributor. See
[Becoming a Strategy Provider](/guides/strategy-provider-overview) if you also
create and manage the source strategy.

## Choose a strategy

You can distribute:

* A strategy owned by your tenant, including a private strategy.
* A public strategy from another provider when you have its `strategyId`.
* A Glider-selected strategy returned by `GET /v2/discovery/strategies`.

Read the current strategy before you present it. Use its stable `strategyId`
throughout enrollment and portfolio management. Public status does not
guarantee placement in Glider's curated or top-performing collections.

## Distribution flow

1. **Present the strategy.** Show users the current strategy information that
   is relevant to their decision.
2. **Enroll the user.** Use the
   [Two-Stage Enrollment](/guides/two-stage-enrollment) flow to collect the
   user's authorization and create a portfolio.
3. **Fund the portfolio.** Send assets to the correct chain-bound smart
   account. See [Fund a Portfolio](/guides/portfolio-deposit).
4. **Operate and monitor.** Use
   [Portfolio Automation](/guides/portfolio-automation) and the portfolio read
   endpoints to surface status, positions, and performance.
5. **Support exits.** Use
   [Two-Stage Withdrawal](/guides/two-stage-withdrawal) when a user withdraws
   or liquidates assets.

The detailed guides contain the request bodies, signature rules, and retry
requirements for each step.

## When the provider updates a strategy

The `strategyId` remains the same when the provider updates metadata, changes
the schedule, or publishes an allocation version. A new strategy version
becomes active immediately. Enrolled portfolios use the new target during
their next rebalance.

Keep the strategy information in your application current. Tell enrolled users
about material changes that affect the product you present.

## Distributor responsibilities

* Keep the Glider API key on your backend.
* Show users the exact authorization that they will sign.
* Keep signed payloads unchanged between stages.
* Map each user identity to the correct wallet and portfolio.
* Reuse idempotency anchors when you retry a request.

Use the [Glider Console](https://console.glidercloud.dev/) to get access and
manage B2B API keys.

## Next steps

* [Two-Stage Enrollment](/guides/two-stage-enrollment)
* [Fund a Portfolio](/guides/portfolio-deposit)
* [Portfolio Automation](/guides/portfolio-automation)
* [Updating Portfolios](/guides/portfolio-update)
* [Two-Stage Withdrawal](/guides/two-stage-withdrawal)