{: .table .table-bordered .table-hover}

| Service Account Setting| Description|

| ------------------------| ----------------|

|**Name**| The name of the service account. <br>The**Admin** label to the right of the name indicates that the service account has been assigned an admin role.NIMA: what is the added value of admin role?|

|**Name**| The name of the service account. <br>The**Admin** label to the right of the name indicates that the service account has been assigned an admin role.|

|**API Keys**| The number of API keys assigned to the service account. <br>Selecting a service account displays the API keys generated for that account. Modify selected scopes by clicking Edit, or delete the API key.|

|**Teams**| The names of the teams the service account is assigned to.|

|**Status**| Indicates if the service account is currently active (**Enabled**) or inactive (**Disabled**). You may want to disable a service account to invalidate its API keys without having to remove the service account, and simply reenable when needed.|

|**Actions**| The options available to manage the service account through its context menu: {::nomarkdown}<ul><li><b>Edit</b>: Modify the settings of the service account, including adding/removing teams, enabling/disabling admin role.</li><li><b>Delete</b>: Delete the service account, including all the API keys defined for the account. This means that actions through the Codefresh API or CLI that require these keys will fail.</li></ul>{:/}|

Authenticate to Amazon ECR registries with credentials from the service account instead of the Access Key ID and Secret Access Key.

This allows pipelines to seamlessly authenticate to Amazon ECR via service account credentials, enhancing security and simplifying access management.

There are two requirements:

1. Set the option to authenticate via service accounts at the account level for pipelines. See[Advanced options for pipelines]({{site.baseurl}}/docs/pipelines/configuration/pipeline-settings/#advanced-options-for-pipelines).

1. Configure Amazon ECR integration to use service account credentials. See[Amazon ECR Container Registry pipeline integration]({{site.baseurl}}/docs/integrations/docker-registries/amazon-ec2-container-registry/).

[Access control for pipelines]({{site.baseurl}}/docs/administration/account-user-management/access-control/)

[Access control for pipelines]({{site.baseurl}}/docs/administration/account-user-management/access-control/)

As a Codefresh account administrator, you can define[global settings for pipelines] which are inherited by all new pipelines created in the account. Users can still override specific settings for individual pipelines.

As a Codefresh account administrator, you can define global settings for pipelines which are inherited by all new pipelines created in the account. Users can still override specific settings for individual pipelines.

||[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.|

|Other|[Advanced options for pipelines](#advanced-options-for-pipelines)| Configureoptionsforbuild approvalandpipeline volumes.|

|Advanced options|[Advanced options for pipelines](#advanced-options-for-pipelines)| Configurethe default behaviorforvolumes, concurrent builds,andauthentication 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.|

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}}

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.

Configure the default settings that definetheadvanced behavior for pipelines.

Configure the default settings that define advanced behavior for pipelines.

* Manage shared volumes for builds pending approval

***Manage shared volumes for builds pending approval**

Define if to[retain or discard]({{site.baseurl}}/docs/pipelines/steps/approval/#keeping-the-shared-volume-after-an-approval) the volume when a pipeline build is pending approval.

This option_affects pipeline resources and/or billing in the case of SaaS pricing_.

It will also affect users of existing pipelines that depend on this behavior.

Once you either enable or disable this option for an account, werecomend leaving it unchanged.

Once you either enable or disable this option for an account, werecommend leaving it unchanged.

* Concurrency policy forbuild pending approval

Determines whetherpipelines pending approval are[included or excluded from the concurrency count]({{site.baseurl}}/docs/pipelines/steps/approval/#define-concurrency-limits).

***Concurrency policy forbuilds pending approval**

Determines whetherpipeline builds pending approval are[included or excluded from the concurrency count]({{site.baseurl}}/docs/pipelines/steps/approval/#define-concurrency-limits).

* ServiceAccountfor Amazon ECR authentication

Define the[Service Account]({{site.baseurl}}/docs/integrations/docker-registries/amazon-ec2-container-registry/#setting-up-ecr-integration---service-account) for Amazon ECRintegration.

***Serviceaccount credentialsfor Amazon ECR authentication**

Define the[Service Account]({{site.baseurl}}/docs/integrations/docker-registries/amazon-ec2-container-registry/#setting-up-ecr-integration---service-account)to optionally useforauthentication inAmazon ECRintegrations.

* Public Marketplace Registry

***Public Marketplace Registry**

Set the default registry from which to pull images for all_Public Marketplace Steps_.

You can select any[Docker Registry]({{site.baseurl}}/docs/integrations/docker-registries/) integrationsetup in Codefresh.

You can select any[Docker Registry]({{site.baseurl}}/docs/integrations/docker-registries/) integrationthat has been set up in Codefresh.

Example: Public Marketplace Step image is defined to use Docker Hub. If you select a`quay.io` integration, all Public Marketplace Step images are pulled from`quay.io` instead of from Docker Hub.

Example: Public Marketplace Step image is defined to use Docker Hub. If you select a`quay.io` integration as the Public Marketplace Registry, all Public Marketplace Step images are pulled from`quay.io` instead of from Docker Hub.

The selected registry affects only custom or typed steps.<br>