Start with membership
Workspace membership establishes which workspace a person may use. Teams and resource scopes can make access narrower. Check the active workspace and the resource's audience when a person cannot see something.
Review connection scope
A connection can expose sensitive information even when its intended task is simple. Confirm which people and teams may use it and which tools are permitted. Keep a personal account separate from a shared source where appropriate.
Do not infer access from a channel
A Slack or Teams conversation identifies where a request comes from. It does not authorize every participant to use every connection. The server's access checks still apply when a task arrives through chat.
Test the role you are granting
Review both a permitted operation and a denied one with the intended role. Avoid broadening permissions simply to make an unrelated test pass. Document who owns the access policy.
Open the relevant screen
Use Workspace permissions 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.