---
name: secrets-manager-assign-access
title: Assigning access to Secrets Manager
description: You can enable different levels of access to IBM Cloud&reg; Secrets Manager resources in your IBM Cloud account by creating and modifying IBM Cloud IAM access policies.
last-updated: 2026-07-10
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/secrets-manager?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

{:codeblock: .codeblock}
{:screen: .screen}
{:download: .download}
{:external: target="_blank" .external}
{:faq: data-hd-content-type='faq'}
{:gif: data-image-type='gif'}
{:important: .important}
{:note: .note}
{:pre: .pre}
{:tip: .tip}
{:preview: .preview}
{:deprecated: .deprecated}
{:beta: .beta}
{:term: .term}
{:shortdesc: .shortdesc}
{:script: data-hd-video='script'}
{:support: data-reuse='support'}
{:table: .aria-labeledby="caption"}
{:troubleshoot: data-hd-content-type='troubleshoot'}
{:help: data-hd-content-type='help'}
{:tsCauses: .tsCauses}
{:tsResolve: .tsResolve}
{:tsSymptoms: .tsSymptoms}
{:video: .video}
{:step: data-tutorial-type='step'}
{:tutorial: data-hd-content-type='tutorial'}
{:api: .ph data-hd-interface='api'}
{:cli: .ph data-hd-interface='cli'}
{:ui: .ph data-hd-interface='ui'}
{:terraform: .ph data-hd-interface="terraform"}
{:curl: .ph data-hd-programlang='curl'}
{:java: .ph data-hd-programlang='java'}
{:ruby: .ph data-hd-programlang='ruby'}
{:c#: .ph data-hd-programlang='c#'}
{:objectc: .ph data-hd-programlang='Objective C'}
{:python: .ph data-hd-programlang='python'}
{:javascript: .ph data-hd-programlang='javascript'}
{:php: .ph data-hd-programlang='PHP'}
{:swift: .ph data-hd-programlang='swift'}
{:curl: .ph data-hd-programlang='curl'}
{:dotnet-standard: .ph data-hd-programlang='dotnet-standard'}
{:go: .ph data-hd-programlang='go'}
{:unity: .ph data-hd-programlang='unity'}
{:release-note: data-hd-content-type='release-note'}


# Assigning access to Secrets Manager
{: #assign-access}

You can enable different levels of access to IBM Cloud&reg; Secrets Manager resources in your IBM Cloud account by creating and modifying IBM Cloud IAM access policies.
{: shortdesc}

As an account owner, determine an access policy type for users, service IDs, and access groups based on your internal access control requirements. For example, if you want to grant user access to Secrets Manager at the most minimal scope available, you can [assign access to a secret group](#assign-access-secret-group) in an instance.

To learn more about suggested guidelines for assigning access to secrets, check out [Best practices for organizing secrets and assigning access](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-best-practices-organize-secrets&format=markdown).
{: tip}

## Before you begin
{: #before-access}

Before you get started, be sure that you have [**Administrator** platform access](https://cloud.ibm.com/iam?topic=iam-userroles#platformroles) so that you can further assign roles and customize access policies for others.

## Assigning access to a Secrets Manager instance
{: #assign-access-instance}

To assign access to a Secrets Manager instance and its contained secrets or secret groups, you can use the **Access (IAM)** section of the IBM Cloud console.

1. [Create an access group](https://cloud.ibm.com/docs/iam?topic=iam-groups&interface=ui&format=markdown#create_ag) for the users and service IDs that you want to give access to and add those users to the group.

    For example, you might have a group of security admins that might need the same level of access.
2. After you create a group and add users, go to **Manage > Access (IAM) > Access Groups**.
3. Select a table row, and click the **Actions** menu ![Actions icon](../icons/actions-icon-vertical.svg) to open a list of options for that access group.
4. Click **Assign access**.
5. From the list of services, select **Secrets Manager** and click **Next**.
7. In the Resources section, select **Specific resources**. Choose a region and Secrets Manager service instance. Then, click **Next**.

    If you choose not to provide a specific instance, access is assigned for all instances of the service within the region that you selected. If you choose not to select a region, access is granted for all instances of the service in your account.
8. Choose a combination of [platform and service access roles](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-iam&format=markdown) to assign access for access group.
9. Review your selections and click **Add**.
10. Click **Assign**.

    Now you can add users and service IDs to the access group so that you can assign access to Secrets Manager with a single access policy. For more information, see [Setting up access groups](https://cloud.ibm.com/docs/iam?topic=iam-groups&format=markdown).

## Assigning access to a secret group
{: #assign-access-secret-group}



You can further narrow the scope of access to secrets in your instance by creating and managing [secret groups](#x9968962){: term}.

This process requires two sets of distinct access policies, one with [**Viewer** platform role](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-iam&format=markdown#iam-roles-actions) to be able to view the service instance, and another access policy to further scope the access to the required access groups, by using either the service UI, or the IAM UI.

### Assigning Viewer access to the service instance

{: #assign-viewer-access}

1. In the console, go to **Manage > Access (IAM) > Access Groups**.
2. In the row for the access group that you want to manage, click the **Actions** menu ![Actions icon](../icons/actions-icon-vertical.svg) **> Assign access**.
3. Click **Assign access**.
4. From the list of services, select **Secrets Manager** and click **Next**.
5. In the Resources section, select **Specific resources**.
    1. In the **Instance ID** field, select your Secrets Manager instance.
    2. Click **Next**.
6. Review your selections and **Add**.
7. Click **Assign**.

### Assigning access to a secret group in the service UI
{: #assign-access-secret-group-ui}

[After you create a secret group for your instance](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-secret-groups&format=markdown#create-secret-groups), you can use the **Secret groups** section of the Secrets Manager UI to manage its access.

1. In the console, click the **Menu** icon ![Menu icon](../icons/icon_hamburger.svg) **> Resource List** to view a list of your resources.
2. Select your instance of Secrets Manager.
3. In the navigation, click **Secret groups**.
4. Use the **Secret groups** table to browse the groups in your instance.
5. In the row of the group that you want to manage, click the **Actions** menu ![Actions icon](../icons/actions-icon-vertical.svg) **> Manage access**.
6. Select an access group to give its contained users and service IDs access to your secret group.
7. Choose a combination of [access roles](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-iam&format=markdown) to assign.
8. Click **Review**.
9. Review your selections and click **Assign**.

### Assigning access to a secret group in the console
{: #assign-access-secret-group-console}

You can also use the **Access (IAM)** section of the IBM Cloud console to manage access for your secret groups.

To assign access in the IBM Cloud console, be sure that you have the ID of the secret group that you want to manage. You can copy the ID of a secret group from the **Secret groups** table in your Secrets Manager service instance.
{: note}

1. In the console, go to **Manage > Access (IAM) > Access Groups**.
2. In the row for the access group that you want to manage, click the **Actions** menu ![Actions icon](../icons/actions-icon-vertical.svg) **> Assign access**.
3. Click **Assign access**.
4. From the list of services, select **Secrets Manager** and click **Next**.
5. In the Resources section, select **Specific resources**.
    1. In the **Instance ID** field, select your Secrets Manager instance. Click **Add condition**.
    2. In the **Resource Type** field, type the value `secret-group`. Click **Add condition**.
    3. In the **Resource** field, enter the ID that was assigned to your secret group by the Secrets Manager service.
    4. Click **Next**.
6. Choose a combination of [access roles](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-iam&format=markdown) to assign.
7. Review your selections and **Add**.
8. Click **Assign**.