Workspace And Team Settings
Workspace settings are durable. They shape public pages, checkout, booking availability, notifications, integrations, and operator access.
General
Configure:
Business name
Use the public name customers should see in navigation, receipts, booking confirmations, and search previews.
Address and service area
Confirm whether the business serves customers at one location, across a radius, online, or at customer locations.
Timezone
Set this before configuring services, availability, reminders, and reporting windows.
Currency
Match the payment account, products, services, invoices, refunds, and customer expectations before launch.
Phone and email
Use contacts that are monitored by the team responsible for customer questions and replies.
Business hours
Keep public hours, booking windows, support expectations, and local metadata aligned.
Site status
Choose draft, protected, or live intentionally so public traffic matches the workspace's readiness.
General settings affect local business metadata, booking availability, receipts, notifications, and public page context.
Treat this section as the workspace identity baseline. Before changing it, confirm whether the update is cosmetic, operational, or legal: a name or phone update is usually simple, while timezone, currency, address, and service-area changes can alter booking availability, taxes, email copy, and customer expectations.
Team
Use Team to control who can manage the workspace.
Review:
- Owners.
- Managers.
- Staff.
- Former users.
- Role-specific access.
Remove users promptly when they leave the business or no longer need console access.
Review access whenever responsibilities change, not only during onboarding. Owners should keep billing, payments, domain, and legal controls limited to trusted operators; staff accounts should match the work they perform each day so routine operations do not require shared logins or temporary permission workarounds.
Domain And Email
Use Domain and Email to configure public routing and branded sending.
Typical tasks:
- Add or verify a custom domain.
- Review DNS provider guidance.
- Export DNS records.
- Configure mailboxes or sender identity.
- Confirm email records are not proxied incorrectly.
If public links or email delivery are unreliable, start here.
Checkout And Tax
Use Checkout and Tax for payment behavior:
- Stripe connection posture.
- Checkout availability.
- Tax settings.
- Invoice behavior.
- Deposit or balance collection defaults.
- Product shipping implications.
Payment settings should be reviewed with the workspace’s financial owner before launch.
Privacy And Legal
Use Privacy and Legal for:
- Terms.
- Privacy policy.
- Refund policy.
- Shipping policy.
- Cookie consent.
- Communication disclosures.
- Data retention posture.
Analytics and ads require particular care because public-site tags depend on customer consent posture.
Use this section before enabling tracking, forms, bookings, checkout, subscriptions, or consent documents. If the business changes refund, cancellation, shipping, or data-use commitments, update the policy page and then test the public customer path where that commitment appears.
Features
Feature settings decide which capabilities are available or visible:
- Shop.
- Bookings.
- Forms.
- Intake.
- Stories or knowledge content.
- Marketing.
- Customer portal features.
If an operator sees a disabled navigation item, check Features before debugging the page.
Intake Flow
Use Intake Flow to shape customer data collection before work begins. Intake can affect forms, booking questions, routing, and follow-up workflows.
Good intake is:
- Short enough for customers to finish.
- Specific enough for the team to act.
- Connected to the right console triage surface.
Review intake from both sides: customers should understand why each field is required, and operators should know exactly where each answer appears. Remove questions that nobody uses, split high-friction intake into later follow-up when possible, and verify that sensitive answers are not copied into analytics, ads, or public URLs.
AI Assistance
AI assistance settings control drafting, summarization, recommendations, and other AI-supported behavior. Keep these settings aligned with the business’s service model, customer tone, safety boundaries, and review expectations.
Use a narrow posture for a new workspace: allow drafting, summarization, and operator support first, then expand only after the team can review outputs confidently. Customer-facing or record-changing assistance should have an owner, a visible review surface, and a stop condition for ambiguous or high-risk situations.
Settings Change Protocol
- Identify the public or operational surfaces affected.
- Make one coherent settings change.
- Save.
- Verify in console and on the public site.
- Test downstream workflows if payments, bookings, notifications, or integrations are involved.
For launch-impacting settings, record the before/after state and the verification route. Examples: a domain change should be verified from the final host, a currency change should be verified through checkout, a timezone change should be verified through public booking availability, and a consent change should be verified through analytics or ads behavior.