# Other features of the environments

Configuration

The **Environment Configuration** section displays applications associated with clients within that environment. In this section, you can:

* **Remove applications.**
* **View application details.**

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

***

### Sessions

The **Sessions** tab, just like in the Instances section, allows you to view users connected to all your instances in a centralized manner. This enables mass disconnection of sessions and streamlines management, providing a faster and more efficient overview.

<figure><img src="/files/01Fa6i6VlupKB7GOROnm" alt=""><figcaption></figcaption></figure>

***

## **Maintenance and History**

The "**Maintenance"** features are useful for notifying users about unavailability before they attempt to access the application environment.

* **Show alert:**&#x20;

This feature allows you to configure messages informing users about unavailability at specific times.

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

* **Scheduled Maintenance:**

This feature blocks user access at a defined date and time, allowing for scheduled maintenance. It can also terminate active sessions and prevent new logins from clients linked to the environment.

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

* **Manual Maintenance:**

  \
  With this feature, you can immediately block access to the environment for maintenance. Active sessions will not be terminated, but new logins will be prevented.

  \
  By enabling this option, you will see the option to:

  * **End sessions**
  * **End instances**

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

* **Daily blocking of instance:**&#x20;

Allows automatic daily instance locking configuration.

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

{% hint style="info" %}
Whenever activating or deactivating maintenance or displaying a notification, you must provide a reason for the action. This reason will be automatically recorded in the Maintenance History, ensuring transparency and traceability of changes made.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.skyone.cloud/english/cloud-computer/skyone-autosky/skyone-autosky-platform/environments/other-features-of-the-environments.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.