Skip to content

Settings ​

When Asha sets up the Acme Support workspace, there are a few things she almost always does in the first hour: fill in the company profile, decide how long conversation data is kept, choose how the team signs in, and point chat.acme.com at the workspace. All of that lives on Admin → Settings.

Who this is for: workspace admins. Viewing Settings needs the View settings permission. Saving the Business tab needs Manage settings; changing the Authentication tab and using the Custom Domain tab are for admins only. API keys, the MCP server and scheduled jobs are on the separate Developer page.

Three tabs ​

Go to Admin → Settings (/settings). The page has three tabs, each linkable with ?tab= — for example /settings?tab=custom_domain.

TabWhat it configuresWho sees it
BusinessBusiness profile, Cross-Channel Customer Identity, Data Retention PolicyView settings (saving needs Manage settings)
AuthenticationHow your team signs in, including Single Sign-On (OpenID Connect)View settings (only admins can change it)
Custom DomainReach the workspace on your own domainAdmins only

Settings does not hold channels, users, roles, compliance, developer keys or billing — each has its own page (/credentials, /users, /roles, /compliance, /developer, /accounts/*). An old link to /settings?tab=api_keys takes you to the Developer page.

Settings → Business: the business profile

Business tab ​

The Business tab stacks three cards.

Business profile ​

Your company name, address and contact details. It is informational — it does not print on invoices.

  • Business Name — the workspace's display name.
  • Business address & contact (all optional): Address line 1, Address line 2, City, State, Postal code, Country, Contact email, Contact phone, Website, Industry.

Copy from billing details fills Address line 1, State and Contact email from your billing details on Accounts → Billing (or tells you to add billing details first if there are none). Click Save Changes to save the profile.

Business profile ≠ billing details

The legal name, GSTIN and address printed on GST invoices live on Accounts → Billing. The Business profile here is separate.

Cross-Channel Customer Identity ​

This card controls how the AI groups one customer's history across email, SMS, WhatsApp, phone and web chat.

Cross-Channel Customer Identity and Data Retention Policy

Your own business customer ID (external_id) always groups first. You can set it when you identify a visitor in the chat widget, through the customer-link API, or from a customer-lookup tool in your MCP server. This setting decides what happens when no external_id is known:

OptionBehaviour
Business external ID only (default, safest)Channels are grouped only when your external_id is known. You own identity; Perfox never guesses.
Let Perfox unify by these fieldsAlso group contacts by a combination of fields when no external_id is present.

With Let Perfox unify by these fields, tick the fields that must all match before two contacts are treated as one customer — mobile, email, name — or type a custom attribute key (for example membership_id) and click Add. Requiring mobile and name, for instance, keeps family members who share a phone number apart. At least one field is required. Click Save Identity Settings.

Data Retention Policy ​

Controls how long data is kept before the daily cleanup permanently deletes it.

  • Enabled — the master switch. Turning it off pauses cleanup.
  • Three day counts, each 365 days by default:
FieldWhat it deletes
Conversation events (days)Conversation history — messages and tool calls
Voice/phone recordings (days)Call recordings
Media attachments (days)Uploaded media

The maximum is 365 days ("Max 365 days."). A value over the limit shows an error and disables Save Retention Policy. You can shorten retention freely — useful for DPDP / GDPR data-minimisation — but not extend it past 365 days. A "Saved" confirmation appears on success.

Keep the three windows equal (or conversation events longest), so a conversation is never left pointing at a recording that has already been removed.

Authentication tab ​

The Authentication tab controls how your team signs in to the Studio.

Sign-in is passwordless. Team members sign in with a one-time link emailed to them, or with your company's Single Sign-On once you set it up below. Password sign-in is not available on any workspace — even if an account has a password, it can't be used to sign in. (The tab still shows an Email & Password card with an "Enable email / password sign-in" switch; it doesn't turn password sign-in back on.)

Only workspace admins can change this tab. Anyone else with View settings sees it read-only, with the note "Only workspace admins can change how people sign in. You can view these settings; ask an admin to change them."

Single sign-on is powerful

Admins see this reminder on the tab: "Whoever controls single sign-on can sign in as anyone in this workspace. Every admin gets an email when these settings change." Every admin is emailed whenever a sign-in setting actually changes, so an unexpected change doesn't go unnoticed.

Changes apply to the whole workspace as soon as you click Save Authentication Settings.

Single Sign-On (OpenID Connect) ​

Connect any standard OpenID Connect identity provider — Okta, Auth0, Keycloak, Microsoft Entra ID and similar. A toggle in the card header turns SSO on (off by default); while it is off the fields are greyed out.

FieldNotes
Provider Display NameThe label on your SSO sign-in button
ScopesDefault openid email profile
Discovery URLYour provider's .well-known/openid-configuration address
Client IDFrom your identity provider
Client SecretWrite-only and stored encrypted. After saving, the field shows ••••••••; type a new value to replace it, or leave it to keep the stored secret
PKCE (Proof Key for Code Exchange)On by default and recommended

Test Connection fetches the Discovery URL and checks that it lists an authorization and a token endpoint, then shows the issuer (or the error).

Redirect URI (add this in your IdP) shows the exact callback address for your workspace — copy it into your identity provider's allowed redirect URIs. It always points at your workspace's API address, even when you open the Studio on a custom domain.

Set up SSO before November 2026?

The redirect address changed in a sign-in update in November 2026. If your identity provider still has the older address registered, SSO sign-in fails until you replace it with the address shown on this tab now.

How each person starts using SSO ​

SSO never creates accounts and never joins an SSO login to an account just because the email matches. So each person connects SSO to their own account once:

  1. You invite them on Users. They sign in the first time with the emailed link.
  2. They open the account menu (their avatar, top right) and click Connect single sign-on, followed by your provider's name.
  3. They sign in at your identity provider. It must return the same email address as their Perfox account.

From then on, the SSO button on the sign-in page signs them in. The Connect single sign-on item appears only while SSO is turned on and that person hasn't connected yet. If the connection is refused, the account menu opens once to show why. Someone who tries the SSO button before connecting is sent back to the sign-in page with an error.

Custom Domain tab ​

Admins can reach the workspace on their own domain — for example chat.acme.com — in addition to the default address, which keeps working.

Settings → Custom Domain: add a domain

  1. Type the domain under Domain and click Add domain. It is added in Pending DNS.

  2. Create the two DNS records shown in the table — a CNAME pointing at the target Perfox gives you, and a TXT record with your ownership token. Each value has a copy button; TTL is "Auto / 3600".

  3. Click Verify. Perfox checks ownership (the TXT record) and routing (the CNAME). If something is wrong, the reason is shown under the domain.

    Verify within 72 hours. Until it is verified, the domain isn't reserved for you: if another workspace adds the same domain once your claim is more than 72 hours old, your claim is released. A verified or active domain is never released, and a domain that already serves another workspace can't be added.

  4. Once verified, a TLS certificate is issued automatically (this can take a few minutes). When the domain is Active, the panel shows "Live — your workspace is reachable at https://…".

Use Remove to drop a domain.

BadgeMeaning
Pending DNSRecords not created yet, or not yet visible
Verified — issuing certificateOwnership and routing confirmed; certificate on its way
ActiveLive over HTTPS
Action neededVerification failed — check the reason shown

One custom domain serves everything: the Studio, the chat widget, your API and webhooks. See Custom Domains for a worked example.

Reference ​

How the daily cleanup works ​

Cleanup runs once a day. It deletes conversation events, recordings and media older than your retention windows. When a recording or attachment has expired but its conversation entry is still kept, the Studio shows it as "expired" rather than a broken link. This pairs with the data-subject rights on Compliance.

Every option ​

TabControlValues / default
BusinessBusiness Name + 10 address & contact fieldstext, all optional except the name
BusinessCopy from billing detailsfills Address line 1, State, Contact email
BusinessCross-Channel Customer IdentityBusiness external ID only (default) / Let Perfox unify by mobile, email, name or custom keys
BusinessRetention Enabledon
BusinessConversation events / recordings / media (days)1–365, default 365
AuthenticationSign-inEmailed sign-in link, or SSO; password sign-in is not available. Admins only can change
AuthenticationSSOoff; Provider Display Name, Scopes (openid email profile), Discovery URL, Client ID, Client Secret, PKCE (on)
Account menuConnect single sign-oneach person, once, while SSO is on
Custom DomainAdd domain / Verify / Removeadmins only; verify within 72 hours

See also ​