> For the complete documentation index, see [llms.txt](https://docs.whiteswan.io/partner-knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.whiteswan.io/partner-knowledge-base/platform-overview/managing-downline-agencies/downline-settings.md). # Downline Settings You can access downline settings through the settings page, which will let you control how your downline agencies interact with the White Swan platform. The downline settings has the following standard capabilities: * **Blocking white-label branding capabilities.** This blocks the ability for your downline agencies to set up their own [white-label branding](/partner-knowledge-base/branding-and-white-labeling/branding-and-design.md). If you block this, they will have the same branding as you have. * **Controlling logo branding in the platform.** Including the ability to cobrand the platform with your own logo (either always or before your downlines set up their own logo) or enforce that the platform should always be branded with your logo only. * **Blocking white-label domain capabilities.** This blocks the ability for your downline agencies to set up their own [white-label domain](/partner-knowledge-base/branding-and-white-labeling/infrastructure-and-communications/custom-domain.md). If you block this, they will have the same domain as you have. * **Blocking white-label email capabilities.** This blocks the ability for your downline agencies to set up their own [white-label emails](/partner-knowledge-base/branding-and-white-labeling/infrastructure-and-communications/email.md). If you block this, they will have the same email setup as you have. * **Blocking white-label phone system capabilities.** This blocks the ability for your downline agencies to set up their own [white-label phone integration](/partner-knowledge-base/branding-and-white-labeling/infrastructure-and-communications/phone-and-texting.md). If you block this, they will have the same phone setup as you have. * **Blocking their ability to view commissions.** This blocks the ability for your downline agencies to access the [commissions dashboard](/partner-knowledge-base/platform-overview/commissions-and-referral-earnings/tracking-commissions.md). * **Blocking their ability to select available policy types/carriers/products.** This blocks the ability for your downline agencies to select what policy types, carriers, and products are available for quoting. Instead, they will only be able to access the selection you pick. * **Blocking their ability to have their own downlines.** This blocks the ability for your downline agencies to invite and manage their own downlines. The capabilities below are gated capabilities that can't be activated by you but must be activated by a White Swan team member. Please get in touch with us if you're interested in any of these capabilities: * **Receiving and distributing commissions for downline agencies.** This option allows you to receive all commissions payable to your downline agencies. It also comes with the responsibility to distribute these commissions to downlines appropriately. Our [commission tracking capabilities](/partner-knowledge-base/platform-overview/commissions-and-referral-earnings/tracking-commissions.md) can help with this. * **Automatically matching agents with your company when signing up outside your** [**official downline onboarding channels**](/partner-knowledge-base/platform-overview/managing-downline-agencies/inviting-new-downlines.md)**.** This option requires you to build and provide White Swan with access to an API that allow us to query a national producer number or an email to see if a particular agent is associated with your company. This API needs to be approved by White Swan before it can be implemented and should follow the structure below. **Agent association match API shape:** 1. You'll provide the URL endpoint for the API, which can be anything, but should be provided without URL parameters (eg. rather than ) 2. The API endpoint should accept two query parameters: ***email*** and ***npn***. It should not require both of these, but should accept either. These parameters will be passed as URL parameters, and not as a JSON body (eg. ; 3. The API endpoint should use authorization in the form of a header field with the key ***x-api-key***. You'll provide a key in setup which will be encrypted and stored securely by White Swan. 4. The API endpoint should return a JSON body with the key ***associated\_agent*** which should be a boolean indicating whether the individual is associated with your company or not. Both email and national producer number should be matched strictly, and you should not for example flag a user as associated with your company based on a matching email domain. It is however accepted and encouraged to match email on a lowercase basis. Example return body: {% code overflow="wrap" %} ```json { "associated_agent":false } ``` {% endcode %} --- # 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.whiteswan.io/partner-knowledge-base/platform-overview/managing-downline-agencies/downline-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.