# updateChatParticipantAdmin

Admin permissions of a user in a [basic group](/api/channel.md#basic-groups) were changed

No such constructor in the current schema.

### Parameters

| Name | Type | Description |
| --- | :---: | --- |
| **chat\_id** | [long](/type/long.md) | Chat ID |
| **user\_id** | [long](/type/long.md) | ID of the (de)admined user |
| **is\_admin** | [Bool](/type/Bool.md) | Whether the user was rendered admin |
| **version** | [int](/type/int.md) | Used similarly to `pts` values to deduplicate/update outdated chat information as specified [here »](/api/peers.md#basic-group-updates). |

### Type
[Update](/type/Update.md)

### Related pages

#### [Peer database](/api/peers.md)
Many constructors in the API need to be stored in a local database upon reception and should only ever be updated reactively (passively) when received via updates or by other means (as specified in the documentation), to avoid overloading the server by continuously requesting changes for the same unchanged information.

#### [Channels, supergroups, gigagroups and basic groups](/api/channel.md)
How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.