Summer Summer setup belongs to a company. Select the correct company before adding integrations, editing knowledge or inviting teammates. If you belong to more than one company, use the company selector in the workspace header.
What you need
Use a work Google account and have a company owner or admin available for setup. For connected tools, involve someone who can manage the provider account and supply the agreed credentials. You can prepare company details and knowledge while Summer finishes the managed operations connection.
1. Sign in and get access
Use your work Google account from Open Summer. New accounts may show Awaiting approval. Save your company name and setup needs on that screen; the Summer team reviews access. Do not include credentials or patient information in the request.
If your company already uses Summer, ask its administrator for a private invitation. Sign in with the exact email the invitation names. Account approval and company membership are separate checks. See Team and access.
2. Choose your first workflow
Open Settings → Company. An owner or admin can save:
- The company name customers and teammates recognize.
- The company timezone, such as
America/Los_Angeles. - A first workflow: customer support, order status and fulfillment, billing support, or another managed workflow.
- A setup note describing the connection or help you need.
Choose a concrete outcome, such as finding the current shipment status for an order. Saving a workflow records your intended setup; Summer must still verify the operational connection before case work is available.
3. Connect the tools that workflow needs
Open Settings → Integrations. Add the relevant provider credentials, connect Slack if needed, or set up the website messenger. Store provider credentials in Summer's secrets manager using the UI or CLI. An MCP client can guide setup and hand secret uploads to the local CLI or UI. You do not need Doppler; connect it only if your team already uses it. Slack is optional.
Choose staging or production before saving API credentials. A Required credentials saved status confirms that values or available vault references are present. Verify the actual provider account and required reads with Summer before relying on the workflow. See Connect your tools.
4. Review your knowledge
Open Knowledge and review the clinic operating profile and starter guides. Replace unknown company facts with approved sources, dates and responsible owners. Start with the policies needed for your first workflow.
The shared knowledge base is available before case-runtime activation. Both agents share that full library, with different role instructions. Build your knowledge base explains both.
5. Invite the people who will review work
Open Settings → Team to prepare private invitations. You can also complete setup as a solo administrator. Operational access and authority to approve customer actions require their own permissions; inviting a teammate does not grant them automatically.
6. Verify a useful outcome
Open Setup to check progress. Once your company’s operational connection is ready, review one authorized case with Summer. Compare original evidence, the proposed plan and the verified outcome. Keep automatic investigations under the rollout controls agreed for your company.
An admin can record a guidance review against the current document ID and revision, and a first-outcome review against the original resolved case. A later guidance revision needs a fresh review. These setup records document what a human checked; they do not approve case actions.
If Operations connection pending appears, finish the settings, credentials and knowledge you control, then contact Summer through Settings → Help. See Troubleshooting for the difference between pending setup and a failed access check.
Know when setup is ready
| Part | Who finishes it | What to confirm |
|---|---|---|
| Company and team | Your owner or admin | Correct company, timezone, workflow and intended teammates. |
| Provider credentials | Your admin and provider administrator | Required fields saved for the intended company, provider account and environment. |
| Knowledge | Your policy owner or admin | Relevant guides have approved facts, sources, dates and responsible owners. |
| Operational connection | Summer with your authorized operator | Required reads work against a known record; case and review permissions are verified. |
| First outcome | Your reviewer with Summer | The original evidence supports the plan and the verified customer outcome. |
For a website-only launch, follow the Messenger installation checks and assistant setup instead of waiting for unrelated operational tools. Keep clinical questions routed to your care team.