> For the complete documentation index, see [llms.txt](https://documentation.dnanexus.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.dnanexus.com/developer/api/data-object-lifecycle/visibility.md). # Visibility Each object has a flag which indicates whether it is a hidden object or not. A UI consuming the API may choose to then display or hide the hidden objects. The primary purpose of this flag is to mark objects that are considered hidden internal data objects that help implement a larger data type. Because hidden objects are meant to represent internal objects, a UI consuming the API may choose to prompt the user to choose whether linked hidden objects are always cloned or removed from the project when the object containing the links is cloned or removed. Because the visibility of the object is tied to its type or its role in satisfying another object's type, this flag can only be set on an object while it is still open. By default, all newly created objects are not hidden. ## API method: `/class-xxxx/setVisibility` ### Specification Sets the visibility of the object. ### Inputs * `hidden` **boolean** (required) Whether to hide the object or not. ### Outputs * `id` **string** ID of the manipulated object. ### Errors * `ResourceNotFound` * The specified object in the URL does not exist. * `InvalidInput` * The input is not a hash. * `hidden` is not present or is not a boolean. * `PermissionDenied` * UPLOAD access is required for the project in which the object was created. * `InvalidState` * The object is not in the "open" state. --- # 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://documentation.dnanexus.com/developer/api/data-object-lifecycle/visibility.md?ask=&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.