Elsa Workflows / Get started
Connect a server
The connection is saved on the installation's main site, under Elsa → Connection, which only administrators see. It becomes the shared pool: every site that uses it gets its own Elsa tenant (see Shared pool and dedicated servers).
| Field | What to enter |
|---|---|
| Name | A label for the server, such as Elsa pool. |
| Elsa server URL | The HTTPS address of the server. /elsa/api is added when the path does not already end in it. |
| Studio URL | Where Elsa Studio is served, when that is not the server address. |
| Authentication | API key (Authorization: ApiKey …), Bearer token, or OAuth client credentials. OAuth posts to the token URL, {origin}/connect/token by default. |
| Default for all subsites | Whether subsites may use this server as the shared pool. |
- Test checks the server and credentials without saving them. Save checks them again and saves only when Elsa answers.
- Credentials are write-only. The page shows Stored or Not stored, and a later save that leaves a credential empty keeps the stored one.
- Disconnect asks you to confirm, then deletes the server and its credentials.
- Addresses must use HTTPS on port 443. Loopback, private, link-local, and cloud metadata addresses are refused (see Security and privacy).
Tip
API-key authentication is the one that signs staff in to Elsa Studio automatically (see Elsa Studio). With a bearer token or OAuth client, Studio opens at its own address with Elsa's own sign-in.