> ## Documentation Index
> Fetch the complete documentation index at: https://docs.threataware.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Settings → Teams

> Logical groups of users for sharing saved views, actions, Studio apps, and notifications

## What Teams are for

[Settings → Teams](/settings/teams) defines logical groupings of users that enable sharing without granting cross-role privileges. A user can belong to multiple Teams.

<img src="https://mintcdn.com/threatawareltd/IwzdezxNqgZB-5I4/images/core/settings-teams.png?fit=max&auto=format&n=IwzdezxNqgZB-5I4&q=85&s=485432c36e7cc4d113a8d9911cc0a35e" alt="Teams page showing IT Service Desk (8), Management (7), Asset Governance (5), Data Compliance (9), SecOps (10)" width="1440" height="900" data-path="images/core/settings-teams.png" />

Example teams:

| Team             | Members |
| ---------------- | ------- |
| IT Service Desk  | 8       |
| Management       | 7       |
| Asset Governance | 5       |
| Data Compliance  | 9       |
| SecOps           | 10      |

## What Teams unlock

| Capability                | How                                                                                     |
| ------------------------- | --------------------------------------------------------------------------------------- |
| **Shared Saved Views**    | When saving a view, pick "Team" visibility and select teams                             |
| **Action ownership**      | Actions can be assigned to a team in their Owner field                                  |
| **Studio app sharing**    | Publish to one or more teams instead of Everyone                                        |
| **Notifications routing** | Action automations can target a team's nominated channel (Teams/Slack webhook)          |
| **Cross-area context**    | Most "Team" filters in the product (Audit Log, Issue assignment) accept Team membership |

Teams are about *scope* not *privilege*. A Team doesn't grant additional permissions — it enables sharing.

## Creating a Team

<Steps>
  <Step title="Click + Create Team">
    Top-right.
  </Step>

  <Step title="Name">
    Use a descriptive name aligned to your org chart or function — `SecOps`, `Asset Governance`, `Client-Acme`.
  </Step>

  <Step title="Add members">
    Pick users from your tenant. Search supports name / email.
  </Step>

  <Step title="Save">
    Team is immediately usable in the visibility pickers across the product.
  </Step>
</Steps>

## Editing a Team

Click any Team's **Edit** to:

* Add or remove members
* Rename
* Delete (revokes Team-scope sharing on any view/action/app that referenced this Team)

<Warning>
  Deleting a Team doesn't delete the underlying views, actions, or apps — but their **visibility** flips to Private (only the original creator can see them). Reassign visibility before deleting, or expect to manually re-share.
</Warning>

## Team design patterns

<AccordionGroup>
  <Accordion title="Mirror your org chart">
    Most common: one Team per real-world team (SecOps, Help Desk, Compliance, Engineering Ops). Easy mental model, easy to maintain.
  </Accordion>

  <Accordion title="Cross-functional projects">
    Time-bound Teams for specific projects (`Project-Win11-Migration`, `Acquisition-Acme-Onboarding`). Disband when complete.
  </Accordion>

  <Accordion title="MSP per-client teams">
    One Team per client (`Client-Acme`, `Client-Bravo`). Combined with a tag-filtered custom role, you scope both *what* technicians see and *who* they share with.
  </Accordion>

  <Accordion title="Geo / region teams">
    `EMEA-Ops`, `APAC-Ops` — useful when regional teams own different bits of the estate.
  </Accordion>
</AccordionGroup>

## Cross-references

<CardGroup cols={3}>
  <Card title="Access Control" icon="users-gear" href="/access-control">
    Conceptual model
  </Card>

  <Card title="Settings → Users" icon="user" href="/settings/users">
    Assign users to teams
  </Card>

  <Card title="Settings → Roles" icon="shield" href="/settings/roles">
    Roles grant permissions; teams enable sharing
  </Card>
</CardGroup>