How admin invite differs
Admin invite changes administrative permissions. Its two stages prepare your working administrators and invite users through those administrators. This guide covers inviteadmin, not the separate inviteadmin_v2 module.
Preparation grants administrative rights to selected accounts. User mode promotes a recipient and then demotes them. Test this in a community you control and inspect the actual administrator list afterward. It is not an ordinary invitation with no permission changes.

The retained screenshots use Russian. The current form separates the stages; some labels may differ.
Prepare access and destination
Specify the group or channel. The assigning account needs ownership or administrator rights that include adding administrators. Permission to invite members alone is insufficient. Check community access, session state and connectivity in the account panel.
Use accounts and communities you are authorized to manage. Record the existing administrators and intended final permissions before testing. A completed task is not a replacement for checking those permissions.
Prepare administrators
The targets at this stage are your own working accounts, not an external user list.
- Select the main administrators who will grant rights.
- In the separate assignment list, select future working administrators. Check their membership: a non-member can be skipped.
- Keep the two lists separate. The interface resolves intersections, so recheck both pools after selecting accounts.
- Start assigning administrators, then review every result in the log and Telegram.
- Once complete, move to user invitation with the prepared list.

The current preparation mode processes the selected assignment list. Do not rely on the maximum-assignments field as a strict stop: limit the list itself. Preparation grants the full rights implemented for that community type, so do not add unnecessary accounts as reserves.
Invite users
If working administrators already exist, start directly at this stage.

Enter users manually or load TXT and review identifiers. Administrator accounts are the workers; list entries are the recipients. Do not put recipients into the application's account selector.
Choose prepared administrators and start user invitation. The current run distributes recipients between workers. Use a small separate test list; restarting the original list is not guaranteed continuation excluding every previously performed action.
Volume and pauses

| Setting | Check |
|---|---|
| Threads | Concurrent worker accounts |
| Maximum invites | Counted invitation limit per worker in user mode, not guaranteed new members |
| Users per series | Recipient batch size before its pause |
| Delay | Seconds between batches; lower bound must not exceed upper bound |
| Thread-start delay | Spreads account startup, not recipient processing |
| Maximum FloodWait | Handling threshold, not cancellation of Telegram's wait |
| Change after attempts | Error-related account handling; inspect the stopping reason |
| Next account on FloodWait | User-mode behavior during a wait |
| Leave afterward | Working account exits; enable only when needed |
Here the bot-protection check reads the latest message and waits. It does not solve arbitrary bot challenges. Unlike this option, ordinary invite's similarly named setting is currently unavailable.
Check promotions and demotions
Distinguish administrator assignment, user invitation/demotion, skips and errors in the report. If an error occurs between promotion and demotion, check the recipient's permissions manually. Stopping a task does not prove every permission change was reversed.
For CHATADMINREQUIRED, check the actual right to appoint administrators. Investigate unresolved users and non-members rather than increasing threads. Respect the reported FloodWait. Compare successful results with membership and the administrator list.
For the ordinary workflow, use the invite guide. See also adding administrators and removing rights. More instructions are in the catalog; installers are on the download page.