> ## Documentation Index
> Fetch the complete documentation index at: https://symphony-docs.fcamara.com/llms.txt
> Use this file to discover all available pages before exploring further.

# SaaS Manual - New client onboarding

> Complete playbook for provisioning a new company (tenant) in Symphony end to end.

<Warning>
  **Exclusive access to the Master profile.** This is an operational guide for **provisioning a new company (tenant)** in Symphony end to end: creation, permissions, groups, connections, models, documents, features, and agents.
</Warning>

## Prerequisites

* Have **master access** to Symphony.

## Step 1 — Access the Admin Panel

<Steps>
  <Step title="Locate your name">
    In the left sidebar, at the bottom of the screen.
  </Step>

  <Step title="Click your name" />

  <Step title="Select Admin Panel" />
</Steps>

## Step 2 — Create the company

<Steps>
  <Step title="Go to Platform → Companies" />

  <Step title="Click New company" />

  <Step title="Fill in the required fields">
    | # | Field                  | Guidance                                                              |
    | - | ---------------------- | --------------------------------------------------------------------- |
    | 1 | **Company name**       | Use the company's **official** name. Avoid unnecessary abbreviations. |
    | 2 | **Number of licenses** | Set according to the **contract** signed with the client.             |
    | 3 | **Domain**             | Use the pattern `/companyname`.                                       |
  </Step>
</Steps>

### SSO configuration

If the company uses corporate authentication, configure **SSO — Single Sign-On**. Validate:

* Login/logout **URLs**;
* **Certificates** (if required);
* **Parameters** required by the identity provider.

<Warning>
  Errors in SSO configuration can **prevent users from accessing** the environment.
</Warning>

## Step 3 — Permissions (advanced settings)

After creating the company, you need to **switch to the created company's view**:

<Steps>
  <Step title="Click your name in the sidebar" />

  <Step title="Select the newly created company (Switch company)" />

  <Step title="Go to Admin Panel → Platform → Permissions" />
</Steps>

### Recommended default configuration

**In Admin and User → Chat:** keep **disabled only** these options:

* **Direct tool servers**
* **Force temporary chat**

<Note>
  All other Chat options (file upload, delete/edit messages, controls, STT, TTS, voice call, multiple models, code interpreter, web search, image generation, archived chats, attach knowledge/prompt/tools, temporary chat) remain **enabled**.
</Note>

**In Admin → Admin Panel:** limit the **visible/active** sections to only:

* **Users**
* **User groups**
* **Models**
* **General Settings**
* **Interface**

<Tip>
  **When to change permissions?** Only if the company **requests specific access** or if there is a need to **restrict** features. In most cases, the **default configuration** already meets the company's initial operation.
</Tip>

## Step 4 — User group structure

<Steps>
  <Step title="Go to Management → User groups" />

  <Step title="Create the necessary groups according to the company's structure" />
</Steps>

<Warning>
  When creating or editing a group, check the **BU — Business Unit** option. This allows the group to:

  * appear in **user registration**;
  * be **selectable** when creating/editing users;
  * be used for **access segmentation** and permissions.
</Warning>

## Step 5 — Connection configuration (APIs)

<Steps>
  <Step title="Go to Connection in the Admin Panel" />

  <Step title="Configure connection URLs according to the providers used by the company" />

  <Step title="Add API keys and required models" />

  <Step title="Validate operation after inserting each key" />
</Steps>

**Connection examples:**

| # | Provider      | Base URL                                                  |
| - | ------------- | --------------------------------------------------------- |
| 1 | Google Gemini | `https://generativelanguage.googleapis.com/v1beta/openai` |
| 2 | Anthropic     | `https://api.anthropic.com/v1`                            |
| 3 | OpenAI        | `https://api.openai.com/v1`                               |
| 4 | Perplexity    | `https://api.perplexity.ai`                               |
| 5 | Azure OpenAI  | `https://<resource-name>.openai.azure.com/openai/v1`      |

