> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/ras-cpf-integration-guide/custom-provider-framework/admin-configuration-workflow.md). # Admin Configuration Workflow The Custom Provider onboarding flow follows a wizard-like experience in RAS.
StepAdmin actionDetails
  1. General
Provide provider identity and broker-related settings.Name, description, credentials for communication with the Connection Broker, Guest Agent deployment credentials, and preferred Connection Broker.
  1. Connection

Point RAS to the connector implementation.Command, command arguments, and working directory.
  1. Customization
Pass provider-specific configuration to the script.Key/value pairs are forwarded as custom settings and are not interpreted by RAS.
  1. Review
Confirm and create the provider.RAS stores the configuration and uses it during provider initialization and connection.
### Editing an existing provider Once created, the provider can be edited through the standard properties experience. Custom Provider adds dedicated Connection and Customization tabs for command-path settings and custom variables. ### Security and settings caveat Secure custom settings are masked in the administrator UI for display purposes only. RAS still passes all key/value pairs to the script as plain text. Customers should design the connector host, credential handling, and logging practices accordingly. --- # 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://docs.parallels.com/landing/ras-cpf-integration-guide/custom-provider-framework/admin-configuration-workflow.md?ask=&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.