Run your business.
Build what it needs.

Form builder supports draft definitions, preview and published share links. Review responses and customer matches before accepting them into the existing intake path.

Proposals retain the services, pricing and customer context. Material edits and acceptance use the existing proposal lifecycle and linked pipeline rules.

Open an invoice from a won opportunity with its linked contact selected. Search loaded invoices, review open and overdue balances by currency, create a missing billing customer, and approve invoice creation, sending or unpaid-invoice cancellation. Payments & refunds adds reviewed refunds, source receipts and selected-record CSV exports. Provider payment facts remain authoritative; reports state their loaded scope.

Enable Events & Tickets and connect the business's Stripe account and Resend. Buyers choose several tickets and pay through secure card fields on an internal payment page. Confirm admission from verified payment; existing orders retain their price. Accelerate's homepage promotion opens the workshop overview using saved event details. Refunds, buyer exports, reservation reconciliation and reviewed AI changes share the same workspace services.

Prepare recipients, message version, cadence and limits. Approved activation uses the existing sender and checks recorded replies, suppression and stop rules.

Use the configured model, scheduler and registered tools. Work keeps its source context and recorded results; current policy determines which changes need a decision or can use bounded internal permission.

Connected Drive indexing retains extracted text from supported files. Review extracted information against the source; processing depends on the configured sync, supported file type and available AI workflow.

Contact import lets you inspect proposed records before confirming them. Other requests use the assistant’s available tools and may need a separately reviewed proposal.

Connect and verify the mailbox, then inspect sync results and identity matches. Unfamiliar senders can be reviewed before their conversations are linked to a contact.

A configured calendar connection provides meeting context. Meeting preparation identifies upcoming appointments; Meeting commitments turns an explicitly entered checklist into assigned tasks.

Review the provider permissions, job limits and sync results to understand the history imported. A connected account does not guarantee that its entire archive has been read.

CSV, TSV and flat JSON use explicit column mapping with no model request. AI-assisted extraction is optional for free-form lists. Both paths retain original source rows, identify existing contacts and require approval before canonical writes.

Open a contact to see its next step, recent open work, linked conversations, opportunities and timeline together. Ask AI opens a draft question about that record; the person decides when to send it. Missing sources or unresolved identities remain visible work for the team to check.

Company records tie people, deals, and history together, so an account is one place to look instead of a set of names you have to join up yourself.

Open the opportunity to inspect its customer, activity and next step. Calendar shows dated next actions on the viewer's local day and keeps unscheduled opportunities visible. Individual and bulk status changes from Leads use the same Pipeline rules, with named recovery details for incomplete updates. Retrying the same change preserves its existing follow-up or client engagement. Use the evidence you have before changing the record, then confirm the saved result.

Work starts with your open tasks and can show team work when needed. Use the same tasks as a list, status board or date calendar; filter and save a personal or workspace view; then edit, snooze or complete work through its existing task service. The list supports keyboard triage. The inspector edits instructions, keeps its task link through reload, opens related records and offers read recovery while preserving failed edit drafts. Ask AI can prepare task reopening and description edits for review, with stale-change checks before execution. Onboarding and meeting workflows can create assigned checklists linked to their source records. A client follow-up appears beside its activity and refreshes the task views in Work and Today.

Create and edit items in Content, clear optional details, and move work between current columns. Ask AI or a connected MCP assistant can prepare creation, edits, permanent deletion and moves for review in Approvals. Saving checks current access and refuses changed items. Calendar status tracks the work; publication remains in the publishing destination.

Save notes where the team can find them alongside the relationship history. Inspect the original source when a note affects a decision or commitment. Client records load independently of their history, retain your edits during refreshes, and offer a separate retry for each failed section.

Review a saved Blueprint inside Architect, preview a patch and approve its draft save. Simulate workflows without live effects before the separate workspace application. Use supported settings where available. New fields, record types or lifecycles may require a source extension that reuses the existing identity and permission services.

Suggested relationships from Opportunity Radar arrive with their sources and wait for your review. An introduction offer is an offer, and it does not mean the other person has agreed to be contacted.

