mirror of
https://github.com/Unleash/unleash.git
synced 2025-02-19 00:15:43 +01:00
docs: remove notifications docs (#9258)
This commit is contained in:
parent
fb68692247
commit
ccd8de6e74
@ -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.
|
||||
|
||||

|
||||
|
||||
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
|
@ -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.
|
||||
|
@ -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',
|
||||
|
Loading…
Reference in New Issue
Block a user