Teams
Microsoft Teams setup lets you brand the Leena AI Teams app for your organisation and download the app package to upload into Teams.

Where to find it
Open the Admin Console, then go to External channels → Teams.
Credentials are set up separatelyThis page handles branding and the app package. The underlying Teams credentials are added by the Leena AI team on the flow dashboard, not here.
Until they're in place, the page shows We're setting up your channel instead of the form. Leena AI team members see Set up credentials at this point, with a pointer to the flow dashboard.
Branding details
Add the name, descriptions, and icons that define how the app appears in Teams. Every field is required. Each one maps to the equivalent field in the Teams app manifest, and the length limits are Microsoft's — Leena AI checks them before it builds the package.
| Field | Limit | What it is |
|---|---|---|
| Short Name | 30 characters | The app's name in Teams |
| Long Name | 100 characters | The full name |
| Short Description | 80 characters | One-line summary |
| Long Description | 4000 characters | Full description shown in the app details |
| Tab App Name | 30 characters | The label employees click to open the app — for example, Home |
Icons
Both icons must be .png files of up to 3 MB, at an exact size. Leena AI checks the dimensions when you submit and shows an error if either icon is the wrong size.
| Field | Requirement |
|---|---|
| App icon colour | 192 × 192 px .png |
| App icon (outline) | 32 × 32 px .png with a transparent background |
Leena AI checks the outline icon's size but not its background. Microsoft expects a white icon on a transparent background, so check this before you submit — a solid background still passes here.
Generating the app package
Submit saves the branding and builds the app package: a zip containing the Teams manifest and both icons. The button becomes active once you change something on the form, and Cancel discards unsaved changes.
The first time you submit, Leena AI also finishes configuring the app's Microsoft registration in the background — client secret, sign-in scopes, Teams client pre-authorisation and Microsoft Graph permissions. A progress bar shows each step, and the page updates on its own when it's done.
Once ready, an information bar confirms Your branding is ready with a Download zip action. The file is named after the Short Name and the package version — for example, Leena-v1.0.0.zip.
After the first package, Submit becomes Update branding. Use it to revise the details and regenerate the package; each update raises the package version (1.0.0 → 1.0.1 and so on), so Teams treats it as a new version of the same app.
External app ID
Once the first package has been generated, an optional External app ID field appears above the branding details. After you've uploaded the app to Teams, you can enter the app ID Teams assigned to it (in GUID format). Leena AI uses it to build links that open the Leena AI app in Teams.
Uploading to Teams
Upload the downloaded zip into Microsoft Teams as a custom app, through the Teams admin centre or by sideloading, depending on your organisation's policy.
To roll the app out to a specific group of employees and pin it in their Teams app bar, follow Setup user group policies for Microsoft Teams apps in the Appendix. It covers uploading or updating the package in the Teams admin centre, granting admin consent, and assigning an app setup policy to a group.
For your security review — the Microsoft permissions the app requests, how sign-in and notifications work, and the domains it loads — see Microsoft Teams app: permissions, data and security.
Re-uploading a regenerated package is how branding changes reach employees — editing the branding here alone doesn't update an app already installed in Teams.
Updated 11 days ago
