> ## Documentation Index > Fetch the complete documentation index at: https://help.superhawk.ai/llms.txt > Use this file to discover all available pages before exploring further. # Team & Access > Workspaces, members, teams, and who can see what. Everything in Superhawk lives inside a workspace. This section covers how workspaces isolate data, how people get in, and how access is controlled once they are. ## Workspaces A workspace is a team's environment, and workspaces are fully isolated from each other: * **Data is isolated.** Accounts, health, signals, tasks, and memory in one workspace are never visible from another, and never mixed into another workspace's answers. * **Integrations are per-workspace.** Each connects to its own CRM, support desk, and analytics. * **Members are managed independently.** Membership and permissions apply to one workspace only. * **Mode is per-workspace.** See [Workspace Modes](/getting-started/workspace-modes). ## Switching workspaces If you belong to more than one, use the workspace switcher in the navigation. Everything you see changes with it: accounts, signals, tasks, integrations, and members. ## Teams Within a workspace, members can be organised into **teams**. Teams are what make scoped access work: a permission can grant someone access to their own accounts, to their team's accounts, or to everything. Without teams, access is effectively all-or-own. With them, a regional lead can see their region without seeing the whole book. ## Access control Superhawk uses permission sets rather than fixed roles. **Owner**, **Admin**, and **Member** exist as built-in sets covering the common cases, and custom sets can be defined for anything else. See [Roles & Permissions](/team/roles-permissions). ## Audit Membership and access changes are recorded: members added and removed, ownership transferred, permissions changed. Who did it, and when. ## Related Invite people and manage your workspace team. How permission sets, resources, and scopes work.