# Telegram group add link requests admin rights up front

> Use `startgroup` or `startchannel` links with the right admin permissions before rollout, so the bot lands in the team context with enough authority to do the job on day one.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/telegram-group-add-link-requests-admin-rights-up-front/
- Source: [core.telegram.org](https://core.telegram.org/api/links)
- GrowthDex source hub: [Deep links](/sources/deep-links-core-telegram-org/)
- Last checked: 2026-06-09T04:07:00.000Z
- Rarity: rare
- Budget: low
- Channels: Onboarding, Product, Activation
- Stages: telegram mini apps, group rollout, admin rights, collaboration UX


## Why this can grow

A collaborative Mini App often fails for a boring reason: the bot is added to the chat, but it cannot actually perform the action that justified the install. Telegram's deep-link docs are unusually explicit here. Group and channel links can request admin permissions up front, and group links can also pass a start parameter after the bot is added. That turns the invite link into a qualification tool. If the job needs pinning, posting, or topic management, ask for the right shape of install instead of leaving the operator to fix permissions later.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where telegram group add link requests admin rights up front can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Onboarding and Product channel.
3. Use the evidence from core.telegram.org to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

Telegram documents `startgroup` and `startchannel` links that can request combinations of admin rights like `post_messages`, `pin_messages`, `manage_topics`, and `invite_users`, while group links can also invoke the bot with a start parameter after install.

## Adjacent tactics in the same lane

- [Slack onboarding starts at the first invocation context](/growth-ideas/slack-onboarding-starts-at-the-first-invocation-context/) - 3 shared channels
- [Google Chat app command menu for fast and typed jobs](/growth-ideas/google-chat-app-command-menu-for-fast-and-typed-jobs/) - 3 shared channels
- [Telegram menu button matches the user state](/growth-ideas/telegram-menu-button-matches-the-user-state/) - 2 shared channels, 1 shared stage
- [Teams default install scope matches the first job](/growth-ideas/teams-default-install-scope-matches-the-first-job/) - 3 shared channels

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The Telegram Mini App should open where the habit already lives](/blog/the-telegram-mini-app-should-open-where-the-habit-already-lives/) - product-led growth, onboarding, brand trust

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.