What an approval covers
An approval describes a proposed tool action in a workspace. It is tied to the action and context being reviewed. Read the destination, account, and arguments, rather than approving only because the surrounding task sounds familiar.
Approve or reject
Use the pending action's decision controls. Approving permits that proposed action to proceed; rejecting keeps it from proceeding and gives you a chance to explain the change. A rejected action is not a failed connection.
Permission still applies
The server checks both the tool's classification and its configured mode. A request in chat cannot widen a connection's access. Only change standing permission rules when the workspace administrator understands the consequences.
Review the result
After an approved action, inspect the reported result and the external destination when appropriate. Save the decision context with the task. For repeated workflows, prefer a narrow permission rule over a broad exception.
Open the relevant screen
Use Approvals in the active workspace. Sign in if needed. Check the workspace name before changing shared settings, connections, or billing.
If a control is unavailable, ask the workspace administrator or contact support. Include the screen, the action you tried, and the approximate time. Keep credentials and private customer material out of the request.