> ## Documentation Index
> Fetch the complete documentation index at: https://developer.suki.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Implementation

> Implementation questions and best practices for Web SDK integration

<Accordion title="Are There Any Best Practices for Implementing the Suki SDK?">
  Yes, to ensure a successful implementation of the Suki SDK, start by clearly
  defining your project requirements and reviewing the SDK documentation
  thoroughly.

  Set up your development environment with the necessary tools and
  adopt a modular approach, integrating one feature at a time to simplify
  troubleshooting. Adhere to coding standards, implement robust error handling
  and logging, and secure your API keys and data transmissions.
</Accordion>

<Accordion title="Can the Suki SDK Be Customized to Fit Our Organization's Specific Needs?">
  Yes, there are a set of elements within the SDK UI related to its look and
  feel that can be changed such as color, width/height and presence of buttons.
</Accordion>

<Accordion title="Is Provider Substitution Supported?">
  No. The Web SDK does not support switching the active provider in place without starting a new SDK lifecycle.

  Create `SukiAuthManager`, then call `initialize()` (JavaScript) or `init()` (React), for **one** provider session. The Web SDK client is a singleton. Calling `initialize()` or `init()` again with a different `SukiAuthManager` does not replace the active provider.

  Use a separate provider session when the signed-in clinician changes. Do not reuse one provider's `partnerToken` for another provider. For partners that authenticate with a shared organization token and pass `provider_id` on login, refer to [Bearer partner authentication](/api-reference/bearer-partner-authentication).

  If your product needs multi-provider workflows in one page session, contact your Suki partnership team.
</Accordion>