> For the complete documentation index, see [llms.txt](https://developer.collibra.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.collibra.com/api/graphql/data-access/input-types/what-data-object-remove-input.md).

# WhatDataObjectRemoveInput

Input object to identify a WHAT data object to remove from an access control. When both permissions and globalPermissions are omitted, the entire WHAT link is removed. When specific permissions are provided, only those permissions are subtracted.

```graphql
input WhatDataObjectRemoveInput {
  dataObject: ID!
  globalPermissions: [String!]
  permissions: [String!]
}
```

### Fields

#### dataObject ● [`ID!`](/api/graphql/data-access/scalars/id.md) non-null scalar <a href="#data-object" id="data-object"></a>

The ID of the data object to remove or remove permissions from.

#### globalPermissions ● [`[String!]`](/api/graphql/data-access/scalars/string.md) list scalar <a href="#global-permissions" id="global-permissions"></a>

Specific global permissions to remove. When omitted (together with permissions), removes the entire WHAT link.

#### permissions ● [`[String!]`](/api/graphql/data-access/scalars/string.md) list scalar <a href="#permissions" id="permissions"></a>

Specific permissions to remove. When omitted (together with globalPermissions), removes the entire WHAT link.

### Member Of

[`AccessControlInput`](/api/graphql/data-access/input-types/access-control-input.md) input


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.collibra.com/api/graphql/data-access/input-types/what-data-object-remove-input.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.