<Warning>
  **Best practices:**

  * Never share API keys in public environments.
  * Validate that the key has the **correct permissions**.
  * **Test** the connection after configuration.
  * Internally record which keys were used and for what purpose.
</Warning>

## Step 6 — Base model configuration

<Steps>
  <Step title="Go to Models in the Admin Panel" />

  <Step title="Configure each model">
    * Add a **clear description** (refer to the [LLM Models Comparison](https://camara1.sharepoint.com/:x:/r/sites/nucleo.ia.dev/Documentos%20Compartilhados/Documentos/Comparativo%20de%20Modelos%20LLMs.xlsx?d=w3592eb1560a24a08a15aa169c603e1ae\&csf=1\&web=1\&e=GrCHe5)).
    * Configure the necessary **parameters**, if applicable.
    * **Share** the model with the corresponding **groups**.
  </Step>
</Steps>

## Step 7 — Document configuration (Embedding)

<Steps>
  <Step title="Go to the Documents page in the Admin Panel" />

  <Step title="Define the embedding model (document vectorization)" />
</Steps>

**Impact of this configuration:**

* Directly affects **internal search quality**.
* Influences the **performance of document-based agents**.

<Warning>
  If you update or change the embedding model, you will need to **reimport all documents**.
</Warning>

## Step 8 — Web search configuration

<Steps>
  <Step title="Go to Web search in the Admin Panel" />

  <Step title="Define the model/engine responsible for searching">
    E.g.: Google PSE, with API key and engine ID.
  </Step>
</Steps>

**Expected use** — web search is used for external queries, information updates, and enriching responses with recent data.

## Step 9 — Code execution configuration

<Steps>
  <Step title="Go to Code execution in the Admin Panel" />

  <Step title="Define the engine responsible for code execution">
    E.g.: `pyodide`.
  </Step>
</Steps>

## Step 10 — Audio configuration

<Steps>
  <Step title="Go to the Audio page in the Admin Panel" />

  <Step title="Define the STT (speech-to-text) and TTS (text-to-speech) models/engines">
    According to the company's needs.
  </Step>
</Steps>

## Step 11 — Image configuration

<Steps>
  <Step title="Go to the Image page in the Admin Panel" />

  <Step title="Define the image generation engine and available visual features">
    For users, when applicable.
  </Step>
</Steps>

## Step 12 — Agent configuration

<Info>
  This is a **strategic** step and should be carried out **together with the client**.
</Info>

### Assessment with the company

Before configuring, understand:

* Which **agents** will be used?
* What is the **objective** of each agent?
* Which **areas** will use the agents?

<Tip>
  Consult the complete catalog in the [Agents Gallery](https://symphony.fcamara.com/agents-gallery) to support the client assessment and choose agents by area.
</Tip>

### Agent configuration

<Steps>
  <Step title="Clone existing agents from FC's Symphony">
    See [Clone agent between companies](/en/admin/perfil-master#clone-agent-between-companies).
  </Step>

  <Step title="Adjust each agent">
    * **Prompt**
    * **Permissions**
    * **Contexts**
    * **Groups with access**
    * **Tools** enabled, if applicable.
  </Step>
</Steps>

<Note>
  **Quick Access Agents (future feature).** When available, it will allow configuring the company's most-used agents as **quick access**. This feature is **not yet implemented**.
</Note>

## Final checklist

Before finalizing the company registration, validate:

* [ ] Company created correctly
* [ ] Domain configured
* [ ] Number of licenses according to contract
* [ ] SSO configured and functional, when applicable
* [ ] Default group created
* [ ] BU groups configured
* [ ] APIs inserted and working
* [ ] Base models configured and shared with default group
* [ ] Embedding model defined
* [ ] Web search configured
* [ ] Code execution configured
* [ ] Image generation configured
* [ ] Agents created and tested
* [ ] Final validation carried out with the client or internal responsible