> For the complete documentation index, see [llms.txt](https://help.besmart.software/t4i/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/t4i/commands-overview/commands-outside-the-inventor-ribbon/ucs-visibility.md).

# UCS Visibility

## Command Description

<figure><img src="https://4060565498-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL8qMZuBhZUXGRVospdct%2Fuploads%2FGB3gu9cghEt7pl40PZxa%2Fimage.png?alt=media&amp;token=b91f9f8d-cb26-4834-ad42-819696f9ac43" 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

`Be.Smart T41 -> Be.Smart T4I -> Edit settings -> Other tools -> UCS Visibility`

<figure><img src="https://4060565498-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL8qMZuBhZUXGRVospdct%2Fuploads%2FnCJwTG8bYUj99qYLXLI6%2Fimage.png?alt=media&amp;token=e87222d5-763a-46ca-88b4-e127dd61e4f0" alt=""><figcaption></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="https://4060565498-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL8qMZuBhZUXGRVospdct%2Fuploads%2FS4aAC6stH5uVUwtE4MpV%2FUCS.gif?alt=media&amp;token=4a9457a1-f7cc-45e2-a85c-7acf6f92aafb" 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 by asking a question.

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

```
GET https://help.besmart.software/t4i/commands-overview/commands-outside-the-inventor-ribbon/ucs-visibility.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.
