Your customer work.
Connected.

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.

An import is a review step rather than a blind write. The system flags rows that look like someone you already have, which is how an unfamiliar sender ends up attached to the right person instead of becoming a duplicate.

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. 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. Onboarding and meeting workflows can create assigned checklists linked to their source records.

Save notes where the team can find them alongside the relationship history. Inspect the original source when a note affects a decision or commitment.

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.

Uses the shared approval process.

New forks start with an editable, neutral product homepage and a fictional demo that needs no credentials. Guided setup connects your own workspace; save a contact and task before adding optional providers. Create your own pages, connect published forms to reviewed intake, and choose an AI model by provider and price or edit manually. Drafts stay private until published, with revision history and optional owner-only ChatGPT access through the same editor services.

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

Uses the shared approval process.

Fresh payment and contact checks stop a stale reminder going out. The receipt tells you whether the send was confirmed or still needs reconciliation, so you never retry blind.

Uses the shared approval process.

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.

Uses the shared approval process.

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

Uses the shared approval process.

The bundled workflow plugins prepare one to ten tasks with descriptions, dates and assignees. Review the plan and confirm the created tasks after execution.

Uses the shared approval process.

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

Uses the shared approval process.

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

Uses the shared approval process.

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.

Uses the shared approval process.

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 provides source-linked attention and supporting context. Open a finding to inspect its record before acting.

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.

Eight primary destinations group the workspace around Today, Work, Records, Conversations, Knowledge, Coworkers, Apps and Settings. Personal and shared Today arrangements are available, wide desktop layouts keep independent columns, and the mobile dock keeps the three daily destinations within reach.

With Content enabled, the assistant can list calendar items by status or category and prepare a grounded editorial brief when an AI provider is configured. It cites records it reads and reports unavailable sources instead of guessing.

Compatible clients can use tenant keys; supported ChatGPT web workspaces can use a separately configured OAuth connection. Both reach registered workspace tools with module and approval rules. A distinct owner-only Site Studio OAuth connection can edit the installation website under revocable delegation, with recorded results.

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. Demo choices stay separate from the live workspace.

Core capabilities remain available. Disabling an optional module removes its navigation and gates its routes and tools, while preserving existing records.

The agent does not need a ticket key or a provider-specific command, and it never asks you to paste credentials. 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.

Use the neutral starter and self-hosting guides for your own installation. Review the documented content exports, data ownership and support arrangements when planning a handoff.