From ccd8de6e74e81019c39b66d87e12ef33fd2d6b15 Mon Sep 17 00:00:00 2001 From: Mateusz Kwasniewski Date: Mon, 10 Feb 2025 10:25:49 +0100 Subject: [PATCH] docs: remove notifications docs (#9258) --- website/docs/reference/notifications.md | 34 ------------------- .../deploy/configuring-unleash.mdx | 3 +- website/sidebars.ts | 3 +- 3 files changed, 2 insertions(+), 38 deletions(-) delete mode 100644 website/docs/reference/notifications.md diff --git a/website/docs/reference/notifications.md b/website/docs/reference/notifications.md deleted file mode 100644 index 20f0ce50b7..0000000000 --- a/website/docs/reference/notifications.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: Notifications -pagination_next: reference/login-history ---- - -:::note Availability - -**Plan**: [Pro](/availability#plans) and [Enterprise](https://www.getunleash.io/pricing) | **Version**: `4.22+` - -::: - -Unleash's notifications give you updates when certain events occur in projects that you are part of. The notifications are accessible from the notifications button in the navigation section of the admin UI. - -Your notifications will only contain updates from other members; you will not get notifications about actions you perform yourself. - -![The notifications overview. It's telling the user about a feature that was enabled in production and that there is a change request ready for review.](/img/notifications.png) - -From within the notifications list, you can: -* navigate to the features or change request that the notification is for -* mark all notifications as read -* filter out unread notifications - -Notifications can not be disabled. - -## Notification events - -The following actions in your projects will trigger notifications for your project members: -* Creating a feature -* Archiving a feature -* Enabling a feature in an environment -* Submitting a change request -* Approving change request -* Rejecting change request -* Applying change request diff --git a/website/docs/using-unleash/deploy/configuring-unleash.mdx b/website/docs/using-unleash/deploy/configuring-unleash.mdx index c50a240089..0ab6161a58 100644 --- a/website/docs/using-unleash/deploy/configuring-unleash.mdx +++ b/website/docs/using-unleash/deploy/configuring-unleash.mdx @@ -90,8 +90,7 @@ unleash.start(unleashOptions); - `none` - _Deprecated_ Turn off authentication completely. If no API token is provided towards /`api/client` or `/api/frontend` you will receive configuration for the "default" environment. We generally recommend you use the `demo` type for simple, insecure usage of Unleash. This auth type has many known limitations, - particularly related to personalized capabilities such as favorites - and [notifications](../../reference/notifications.md). + particularly related to personalized capabilities such as favorites. - `customAuthHandler`: function `(app: any, config: IUnleashConfig): void` — custom express middleware handling authentication. Used when type is set to `custom`. Can not be set via environment variables. - `initialAdminUser`: `{ username: string, password: string} | undefined` — The initial admin username and password - Defaults to `admin` and `unleash4all`, respectively. Can be set using the `UNLEASH_DEFAULT_ADMIN_USERNAME` and `UNLEASH_DEFAULT_ADMIN_PASSWORD` environment variables. diff --git a/website/sidebars.ts b/website/sidebars.ts index e97b510509..c688e742be 100644 --- a/website/sidebars.ts +++ b/website/sidebars.ts @@ -444,10 +444,9 @@ const sidebars: SidebarsConfig = { type: 'category', link: { type: 'doc', - id: 'reference/notifications', + id: 'reference/login-history', }, items: [ - 'reference/notifications', 'reference/login-history', 'reference/banners', 'reference/command-menu',