# Admin-HWIDS

`adminHwids` — a list of device HWIDs that the provider has been granted **admin privileges** within a specific subscription domain. There are two privileges: viewing/editing server configs directly in the app and sending push notifications bypassing moderation.

***

## Where it is set

The provider adds the HWID to [the web panel](https://web.incy-panel.com/) in the domain settings, in the **Admin access**. The field is stored in `SubscriptionSettings` and returned to the client via [Premium API](broken://pages/55413640d0975240d1f826f63d0ddeb322f3df1a):

| Field        | Type       | Description                                                                  |
| ------------ | ---------- | ---------------------------------------------------------------------------- |
| `adminHwids` | `string[]` | An array of HWIDs in a format identical to what the client sends as `x-hwid` |

HWID format — see [hwid.md](broken://pages/de7b1721afd8537518b2ab87e0bc4ff47ae3c0cf). Comparison is done **character by character** (without case normalization), i.e. you need to copy the HWID exactly as the app sees it in its settings.

***

## Privilege 1: viewing and editing server configs

If the device HWID is included in `adminHwids` the current subscription:

* An edit button appears on the server card in the app (usually hidden from other users).
* The device can edit VLESS/VMess/Trojan/... parameters directly in the UI: address, port, UUID, transport settings.
* The edits apply **only locally** on this device — they are not sent back to the subscription. At the next `refresh` of the subscription, the server will revert to the provider’s version.

Used for debugging: the provider, acting as a “their own” device, can check how a specific key or transport parameter works without rewriting the config on the server side.

***

## Privilege 2: sending notifications without moderation

By default, any notification the provider sends from the panel goes into the `pendingNotifications` collection with status `pending` and waits for approval from an INCY moderator (via the support bot).

If the targeting specifies a **specific HWID** and this HWID is present in `adminHwids` any verified provider domain:

* The record in `pendingNotifications` is created immediately with status `approved`.
* Field `autoApproved: true`, `autoApproveReason: "adminHwid"` — for auditing.
* The FCM broadcast starts immediately — without waiting for moderation.

This is needed for debugging your own notifications: the provider sends a test to their personal device and instantly sees the result.

> **Important:** auto-approve triggers only when `targetSegment.hwid` is set **and** matches one of `adminHwids`. Notifications without HWID targeting or to someone else’s HWID still go through moderation. More details — [provider-notifications.md](broken://pages/0f228ec3507d2d2ae7345eeeb0598c11dcc4519c).

***

## Hygiene

* Keep only your own devices in `adminHwids` . Admin access gives a bypass for push notification moderation — a random HWID from another user could spam the other subscribers.
* The device HWID changes after a factory reset or OS reinstallation — the list `adminHwids` needs to be updated.
* Removing an HWID from the list takes effect the next time the device receives the config (typically 1–5 minutes, depending on cache).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://incy.gitbook.io/docs/docs-en/premium-api/admin-hwids.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.