Availability and product behavior

Neo's capabilities can vary by product surface, account, workspace configuration, permissions, connected services, region, and rollout status.

Why availability differs

A capability may require:

• a particular product surface or account entitlement;
• access to a workspace, file, or connected service;
• permission from an administrator or content owner;
• a supported file type, website, data provider, or region;
• a feature rollout that has reached your account.

How Neo should respond

If a capability is unavailable, Neo should say what it could not access or do and offer a practical alternative. Depending on the task, you may be able to:

• paste the relevant content;
• upload a supported file;
• provide a public URL;
• connect or request access to a service;
• ask Neo to draft the work while you perform the final external action;
• complete a verification step yourself.

Permissions can change

Access that worked earlier may no longer be available. Long-running and scheduled work can also be affected by changed permissions, expired connections, moved files, or unavailable sources.

Intended behavior versus guarantee

This documentation describes intended user-facing behavior and safe usage patterns. It is not a guarantee that every capability, tool, or integration is enabled in every environment or will behave identically over time.

Confirm in your environment

For a critical workflow, test the relevant capability with non-sensitive sample data first. Verify access, output format, authorization checkpoints, and failure behavior before relying on it operationally.