Classic pipeline settings rewrite (#1315)

* Update content

* Update pipeline settings

Restructured and rewrote pipeline settings content

* Update pipelines.md

* Update pipelines.md

* Update

* Update on-prem-feature-management.md

Author: NimRegev

_docs/installation/installation-options/on-premises/on-prem-feature-management.md

@@ -2,8 +2,6 @@
 title: "Codefresh on-premises feature management"
 description: "Enable/disable features for Codefresh accounts in your organization"
 group: installation
-redirect_from:
-  - /docs/installation/on-premises/on-prem-feature-management/
 toc: true
 ---
 
@@ -82,19 +80,19 @@ The table describes in alphabetical order, the features you can open for Codefre
 | `delightedSurvey`            | When enabled, displays Delighted CX surveys in the Codefresh UI. <br>If there are security concerns because of outbound requests from clients, disable this Feature Flag.  | TRUE|  |
 |`dindPodRequestsEqualLimits`   | When enabled, sets both the resource requests and limits for the pod to the same values.|FALSE |  |
 |`disableWelcomeScreen` | When enabled, bypasses the Codefresh Welcome screen that requires the user to enter additional information on first sign-in. <br>Required mostly in on-premises environments, especially for LDAP, which has all login info already configured. | FALSE|  |
-|`disableRolloutActionsWithoutRBAC` |Relevant to GitOps application deployments. <br>When enabled, disables rollback and rollout controls in the Timeline's tab's Rollout Player for the application. {::nomarkdown}<ul><li>Rollback for the selected Rollout. The <b>Choose version to Rollback</b> dropdown is disabled.<br>See <a href="https://codefresh.io/docs/docs/deployments/gitops/manage-application/#manually-rollback-completed-rollout-to-previous-revision">Manually rollback completed rollout to previous revision</a>. </li><li>The <b>Pause</b>, <b>Resume</b>, <b>Skip Step</b> and <b>Promote Full</b> controls in the Rollout Player are also disabled.<br>See <a href="https://codefresh.io/docs/docs/deployments/gitops/manage-application/#manage-an-ongoing-rollout-with-the-rollout-player">Manage an ongoing rollout with Rollout Player</a>.</li></ul>{:/} | FALSE |   |
+|`disableRolloutActionsWithoutRBAC` |Relevant to GitOps application deployments. <br>When enabled, disables rollback and rollout controls in the Timeline's tab's Rollout Player for the application. {::nomarkdown}<ul><li>Rollback for the selected Rollout. The <b>Choose version to Rollback</b> dropdown is disabled.<br>See <a href="https://codefresh.io/docs/docs/deployments/gitops/manage-application/#manually-rollback-completed-rollout-to-previous-revision">Manually rollback completed rollout to previous revision</a>. </li><li>The <b>Pause</b>, <b>Resume</b>, <b>Skip Step</b> and <b>Promote Full</b> controls in the Rollout Player are also disabled.</li></ul>{:/} | FALSE |   |
 | `disableInviteWelcomeMail`     | When enabled, does not send the Welcome email to users invited to an account.      | FALSE         |  |
-|`forbidDecrypt` |When enabled, prevents users from decrypting secrets when running the `codefresh get context --decrypt` command. <br>Users can bypass this by running `--decrypt` with the built-in `CF_API_KEY` command that is injected into every build. |FALSE| . |
+|`forbidDecrypt` |When enabled, prevents users from decrypting secrets when running the `codefresh get context --decrypt` command. <br>Users can bypass this by running `--decrypt` with the built-in `CF_API_KEY` command that is injected into every build. |FALSE|  |
 | `fullstory`                   | When enabled, allows Codefresh to track user activity in the Codefresh UI through Fullstory.<br>**NOTE**: When enabled for air-gapped environments, client attempts to communicate with a Fullstory service may result in network errors.| FALSE  |  |
 | `genAICronExpression`       | When enabled, supports generating Cron expressions in the Codefresh UI using Generative AI.| FALSE  |   |
 |`gerritIntegration`      | When enabled, enables Gerrit integration in Account settings. See also `supportGerrit`. <br>See [Gerrit as Git provider for pipelines]({{site.baseurl}}/docs/integrations/git-providers/#gerrit).    | FALSE         |  |
-|`gitopsArgoCdRollback` |Relevant to GitOps application deployments.<br>When enabled, allows you to rollback active GitOps applications to previously deployed versions.<br>See [Rollback GitOps applications]({{site.baseurl}}/docs/deployments/gitops/manage-application/#rollback-gitops-applications).| FALSE |  |
-| `gitopsAppGroups`       | When enabled, allows users to group GitOps applications by annotations, and view these applications in the Groups tab of the GitOps Apps dashboard. <br>See [Application Groups for GitOps applications]({{site.baseurl}}/docs/deployments/gitops/gitops-app-groups/). | TRUE   |  |
+|`gitopsArgoCdRollback` |Relevant to GitOps application deployments.<br>When enabled, allows you to rollback active GitOps applications to previously deployed versions.<br>See [Rollback GitOps applications]({{site.baseurl}}/docs/deployments/gitops/manage-application/#rollback-argo-cd-applications).| FALSE |  |
+| `gitopsAppGroups`       | When enabled, allows users to group GitOps applications by annotations, and view these applications in the Groups tab of the GitOps Apps dashboard. <br>See [Application Groups for Argo CD applications]({{site.baseurl}}/docs/deployments/gitops/gitops-app-groups/). | TRUE   |  |
 | `gitopsOnboarding` | When enabled, enhances the onboarding user-experience.| FALSE  | _New in v2.6_ |
 | `gitopsGroupsPage` | When enabled, on selecting **GitOps Apps** from the sidebar, opens the **Groups** tab instead of the Applications tab.| TRUE  | _New in v2.6_ |
 | `gitopsEnvironments` | When enabled (the default), displays the Environments dashboard option in the sidebar, and enables users to manage environments.| TRUE  |_New in v2.6_ |
 | `gitopsDynamicBreadcrumbs`     | When enabled (the default), supports rendering dynamic breadcrumbs for GitOps.   | TRUE         |  |
-|`gitopsImageReporting` |Relevant to ProjectOne.<br>When enabled, reports images created with Codefresh Pipelines to the Images dashboard. <br>See [Images in Codefresh]({{site.baseurl}}/docs/dashboards/images/).| FALSE |  |
+|`gitopsImageReporting` |When enabled, reports images created with Codefresh Pipelines to the Images dashboard. <br>See [Images in Codefresh]({{site.baseurl}}/docs/dashboards/images/).| FALSE |  |
 | `hideCompositionsMenuItem`     | When enabled, does not show Compositions within Artifacts & Insights in the sidebar of the Codefresh UI. | FALSE  |
 |`injectClusterListFromPipelineSettings` | When enabled, turns on the pipeline setting **Kubernetes cluster context pipeline injection** for the account. Individual users can then selectively inject clusters for pipelines from those to which they they access.<br><br> This feature requires the users to have the Update Cluster permission. If not granted, then this feature has no impact when enabled. <br>See [Enabling cluster-contexts for pipelines]({{site.baseurl}}/docs/pipelines/configuration/pipeline-settings/#kubernetes-cluster-contexts-for-pipelines). | FALSE|   |
 |`logMasking` |When enabled, secrets in build logs, both online and offline logs, are masked and replaced by asterisks. <br><br>This feature is currently available only for Enterprise customers. |FALSE|  |
@@ -132,4 +130,4 @@ The table describes in alphabetical order, the features you can open for Codefre
 ## Related articles
 [Codefresh on-premises installation]({{site.baseurl}}/docs/installation/on-premises/)  
 [Codefresh on-premises upgrade]({{site.baseurl}}/docs/installation/on-premises/codefresh-on-prem-upgrade/)  
-[Codefresh on-premises account & user setup]({{site.baseurl}}/docs/installation/on-premises/on-prem-configuration/)  
+[Codefresh on-premises setup]({{site.baseurl}}/docs/installation/on-premises/on-prem-configuration/)  

_docs/pipelines/configuration/pipeline-settings.md

@@ -1,6 +1,6 @@
 ---
 title: "Account-level settings for pipelines"
-description: "Configure global pipeline settings for the account"
+description: "Configure settings pipelines at the account-level"
 group: pipelines
 sub_group: configuration
 redirect_from:
@@ -26,9 +26,9 @@ Users can still override specific settings for individual pipelines.
 | |[Restarting from failed steps](#restarting-from-failed-steps) | Enable option to restart pipelines from failed steps instead of from the beginning.|
 | |[Memory usage warning for pipeline builds](#memory-usage-warning-for-pipeline-builds)| Enable alerts when pipelines reach/exceed the threshold. |
 | |[Default behavior for build step](#default-behavior-for-build-step)| Configure push image options for build steps.  |
-| |[Default behavior for pending-approval step](#default-behavior-for-pending-approval-step) | Determine if `pending-approval` steps require manual action. |
-|Advanced options|[Advanced options for pipelines](#advanced-options-for-pipelines) | Configure the default behavior for volumes, concurrent builds, and authentication for Amazon ECR integrations, and more. |
-|Argo Workflows |[Enable pipelines with Argo Workflows]({{site.baseurl}}/docs/workflows/create-pipeline/) | Create pipelines based on Argo Workflows. |
+| |[Default behavior for pending-approval step](#default-behavior-for-pending-approval-step) | Determine if pending-approval steps require manual action. |
+|Other|[Advanced options for pipelines](#advanced-options-for-pipelines)| Configure options for build approval and pipeline volumes. |
+|Argo Workflows |Enable pipelines with Argo Workflows | Create pipelines based on Argo Workflows. |
 
 
 
@@ -117,10 +117,12 @@ Define if users can create pipelines from pipeline templates or by cloning exist
 
 If required, restrict the sources from which users can create or upload YAML files for a pipeline workflow.
 
+The options are:
 * **Inline YAML**: Enable/disable the [inline editor]({{site.baseurl}}/docs/pipelines/pipelines/#using-the-inline-pipeline-editor) where YAML is stored in Codefresh SaaS
 * **YAML from repository**: Enable/disable pipeline uploading YAMLs from connected Git repositories
 * **YAML from external URLs**: Enable/disable loading YAMLs for pipelines from [external URLs]({{site.baseurl}}/docs/pipelines/pipelines/#loading-codefreshyml-from-version-control)
 
+
 >**NOTE**  
 You must allow at least one of these options so that users can create new pipelines.  
 We suggest selecting the **Inline YAML** option when users are still learning about Codefresh and want to experiment. 
@@ -144,8 +146,7 @@ As a Codefresh administrator, you can override the account-level scopes for a sp
 
 
 ## Kubernetes cluster-contexts for pipelines
-By default, all pipelines in the account can access all clusters integrated with Codefresh.  
-Restrict pipeline access to clusters by enabling cluster-injection for pipelines in the account. When enabled, users are required to select the clusters for the pipeline build.
+By default, all pipelines in the account can access all clusters integrated with Codefresh. Restrict pipeline access to clusters by enabling cluster-injection for individual pipelines in the account.
 
 Selectively restricting access to clusters for a pipeline:  
 * Enhances security by restricting access to users from different teams. 
@@ -188,23 +189,14 @@ max-width="60%"
 ## Restarting from failed steps
 Enable or disable restarting pipelines directly from the failed step for all pipelines in the account. The setting affects the restart options displayed in the [Builds view]({{site.baseurl}}/docs/pipelines/monitoring-pipelines/#restart-pipeline-from-builds-view) and [step view]({{site.baseurl}}docs/pipelines/monitoring-pipelines/#restart-from-step-view). 
 
-{% include image.html
-lightbox="true"
-file="/images/pipeline/settings/account-permit-restart.png"
-url="/images/pipeline/settings/account-permit-restart.png"
-alt="Enable/disable restart from failed step"
-caption="Enable/disable restart from failed step"
-max-width="60%"
-%}
-
-* When **enabled** (the default), allows users to restart the pipeline directly from the specific step that failed. 
+* When **enabled**, allows users to restart the pipeline directly from the specific step that failed. 
 * When **disabled**, allows users to restart the pipeline from the beginning.
 
-Individual pipeline are set to use the account's setting by default, but users can override this setting to enable/disable failed step restart for the specific pipeline. See [Pipeline settings - Policies]({{site.baseurl}}/docs/pipelines/pipelines/#policies).
+Individual pipeline are set to use the account's setting by default, but users can override this setting to enable/disable failed step restart for the specific pipeline. See [Pipeline settings - Policies]({{site.baseurl}}/docs/docs/pipelines/pipelines/#policies).
 
 ## Memory usage warning for pipeline builds
 Select the memory-usage threshold for pipeline builds at which to display alerts. <br>
-Memory-usage thresholds for pipeline builds are useful get timely warnings and prevent build failures, while at the same time avoiding premature and unnecessary warnings.
+Memory-usage thresholds for pipeline builds are useful to both avoid premature and unnecessary warnings, and get timely warnings to avoid build failures, as needed.
 
 Accounts with pipelines that do not consume a lot of memory can have higher thresholds, or even the maximum threshold, as they are unikely to hit available memory limits.  
 Resource-intensive pipelines on the contrary require lower thresholds for timely warnings to prevent build failures. 90% is recommended for such pipelines.
@@ -240,7 +232,7 @@ This behavior is simply a convenience feature for legacy pipelines.
 Users can still use a [`push` step]({{site.baseurl}}/docs/pipelines/steps/push/) to always push an image to a registry regardless of what was chosen in the `build` step.
 {{site.data.callout.end}}
 
-## Default behavior for `pending-approval` step 
+## Default behavior for `pending-approval` step
 Configure if manual confirmation is required after clicking the Approve or Reject buttons for [pending-approval steps]({{site.baseurl}}/docs/pipelines/steps/approval/). When required, a confirmation prompt is displayed on clicking Approve or Reject.  
 * **None**: No manual intervention required on clicking either Approve or Reject. 
 * **All**: Require manual intervention for both Approve and Reject.