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

# TD SYNNEX Stellr

> Connect TD SYNNEX StreamOne Stellr so agents can read customers, subscriptions and prices, create subscriptions, and add or remove licence seats

Neo connects to the StreamOne Stellr API, the cloud marketplace TD SYNNEX resellers in North and Latin America buy Microsoft 365 and other subscriptions through. With it connected, an agent can:

* Find the Stellr customer behind a PSA company, and the Microsoft tenant on its vendor account
* Read subscriptions with their seat counts, renewal dates and auto-renew settings
* Look up products and prices, and read invoices
* Create a customer or a new subscription, and follow the provisioning operation to completion
* Add or remove seats on an existing subscription with [Change License Seats](/agents/tools/m365/change-license-seats)

<Note>
  If your portal is StreamOne ION, the global TD SYNNEX platform, connect [TD SYNNEX ION](/integrations/marketplaces/td-synnex) instead. The two use different APIs and different credentials.
</Note>

## Connect TD SYNNEX Stellr

You need a **Client ID** and a **Client Secret** from the Stellr Developer Portal.

<Steps>
  <Step title="Enroll for API access">
    Sign in to ECExpress and open **StreamOne Stellr → Integration → Developer APIs**. Enroll, then open the **Developer Portal**.
  </Step>

  <Step title="Create a client credential">
    In the Developer Portal, open **My Account → Client Credentials** and create a **Prod** credential. Copy the **Client Secret** now, because the portal shows it only once. Give the credential the **End Customers** and **Subscriptions** API permissions. A new credential can take up to 10 minutes to start working.
  </Step>

  <Step title="Save it in Neo">
    Open [**Integrations**](https://dashboard.neoagent.io/integrations?open=td_synnex_stellr), select **TD SYNNEX Stellr**, and enter the Client ID and the Client Secret. Set **Region** to the region your reseller account belongs to (United States, Canada, Brazil or Mexico). Leave **Environment** on **Production** unless TD SYNNEX gave you sandbox credentials; a sandbox credential works only against the sandbox. Click **Save**. Neo checks the credential against your region before it saves, so a wrong secret, region or environment is refused on the spot.
  </Step>
</Steps>

## Customer mapping

Neo maps each Stellr customer to a PSA company after you save the credentials, and again after each PSA sync:

1. **Microsoft tenant**: the Microsoft ID on the customer's Stellr Microsoft vendor account matches the **Tenant ID** on one of your companies. This is an exact match.
2. **Name**: the customer's company name matches a PSA company name.
3. **AI suggestion**: for the names the first two steps miss.

Review the result under **Integrations → TD SYNNEX Stellr → Organization Mapping**. Map a customer left unmapped, or correct a match; a manual mapping is kept across syncs.

Seat changes spend money, so only a tenant match, an exact one-to-one name match, or a mapping you confirmed selects the customer for a seat change. A suggested match lists for confirmation and never changes seats on its own. To override the mapping for one company, enter its Stellr customer number as a **Marketplace Company ID** on the [Companies](https://dashboard.neoagent.io/end-companies) page; a typed ID always wins.

## What agents can do

Agents call Stellr through the [Vendor API](/agents/tools/vendor-api) tool, which is added when you give the agent TD SYNNEX Stellr permissions in its settings. Each permission group has its own access level, covering customers and their Microsoft tenants, the catalogue and prices, subscriptions and provisioning operations, and invoices.

The access profiles are **Read Only**, **Helpdesk** (every change asks a technician first) and **IT Admin** (no approval). You can set approval per permission group. Seat changes go through Change License Seats, never through the Vendor API tool, and follow that tool's own approval setting.

### Seat changes

To add or remove seats on a subscription a customer already holds, the agent uses [Change License Seats](/agents/tools/m365/change-license-seats). It serializes changes to one subscription, so two changes at the same time cannot both start from the same count. It asks Stellr for the new total seat count, waits for Stellr's provisioning operation to finish, and reads the subscription back to confirm the new count. The wait has a time limit, about 30 seconds in a chat and 90 seconds in an automation. When Stellr takes longer, the agent reports the change as unconfirmed, and you can check the count in the Stellr portal.

A Stellr subscription keeps at least one seat. To remove the last seat, cancel the subscription.

Neo does not schedule a Stellr seat change for the renewal date yet, so a seat change applies immediately. To change seats at renewal, schedule the workflow to run on the renewal day.