Skip to main content
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.

​
Prerequisites

  • Have master access to Symphony.

​
Step 1 — Access the Admin Panel

1

Locate your name

In the left sidebar, at the bottom of the screen.
2

Click your name

3

Select Admin Panel

​
Step 2 — Create the company

1

Go to Platform → Companies

2

Click New company

3

Fill in the required fields

​
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.
Errors in SSO configuration can prevent users from accessing the environment.

​
Step 3 — Permissions (advanced settings)

After creating the company, you need to switch to the created company’s view:
1

Click your name in the sidebar

2

Select the newly created company (Switch company)

3

Go to Admin Panel → Platform → Permissions

In Admin and User → Chat: keep disabled only these options:
  • Direct tool servers
  • Force temporary chat
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.
In Admin → Admin Panel: limit the visible/active sections to only:
  • Users
  • User groups
  • Models
  • General Settings
  • Interface
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.

​
Step 4 — User group structure

1

Go to Management → User groups

2

Create the necessary groups according to the company's structure

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.

​
Step 5 — Connection configuration (APIs)

1

Go to Connection in the Admin Panel

2

Configure connection URLs according to the providers used by the company

3

Add API keys and required models

4

Validate operation after inserting each key

Connection examples:
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.

​
Step 6 — Base model configuration

1

Go to Models in the Admin Panel

2

Configure each model

  • Add a clear description (refer to the LLM Models Comparison).
  • Configure the necessary parameters, if applicable.
  • Share the model with the corresponding groups.

​
Step 7 — Document configuration (Embedding)

1

Go to the Documents page in the Admin Panel

2

Define the embedding model (document vectorization)

Impact of this configuration:
  • Directly affects internal search quality.
  • Influences the performance of document-based agents.
If you update or change the embedding model, you will need to reimport all documents.

​
Step 8 — Web search configuration

1

Go to Web search in the Admin Panel

2

Define the model/engine responsible for searching

E.g.: Google PSE, with API key and engine ID.
Expected use — web search is used for external queries, information updates, and enriching responses with recent data.

​
Step 9 — Code execution configuration

1

Go to Code execution in the Admin Panel

2

Define the engine responsible for code execution

E.g.: pyodide.

​
Step 10 — Audio configuration

1

Go to the Audio page in the Admin Panel

2

Define the STT (speech-to-text) and TTS (text-to-speech) models/engines

According to the company’s needs.

​
Step 11 — Image configuration

1

Go to the Image page in the Admin Panel

2

Define the image generation engine and available visual features

For users, when applicable.

​
Step 12 — Agent configuration

This is a strategic step and should be carried out together with the client.

​
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?
Consult the complete catalog in the Agents Gallery to support the client assessment and choose agents by area.

​
Agent configuration

1

Clone existing agents from FC's Symphony

See Clone agent between companies.
2

Adjust each agent

  • Prompt
  • Permissions
  • Contexts
  • Groups with access
  • Tools enabled, if applicable.
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.

​
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