Summer Summer’s settings belong either to a company, a Messenger installation or your personal account. Choose the right scope before making a change.
Company settings
| Setting | Where | What it changes |
|---|---|---|
| Name, timezone, first workflow and setup note | Settings → Company | The company’s saved setup details. Choosing a workflow does not enable its runtime. |
| Members, invitations and ownership | Settings → Team | Access to this company’s workspace. Operational permissions are checked separately. |
| Issue and reviewer assignment | Settings → Assignment | Who receives newly arriving issues or plans, where operational access is available. |
| Provider credentials, Doppler and Slack | Settings → Integrations | The selected company’s tool configuration. Credentials also have a production/staging scope. |
| Shared procedures and workspace instructions | Knowledge | The company’s current operational knowledge, with revision history. |
| Settings history | Settings → Activity | Recorded company configuration changes visible to authorized admins. |
Changing the company timezone does not change each teammate’s display preference. Configure your own timezone under My account.
Assignment rules
With the required operational access, open Settings → Assignment. Configure New issues and Plan approvals separately:
- Leave unassigned keeps new work available for manual assignment.
- Default teammate sends new work to one eligible teammate.
- Round robin rotates work through the selected eligible team. Use all eligible teammates includes newly eligible teammates as they join.
Existing assignments stay with their current owners. Only current company members with operational access are eligible, and plan reviewers need approval authority. If nobody is eligible, work stays unassigned. Assignment does not approve a plan.
Website assistant behavior
Open Messenger → Chat assistant instructions and choose an installation. You can edit:
- Conversational AGENTS.md: greeting, tone, clarification and human handoff.
- Model spending limit per conversation (cents): the assistant’s conversation budget.
- Enable routine automatic chat replies: whether this installation may use the conversational assistant, subject to the deployment’s runtime switch.
Approved answers, policies, support hours and offer terms live in the shared Knowledge library used by both agents.
Save changes and test a new turn. Instructions cannot weaken clinical prohibitions or approve operational effects. See Assistant and knowledge.
In Customer messenger, edit allowed website origins, guest access, privacy and fallback support URLs, response expectations, public clinician/sign-in/catalog destinations and the optional offer label and URL. Configure getIdentityAssertion in your website code; it is not a field on this settings page. Patient-specific destinations belong in the verified server integration. See Care links for destination setup.
The current customer settings do not expose a widget theme builder, custom CSS editor or model picker. Ask Summer about branding or behavior beyond the available controls before planning an implementation.
Personal preferences and notifications
Open My account → Personal preferences to save your display name, timezone, and email or Slack decision-notice preferences. These settings follow your account rather than changing company permissions.
Automatic operational email and Slack decision delivery are not enabled yet. Preferences are saved for when delivery is available; continue checking the dashboard for decisions. Messenger offline email notifications are also unavailable, so website customers return to the widget for replies.
Use My account → Browser sessions for session management and Team and access for company membership changes.