---
name: vpc-file_storage_vpc_xaccount_share_access_removal
title: Removing access to a file share from other accounts
description: Revoke cross-account access to file shares by removing IAM authorizations and deleting accessor share bindings to sever mount target connections.
last-updated: 2026-07-08
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/vpc?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.

# Removing access to a file share from other accounts
{: #file-storage-accessor-delete}

Revoke cross-account access to file shares by removing IAM authorizations and deleting accessor share bindings to sever mount target connections.
{: shortdesc}

When you no longer want to allow another account or service to have access to your file share data, you can revoke their access at any time. To revoke access, first remove the IAM authorization. Removal of the IAM authorization prevents the other account or service from creating another accessor share and mount target. Then, delete the binding that connects the origin file share to the accessor shares. This action severs the network path, and puts the accessor share and the mount target that is attached to the accessor share in a failed state.

A failed accessor share and its associated mount targets can't become stable again and can't be reused. The accessor account can and must delete these resources.
{: note}


## Removing authorization
{: #file-storage-xaccount-deauth}

[Removing an authorization in the console](https://cloud.ibm.com/docs/iam?topic=iam-serviceauth&interface=ui&format=markdown#remove-auth){: ui}[Removing an authorization by using the CLI](https://cloud.ibm.com/docs/iam?topic=iam-serviceauth&interface=cli&format=markdown#remove-auth-cli){: cli}[Removing an authorization by using the API](https://cloud.ibm.com/docs/iam?topic=iam-serviceauth&interface=api&format=markdown#remove-auth-api){: api}[Removing an authorization by using Terraform](https://cloud.ibm.com/docs/iam?topic=iam-serviceauth&interface=terraform&format=markdown#remove-auth-tf){: terraform}

## Deleting the bindings
{: #file-storage-delete-bindings}

1. Select a file share from the [list of file shares](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-view&format=markdown#file-storage-view-shares-targets-ui).
1. On the File share details page, scroll to the Accessor share bindings section to locate the binding that you want to delete.
1. At the end of the row of the binding, click the **Actions** icon ![Actions icon](../icons/action-menu-icon.svg "Actions") and select **Delete**.
{: ui}

You can delete a share binding by using the `is share-binding-delete` command. See the following example.
{: cli}

```sh
ibmcloud is share-accessor-binding-delete SHARE ACCESSOR_BINDING
```
{: pre}
{: cli}

You can programmatically delete a share binding by calling the `/shares` method in the [VPC API](https://cloud.ibm.com/docs/apis/vpc/latest){: external} as shown in the following sample request.
{: api}

```sh
curl -X DELETE "$vpc_api_endpoint/v1/shares/v1/shares/$share_id/bindings/$binding_id?version=2024-06-21&generation=2"
```
{: pre}
{: api}

If you want to remove a binding by using Terraform, you need to use the `ibm_is_share_delete_accessor_binding` resource.

```terraform
resource "ibm_is_share_delete_accessor_binding" "example" {
    share = ibm_is_share.example.id
    accessor_binding = data.ibm_is_share_accessor_bindings.example.accessor_bindings.0.id
}
```
{: pre}
{: terraform}

For more information about the arguments and attributes, see [ibm_is_share_delete_accessor_binding](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/is_share_delete_accessor_binding){: external}.
{: terraform}