An absent option can have several causes. Treat these as separate checks.
| Layer | Question | Example |
|---|---|---|
| Release status | Is the capability released on this surface? | A staging-only capability is not public production functionality |
| Account access | Is the workflow enabled for this account or firm? | Slack, Teams, and email using a linked Portrait account require full Easel access; Easel ask and session commands in CLI also require the Easel CLI bridge |
| Data entitlement | Is the firm licensed for the requested source or depth? | Third Bridge and Visible Alpha access depend on firm agreements |
| Surface support | Does this client expose the workflow? | MCP does not expose Easel |
| User identity | Is the intended Portrait user connected? | Slack, Teams, email, CLI, and MCP act as a linked user |
| Usage | Does the relevant bucket have remaining capacity? | Deep Research uses Normal research usage |
Release labels
- Production — released on the named surface; account, entitlement, and usage checks can still apply.
- Beta — released with a narrower or changing contract; verify current limits before depending on it.
- Unreleased — staging, planned, or otherwise unavailable as public production functionality.
Access labels
- Account-gated — provisioned only for applicable accounts or firms.
- Entitled — available only when the firm has the required source or data access.
- Usage-limited — subject to the connected account's current usage and concurrency rules.
Data access does not transfer automatically
A firm's source entitlement determines what Portrait may retrieve and display, but provider licences can still restrict redistribution or connected-surface access. A source visible in the web app is not necessarily available through MCP or an external bridge.
Diagnose a missing option
- Confirm the product surface named in the relevant guide.
- Confirm that you are connected as the intended Portrait user and organization.
- If you have app access, check Settings → Usage in the web app when the workflow consumes included research usage. Usage shows credit balances, not which features are enabled for your account; a Mosaic balance or a feature listed there does not establish access. For an email-only trial, use the allowance or admission notice in the same email thread; that trial has no app sign-in.
- Check the page for a beta, account, admin, or source-entitlement requirement.
- Troubleshoot access and setup or contact the team with the exact surface and observed behaviour.
Separate connections and grants
| Workflow | Additional check |
|---|---|
| Scheduled Research | Feature access, eligible usage setup, task authorization, and sufficient commitment budget |
| MCP inside Easel | Account access and provider link, selected at session start or restart; BIA tools remain disabled despite setup |
| Partner API | Provisioned environment, enabled partner organization, partner audience, and operation scopes |
| Email-only trial | Sender approval and remaining trial messages; no app sign-in |
The support assistant cannot inspect these grants or connections from the fact that you mention a feature. A missing control, failed authorization, refused execution, and missing notification require different recovery steps.