Not every capability described in this guide is enabled in every environment. This page groups capabilities by what they typically require, and shows how to determine what is enabled for you right now. Exact availability can change with product surface, account, workspace configuration, and rollout status; treat the groups below as the expected shape, and the check as the ground truth.

Available to everyone

Core capabilities that do not depend on connections or configuration:

conversation, explanation, and tutoring;
writing, editing, and summarization from material you provide;
analysis and structured reasoning over pasted content;
planning, checklists, and reviews;
working with content you paste directly into the conversation.

Available when enabled

Present on most surfaces, but subject to account or workspace settings:

web browsing and search;
file upload and analysis;
workspace files and artifacts;
durable memory and structured knowledge;
image understanding, and image creation where image tools are enabled;
scheduling and reminders;
delegated work.

If one of these is missing, it is usually a settings or entitlement question rather than a limitation of Neo itself.

Requires a connected service

Only available after you or an administrator connects the service and grants access:

reading and drafting in email or messaging threads;
calendars and meeting context;
external document stores and drives;
finance and market data providers.

A connection can also expire or be revoked, which affects long-running and scheduled work that depends on it.

Requires workspace permission

Available in principle, but gated on what your role in the workspace allows:

reading or modifying shared workspace files;
acting on resources owned by other people or teams;
workflows an administrator has restricted to certain roles.

Neo should tell you when a permission—rather than a capability—is what is missing.

Experimental or rollout-dependent

Capabilities that are new, in staged rollout, or explicitly marked experimental may appear for some accounts before others, change behavior between versions, or be withdrawn. The changelog records notable changes; pages describing such capabilities carry a status label under their title.

Check your own environment

Because availability is dynamic, the reliable answer comes from your environment, not from documentation:

Ask directly. “Which tools and connections are available in this conversation?” Neo should enumerate what it can currently use.
Try a harmless probe. Ask for a small, non-sensitive version of the task—browse one public page, create one test reminder, read one test file. A capability that works on a sample will work on the real task.
Read the failure honestly. When something is unavailable, Neo should say what it could not access and offer an alternative (paste the content, upload a file, connect the service). Vague output with no stated limitation is a reason to probe again, not to assume success.
Check connections and settings. Connected services and their permissions are managed in your product's settings; an administrator manages workspace-level access.
Re-check before relying on it. For an operational workflow, verify access again close to the time it matters—permissions and connections change. See Availability and product behavior for how behavior should degrade when they do.

Capability availability