Access is checked at more than one level
Work Mode availability depends on the workspace and Vulcan Intelligence access. App-specific tasks also depend on the app being available to the workspace and allowed for the team member. Editing, lifecycle controls and connection management may need different permissions.
External providers add another boundary: the account, repository, team/project or device must be selected and permitted by the user’s own connection. A successful read is not proof that writes are enabled, and a previously connected account can later be revoked.
Read the current controls, not an old offer
Use the current account, Billing and connection screens for applicable access and pricing. Do not assume that a product trial includes unlimited AI generation, free advertising, a website build or a paid provider subscription. Different work paths can have separate entitlements and usage rules.
The documented source includes controlled rollouts and provider-specific gates. If the capability is absent, ask about availability rather than interpreting a marketing example as a guarantee that your user can execute it today.
Separate the costs
| Kind of work | What to verify |
|---|---|
| Analysis or planning | The current AI usage/credit policy and whether another attempt is a new request. |
| Generated files and images | Available generation capacity and the saved job’s status. |
| Advertising changes | Provider budget/currency and the effect of the exact approved action. |
| Customer website deployment | Hosting/provider plan and any separate domain charges. |
| External plugin use | The user’s provider subscription, token scope and rate limits. |
A recommendation to change a budget is not a charge by itself. An approved provider action may have real spending consequences. Review the exact proposal rather than inferring cost from a task title.
Handle a limit at its source
A provider rate limit, missing app permission, depleted AI allowance and paused rollout are not the same problem. Read the error and connection state, then use the appropriate account or app controls. Do not retry repeatedly while the cause is unchanged.
If a task is interrupted, inspect its saved state before beginning a fresh attempt. A replacement request can consume additional usage or duplicate an external effect; it is not necessarily a continuation of the original.
For workspace administrators
Grant only the app and role permissions needed for the person’s work. Keep external connections personal, explicitly scoped and periodically reviewed. Do not share credentials between users to avoid setup. For Desktop Commander, evaluate full-device terminal permission separately from selected-folder file work.
Have a clear owner for approving spending, publishing and customer communication. The assistant can prepare the work, but the organization still needs people who understand and approve the consequences.