> For the complete documentation index, see [llms.txt](https://help.besmart.software/older-26.0.0/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.besmart.software/older-26.0.0/commands-overview/commands-outside-the-inventor-ribbon/ucs-visibility.md).

# UCS Visibility

## Command Description

<figure><img src="/files/nL9fLXp9uhBXqDkZhruE" alt=""><figcaption></figcaption></figure>

The UCS Visibility command is accessible in the right-mouse click menu on a user coordinate system (UCS). A user can set the visibility of the UCS while respecting the visibility settings of individual UCS features (origin, axes, planes).

It means, for example, that when setting the UCS visibility to ON, only the UCS features allowed in settings will be turned visible.

## Command Location

* Assembly and part environments

## Command Settings

`Holixa T41 -> Holixa T4I -> Edit settings -> Other tools -> UCS Visibility`

<figure><img src="/files/wpMWza3wC2rrhH9yscmz" alt=""><figcaption><p>UCS Visibility settings</p></figcaption></figure>

Check the UCS features you want to be visible when turning the UCS visibility to ON.

## Workflow Overview

1. In settings, select the UCS features that should be visible when turning the UCS visibility to ON.
2. Create the UCS.
3. Use the command.

## Exampe of Using the UCS Visibility Command

<figure><img src="/files/AmRRHiRP2tLnoDl1LgAe" alt=""><figcaption><p>Example of using the UCS Visibility command</p></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.besmart.software/older-26.0.0/commands-overview/commands-outside-the-inventor-ribbon/ucs-visibility.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.