Open the linked source to inspect a timeline entry. The activity record helps distinguish human decisions, proposed work and executed results.

Identity matching lets you match a sender, create a contact when appropriate or leave the item for later. Imports also surface possible matches for review.

Source briefing runs on a budget you set and stays off until you turn it on. Reviewed outreach uses the sender you configured only after an exact human approval, with contact checks and cooldowns. Automatic discovery and outcome measurement are still being built.

New forks include an editable, neutral homepage and a fictional demo. Connect published forms to workspace intake, choose models by provider and price, and cancel pending suggestions without losing edits. Save, reload and import run one at a time, failed reloads retain local edits, and unverified confirmations keep the original retry. Revision history supports rollback; installation owners can connect ChatGPT through the same editor services. Private drafts preview at real phone, tablet and desktop widths, with public page styling and inactive links and forms. Private workspace drafts retain typed titles through failed refreshes and require a fresh read after uncertain saves or discards. Try private creation, renaming and discard in the fictional demo, with separate drafts per business and clearly labeled AI examples.

Each workspace connects its own organization account. An uncertain submission keeps its receipt for review instead of being reported as published.

With Stripe invoicing enabled, open Invoices from the sidebar to create customer invoices, then use Collections to manage overdue balances. Workspace-created invoices also offer an AI-assisted customer-page editor with style starters, phone previews, Undo/Redo, and separate publication approval. Ask AI to propose a pause, promise, dispute, owner or next action, then review the exact change. Fresh invoice and contact checks guard approvals; reminders require a separate review and send receipt.

Stripe stays the payment authority, and the workspace shows a checkout or webhook delay as pending rather than guessing an outcome.

An explicit outreach request can stage a reviewable email proposal in the same conversation. Check the wording, recipient and commitments in Work before approving a send, then inspect its recorded result.

Enter the commitment directly or use a supported task proposal. Meeting commitments takes an explicit checklist; automatic transcript extraction is a separate workflow.

A won opportunity opens its onboarding checklist with the source selected. The bundled workflow plugins prepare one to ten tasks with descriptions, dates and assignees. Review the plan and confirm the created tasks after execution.

Inspect the record, proposed stage and supporting context in the approval flow. Confirm the saved stage and activity after the action runs.

Inspect the audience, sender, content, timing and limits before activation. Reply and suppression handling stop eligible future work through the shared campaign services.

Successful rows stay saved if another row fails, so a partial run is visible and the unfinished part can be retried.

Configure the required capabilities and schedules, then inspect job and action results. A new business rule may require a source extension rather than a setting.

Approval records the decision; execution records the result. Autonomous proposals are checked before they reach the queue, and each one explains why it earned your attention. Anything you asked for directly is never held back, and a background check that finds nothing finishes quietly instead of reporting it. Eligible autonomy changes need a separate human decision, and restricted external actions keep their approval requirements.

Each connected system is registered against the facts it owns, with a tier, an owner and a last-verified date. Grounded searches carry that authority, flag differing evidence for review, and mark overdue sources as stale.

Learning Inbox keeps the proposed rule, scope and source available for review. Approved independent rules stay active together, and edited replies can propose reusable corrections. Cited references and later context receipts make their use inspectable.

A recorded rejection helps the team understand the decision. Propose reusable guidance through Learning Inbox when the correction should apply beyond that one action.

Activity and action receipts retain evidence of execution. Use those records to assess the result; a completed action alone does not establish a business outcome.

Changing a level, a constraint, or the source clears the previous approval, so a shift in policy always comes back to a person. Revoking a permission keeps its audit history.

Today pairs customer context with specific review actions in full-width rows. Expand a finding’s source and next step, or open its linked record to act.

The Meeting preparation plugin provides a time-ordered report. A configured Meeting Intelligence Coworker can support richer briefs; its sources and execution must be set up separately.

Pipeline follow-up and Overdue commitments apply defined rules to available records. Inspect the source and report coverage before drawing conclusions about the customer.

