Settings

An organization has three settings of its own, a display name, a URL slug, and the OpenAI API key its chat runs on, and all three are owner-only. Everything else about how the embedded agent behaves is configured on the other pages in this section.

The name

The name identifies the organization to your colleagues, up to 100 characters. It appears in the dashboard, in the organization switcher, and in the subject line and body of invitation emails.

The name is display text only, as nothing about the embedded chat depends on it and tenant users never see it.

The URL slug

The slug is the first segment of every dashboard URL for this organization, as in /<slug>/agents, and it is only ever a URL.

A slug is 1 to 63 characters of lowercase letters, digits, and hyphens. It has to be unique across all organizations, so a slug you want may already be taken, and it cannot be one of the words the application uses for its own top-level paths, such as docs, api, settings, and organizations.

NOTE: changing the slug breaks every existing dashboard URL for the whole organization at once, as bookmarks, links in your runbooks and tickets, and any tab a colleague has open all stop resolving.

Saving moves you to the new URL, and nobody else is moved.

Nothing outside the dashboard depends on the slug. The organization's real identity is a permanent internal ID, which is what public agent IDs, API keys, and chat auth tokens are built from, so a slug change never affects embedded chat, tokens already minted, or applications in production.

The OpenAI API key

Every chat run for this organization streams on this key, and the deployment holds none of its own, so the embedded agent cannot answer anything until one is set. The organization home page carries a banner while it is missing, and each message the widget sends is refused with the error Org OpenAI key is not configured, which the tenant user sees in place of a reply.

Let's set one. Create a secret key in the OpenAI dashboard, paste it into the field, and press Save key. A key is accepted only in the shape OpenAI issues, which starts with sk- and contains no spaces, so a pasted environment line or project ID is rejected before it reaches storage.

The key is stored encrypted, the same way sandbox credentials are, and it is never shown again in full, not even to you. The card reports Configured and shows the last four characters as sk-***abcd, which is enough to tell which of your keys is in use, and the field below it becomes a replacement: saving a new key replaces the old one, and Remove key clears it, which stops chat for every embedded widget in this organization at once.

NOTE: usage on this key is billed to your own OpenAI account. Model spend for your tenant users is yours, not the deployment's.

Who can change these

Only owners. Developers and viewers do not see this page in the sidebar and are returned to the organization home when they open its URL, where developers still see the missing-key banner. See Members.

An organization cannot be deleted from the dashboard.

Settings that live elsewhere

• Agents, their instructions, and which one is the default: Agents.
• Sandbox providers and their credentials: Sandboxes.
• API keys for the management API and for signing chat tokens: API keys.
• Who can sign in and what each role may do: Members.

Limits on requests, attachments, and sandboxes belong to the deployment rather than to your organization and cannot be raised from here, and they are listed in Limits.

Your own account

Your display name and avatar are yours rather than the organization's, and you change them on your account page, reached from your name at the bottom of the sidebar. Your sign-in email address cannot be changed from the dashboard.

Your password, your connected sign-in providers, and your active sessions are on the security page alongside it. Revoking a session there is the fastest way to cut off a device you no longer control, and changing your password revokes your other sessions for you.