Known limitations

_include/alerts-notifications-retention-notes.adoc

@@ -0,0 +1,7 @@
+//tag::alerts-retention[]
+NOTE: Alerts are retained in NetApp Console local deployment for 7 days from the time they are raised.
+//end::alerts-retention[]
+
+//tag::ui-notification-retention[]
+NOTE: Console UI notifications are retained for 24 hours.
+//end::ui-notification-retention[]

reference-local-known-limitations.adoc

@@ -28,4 +28,18 @@ include::_include/os-reqs.adoc[tag=ip-range-conflict]
 NetApp Console local deployment isn't supported on a VM that is shared with other applications. The VM must be dedicated to the NetApp Console local deployment.
 
 === Third-party agents and extensions
-Third-party agents or VM extensions are not supported on the NetApp Console local deployment VM.
+Third-party agents or VM extensions are not supported on the NetApp Console local deployment VM.
+
+== Identity and access limitations
+
+[cols="1,3",options="header"]
+|===
+| Area
+| Limitation
+
+| Local user onboarding and account recovery
+| An SMTP email server must be configured before you can invite local users or use password reset for local users.
+
+| Active Directory integration
+| Duplicate email addresses are not supported across local users and Active Directory users. For example, if the initial local organization admin later adds themselves as an Active Directory user, they must use a different email address.
+|===

task-alert-rules-manage.adoc

@@ -30,6 +30,8 @@ A notification rule matches alerts based on conditions you define—such as serv
 * To deliver notifications by email, your Organization admin must configure an email server in the Console local deployment. To deliver notifications to an external system, your Organization admin must configure a webhook. For the steps, see link:task-console-configure-notifications-delivery.html[Configure notification delivery].
 * The Console local deployment Notification Center displays notifications by default, so no additional setup is required for in-console notifications.
 
+include::_include/alerts-notifications-retention-notes.adoc[tag=ui-notification-retention]
+
 == View notification rules
 
 The notification rules page is the central place to review and manage every rule that applies to your organization. Each rule shows its key attributes so that you can quickly assess and adjust your alerting behavior.

task-alerts-monitor.adoc

@@ -25,6 +25,8 @@ For ONTAP alerts, you can access tools such as System Manager and Workload Analy
 
 For external reporting, you can export the alerts list to a CSV file for offline analysis.
 
+include::_include/alerts-notifications-retention-notes.adoc[tag=alerts-retention]
+
 NOTE: You can also set up notification rules to receive alerts by email or webhook. link:task-alert-rules-manage.html[Learn how to set up alert notifications].
 
 == Available alerts

task-console-configure-notifications-delivery.adoc

@@ -22,6 +22,8 @@ Super admin or Organization admin. link:reference-iam-predefined-roles.html[Lear
 
 By default, Console local deployment displays notifications through its built-in notification system. Configuring additional delivery channels lets you receive notifications in the way that best fits your workflow.
 
+include::_include/alerts-notifications-retention-notes.adoc[tag=ui-notification-retention]
+
 You can send all notifications through the same channels or use different channels for different notification types. For example, you might send urgent storage alerts through email while routing other alert traffic to a third-party monitoring tool through a webhook.
 
 

task-get-help.adoc

@@ -1,7 +1,7 @@
 ---
 sidebar: sidebar
 permalink: task-get-help.html
-keywords: help, ticket, open support case, support, netapp support, technical support, call support, phone number, open ticket, web ticket, open an issue
+keywords: help, ticket, open support case, support, netapp support, technical support, call support, open ticket, web ticket, open an issue
 summary: NetApp provides support for NetApp Console local deployment in a variety of ways. Extensive free self-support options are available 24x7, such as knowledge base (KB) articles and a community forum. Your support registration includes remote technical support via web ticketing.
 ---
 

task-iam-manage-members-permissions.adoc

@@ -84,6 +84,8 @@ link:reference-iam-predefined-roles.html[Learn about access roles].
 +
 The Console emails instructions to the user.
 
+NOTE: Local user invitation links are single-use and expire after 7 days. If a link expires before the user completes setup, remove the user and add them again to send a new invitation link.
+
 
 
 [[service-account]]

task-install-agent-on-prem-ova.adoc

@@ -86,11 +86,6 @@ b. Select *Actions* > *New VM from this template*
 ** If you selected explicit proxy, enter the proxy server hostname or IP address and port number, as well as the username, password. 
 ** If you selected transparent proxy, upload the respective certificate.
 * *Virtual Machine Configuration*
-** *Skip config check*: This check box is unchecked by default which means the NetApp Console local deployment runs a configuration check to validate network access. 
-*** NetApp recommends leaving this box unchecked so that the installation includes a configuration check of the NetApp Console local deployment. The Configuration check validates that the NetApp Console local deployment has network access to the required endpoints. If it deployment fails because of connectivity issues, you can access the validation report and logs from the NetApp Console local deployment host. In some cases, if you are confident that the NetApp Console local deployment has network access, you can choose to skip the check.
-
-
-
 
 ** *Maintenance password*: Set the password for the `maint` user that allows access to the NetApp Console local deployment maintenance console.
 ** *NTP servers*: Specify one or more NTP servers for time synchronization.