> 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 %}