> For the complete documentation index, see [llms.txt](https://docs.skyone.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.skyone.cloud/english/skyone-autosky/skyone-autosky/skyone-autosky-platform/clients/add-client.md). # Add Client The **Add Client** feature allows you to register new companies, departments, or business units in Autosky and define the necessary settings to access the applications and resources available in the environment. During registration, administrative information, access rules, interface options, virtualization, and authentication settings can be configured, ensuring that each client is created according to the organization's needs. After creation, the client becomes part of the selected environment's structure and is available for the management of users, applications, sessions, access restrictions, and other platform features. *** #### Client List Overview The client list centralizes the management of clients registered in the environment, allowing you to consult operational information and quickly access main administrative features. Available information includes client identification, associated environment, number of active sessions, status, and last access date. In addition to data querying, the page provides actions for client administration, including the management of users, applications, sessions, access restrictions, maintenance, and logs. The creation of new clients is also performed through this area using the **General Actions** option.
*** ### Add Client Registering a new client ensures that all required information is properly recorded to enable access and configuration management. #### Step-by-step to add a client: 1. Click **General Actions**.
#### **Basic Information** Fill in the mandatory and optional fields: * **Client Name:** Name that will identify the client within the platform. * **Client External Code (optional):** Identifier used internally by Autosky for client recognition and possible integrations. * **Administrator Email (optional):** Email of the user responsible for the initial management of the client. * **Environment:** Defines in which environment the client will be created.
#### Access Settings The options below allow you to customize the client's behavior. Configure the **flags** according to your needs: * **Always copy the administrator on email communications:** Automatically includes the registered administrator in communications sent by the platform. * **Block multiple sessions for the same user:** Prevents the same user from having more than one active session simultaneously. * **Use iOS devices:** Enables support for access from Apple devices compatible with the platform. * **Remote profile:** Defines the use of specific settings for remote access profiles. #### Interface Allows you to define the interface used by the client. * **Use the same interface as the client's account:** Automatically inherits the interface configured for the main account. * **Configure interface:** Allows you to select a specific interface for the client when inheritance is not enabled. #### Virtualizer Controls the mechanism used for application publishing. * **Use the same virtualizer as the environment:** Automatically uses the default configuration defined for the environment. * **Virtualizer:** Allows you to manually select a specific virtualizer for the client. * **Primary Port:** Defines the main port used for communication with the selected virtualizer. #### DUO Authentication Autosky allows the use of multi-factor authentication through DUO Security. When enabling this feature, the following fields must be filled out: * **Client ID:** Integration identifier provided by DUO. * **Client Secret:** Secret key used to authenticate the integration. * **Host:** DUO service address responsible for validating access. * **Allow login in case of unavailability:** When enabled, allows users to log in even if the DUO service is temporarily unavailable. #### Notes The Notes field can be used to record additional information about the client, facilitating future administrative queries.
*** #### Completing the Registration After completing the information: 1. Review the provided data. 2. Click **Add**. 3. The client will be created and displayed in the client list. #### Next Steps After adding a client, you can manage their information and perform different actions using the **Action Button**. In the following pages of this documentation, we will detail how to use the available features: * [Edit and Clone](/english/skyone-autosky/skyone-autosky/skyone-autosky-platform/clients/edit-and-clone.md) * [Users](/english/skyone-autosky/skyone-autosky/skyone-autosky-platform/clients/users.md) * [Applications](/english/skyone-autosky/skyone-autosky/skyone-autosky-platform/clients/applications.md) * [Sessions](/english/skyone-autosky/skyone-autosky/skyone-autosky-platform/clients/sessions.md) * [Access Restrictions](/english/skyone-autosky/skyone-autosky/skyone-autosky-platform/clients/manage-access-restrictions.md) * [Maintenance and Logs](/english/skyone-autosky/skyone-autosky/skyone-autosky-platform/clients/maintenance.md) --- # 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.skyone.cloud/english/skyone-autosky/skyone-autosky/skyone-autosky-platform/clients/add-client.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.