Skip to main content

​
Plan and execute a day

Use the Command Center to review priorities. Organize actionable work in Tasks, fixed events in Calendar, and actual work sessions in Track. Smart scheduling has explicit priority and duration rules; calendar provider synchronization is separate from the local planning view. Review progress and goals after updating source work. A dashboard summary is a view over records, not a second place to maintain the same task manually.

​
Turn a meeting into reviewed work

Meet separates planning, participating, recording, transcription, and follow-up proposals. Review the generated evidence before creating a task or calendar event. See Follow-ups, Live assistants, and Solo mode. Provider connectivity, access, and consent affect which tools are available; opening a room is not evidence that transcription or an external provider is working.

​
Capture ideas and knowledge

Workspace Notes, documents, whiteboards, habits, readings, and planning surfaces remain in Web where they have not been assigned to another app. Use Mind for mindboards and nested ideas, Drive for files, and Tulletin for creative worlds and published wiki revisions. These are separate content models; following an app link does not copy or synchronize every record. Notes voice analysis records locally until the user explicitly submits transcription/analysis. Saving the reviewed result creates a workspace Note; it does not automatically create tasks or events. A partial transcript can be useful even when analysis fails, and retries must preserve the actor/workspace scope.

​
Collect information and follow up

Build and share a Form, then review responses and analytics in its studio. Manage the people and groups who participate in Contacts. Forms responses and CRM membership are separate: do not assume a response creates a user, group enrollment, or outreach message unless an explicitly configured product workflow does so.

​
Run a sales workflow

Use Inventory for catalog, stock, costing, bundles, and checkout readiness. Publish a Storefront for buyers. Review provider payment evidence and audit trails before treating an order as paid. Browser success return URLs are navigation signals, not an independent payment proof. Finance handles financial records; Pay handles workspace subscription billing. These three products have different responsibilities.

​
Run a learning workflow

Teach serves educators; Learn serves eligible learners and linked parents. Education access and parent visibility are explicit. Programming runs use the configured Judge/Devbox boundary: local editor diagnostics do not prove a submission verdict. Nova has separate prompt-learning and challenge experiences.

​
Integrate rather than duplicate

Developers should use shared internal API contracts and the SDK. The route catalog helps locate an owner, but private internal handlers are not automatically supported third-party APIs. AI recall is context, not permission to send messages, publish, or mutate a workspace.