The Bookings module keeps topic interest, pairing, question, format, date and the verified Google invitation separate. Today links to the production. Review two inbound participant acceptances before approving an invitation, then recheck the provider event and responses.

The team can return to that context before the next conversation. Use an assigned task when the question needs a specific owner and due date.

Nine business groups explain where to review the operation, manage customers, deliver client work, follow billing, communicate, use AI, connect Apps and adjust settings. Personal and shared Today arrangements keep view tools under More, wide desktop layouts keep independent columns, and Search and Ask AI stay available while you scroll. The mobile dock keeps the three daily destinations within reach and waits for notifications to finish closing before returning. Dismissing notifications returns focus to the bell; following a notification keeps focus with the destination. Notification panels skip animation under reduced motion. More keeps the page paused through closing, then opens Search or Ask AI with keyboard focus. Following a menu link focuses the destination heading.

Ask AI reads records, prepares replies and tasks, and previews ordered jobs. Configured background work retains progress after the browser closes. You can approve exact proposals inside chat and grant bounded permission for named internal operations. Messages, publishing, billing and permission changes keep human review. Cost controls pause model requests or recurring coworker work, set request and spending limits, and show held budget separately from reported provider charges. Available tools depend on modules, providers and current access.

Compatible clients use the same registered tools, record services and approval rules. An authenticated member connection can delegate ordered work and read or control its progress. Tenant bearer keys retain integration scope. Pending proposals link to the exact human review, and unsupported operations are reported plainly. A separate owner-only Site Studio connection handles website editing.

The board scrolls freely, keeps its column controls at every screen size, and supports dragging, touch, and a stage control for moving a card without dragging. Deployments with a dedicated app address also support installation, connection status and local drafts that you can read and reuse after reconnecting.

Use the documented tool, adapter and service contracts. A custom integration needs implementation and permission checks for the particular records and actions it exposes.

Metric definitions are documented, so a forecast is labelled as a forecast and does not read as a recorded fact.

Configuration covers the supported settings today, and broader changes use source development. A general-purpose in-app App builder is planned.

Text contrast is checked before a theme saves, density is adjustable independently, and a theme follows the same permissions and revision checks as other branding. Delete, discard and archive confirmations use the theme's danger appearance. Nested confirmations dim the editor beneath them and reveal it again when closed. Phone navigation returns after the last dialog finishes closing. Dialogs open and close immediately under reduced motion. Demo choices stay separate from the live workspace.

Core capabilities remain available. Plugins and Integrations show each module's status, owner, declared autonomy and available execution receipt. Disabling an optional module removes its navigation and gates its routes and tools, while preserving existing records.

Coding-agent instructions reserve pickup for explicit backlog requests and keep ordinary continuation requests on the current task. The agent does not need a ticket key or a provider-specific command, and it never asks you to paste credentials. If pickup cannot use the approved source, it names the blocked card and the recovery step before claiming. With recovery enabled, a replacement agent can resume an interrupted task from its saved state. Verification renews the active claim, and checkpoints include safe unfinished source while excluding credentials and generated output.

Activity and receipts link actions to source records. Sensitive content stays in authorized records rather than being copied into every audit entry.

Use the relevant configuration control and inspect any pending work. Historical records remain available according to the feature’s retention and access rules.

Managed workspaces use tenant-scoped records, active membership, and row-level policy. A self-hosted installation uses your own database and provider accounts; agree on export and handoff responsibilities before a managed implementation.

The runtime rechecks access for supported operations. An installation can offer Google sign-in alongside email, while active membership still controls workspace access. Review your workspace’s configured permissions instead of assuming a job title automatically grants or hides particular screens.

Setup and operational health views show supported checks with their evidence. Follow the named recovery step and verify the specific connection or job afterward.

Give Claude Code or Codex the business workflow and review its working result. The agent follows setup and extension contracts, reusing customer identity, permissions and business services so each custom screen needs less shared infrastructure. Review its exact source and checks before release, and keep account ownership and recovery responsibilities clear. Setup shows the recorded core version separately from your fork commit and checks the supported stable upgrade path.