Verify identity and resource scope
Check which account, workspace, project, or connection the tool is using. A valid resource name in the wrong account can look like a permission problem, and an outdated connection may no longer have the expected access.
Compare the requested operation with the granted role or token scope. Read access may be sufficient for inspection, while editing, sending, or deleting usually requires a more specific permission.
Grant the minimum necessary access
Ask an administrator to grant the narrow role or scope required for this task, and follow the organization's approval process. Do not share passwords or copy a powerful token into a prompt or log.
Retry with the same resource after access is updated, and verify the result. If access should not be granted, keep the tool read-only or use an approved alternative; do not conceal the failure by reporting the action as completed.