> For the complete documentation index, see [llms.txt](https://docs.adapptio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adapptio.com/getting-started/editor/components-panel/view-settings.md).
# View Settings
Any of the implemented Views has its independent settings from each other. Giving it a proper name and description does not affect the visible or logical output and serves just for internal use; for example, it's handy for team-developed applications.
{% tabs %}
{% tab title="Options Settings" %}
{% endtab %}
{% tab title="Title and Description" %}
{% endtab %}
{% tab title="Code Editor Desription" %}
{% endtab %}
{% endtabs %}
The required authenticated user verifies if the current user ID is not a null value, preventing access of the View to non-authorized persons. Binding access rights with specific condition rules expand accessibility options; in our case, an already logged user has to have a specified Name.
{% tabs %}
{% tab title="Require Authenticated User" %}
{% endtab %}
{% tab title="Authorization Condition" %}
{% endtab %}
{% tab title="Code Editor Description" %}
```
IF(currentUser.firstName == "Martin", true, false)
```
{% endtab %}
{% endtabs %}
If any of the input parameters are changed, reinitializing the output of a View is triggered.
Setting up the virtual URL address of the current View is handy with the logical route component, where instead of its ID targeting nomenclature.
Two different Events methods are triggered by initialization or when the input parameters are changed. Both of the methods are not dependent on each other. Events logic can be added directly by selecting the desired one from the Events panel or clicking on the required action.
{% tabs %}
{% tab title="Events Settings" %}
{% endtab %}
{% tab title="Direct Logic Selection" %}
{% endtab %}
{% tab title="Event Console" %}
{% endtab %}
{% endtabs %}
---
# 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://docs.adapptio.com/getting-started/editor/components-panel/view-settings.md?ask=&goal=
```
`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.