Set up a working workspace

Use this when

Use this guide when you need to connect, configure, or inspect the workspace before relying on a live workflow.

Setup Center shows whether the workspace is ready for the work you want to do. Start with one workflow, such as replying to customers, and verify its requirements before adding more integrations.

1. Confirm your workspace

Sign in and check that you are in the intended business. If you cannot access it, ask the workspace administrator to check your active membership. For a new installation, follow Self-hosting first.

2. Open Setup Center

Open /admin/setup in the workspace. Review the status and action attached to each check.

Status	What to do
Ready	Read what was verified and when
Needs action	Complete the named setup step
Degraded	Inspect the failure and recovery guidance
Optional or disabled	Decide whether your workflow needs this capability

3. Connect what you need

Use Integrations for the relevant provider. AI work needs an available model configuration; real email needs a verified send path. You can explore the fictional demo without either.

4. Prove it with a small, controlled test

Use test data you control throughout. Review a proposed action, confirm its target, and inspect the actual outcome; for email specifically, use a recipient you own and check both the send and delivery results the provider reports back. A successful demo action is a good sign, but the demo never contacts a real provider, so treat it as a rehearsal, not proof that live delivery works.

If a check stays degraded

Record the check name, its visible error, and the time of the last successful verification. Give those details to your administrator. Keep credentials out of screenshots and support messages. Today's system exceptions can point to the same underlying problem.

Interpret source and processing health

Read the latest execution evidence and the pending work counts together. A successful Gmail incremental sync with zero changed threads is quiet, not broken. A Drive source with no selected folders is not configured. A configured source without a run is never run; listed items that have not been stored or remain deferred indicate incomplete processing.

Today links source and job status to the operational receipts. Live failed work and outbound messages still awaiting resolution can require attention even when the most recent sync succeeded. Pending counts describe work to inspect; they are not a count of successfully delivered results.

What to know

Availability depends on enabled modules, workspace permissions, provider connections, and the current installation. Check the recorded status before relying on a live result.

Next: Review Today to see how this work fits into the daily operating flow.