Team Management
Control & DirectionTeams are the organizational building blocks of your security program. Each team represents a functional group within your security organization — such as Security Operations, GRC, Identity & Access, or Cloud Security — with assigned members, a designated manager, and connections to goals, projects, and risk ownership. Navigate to Operating Model → All Teams to manage your teams.
Teams integrate with Goals & Initiatives (team-level goals), Execution Tracking (project assignments), Audit Management (audit ownership), and Vendor Risk (vendor relationship ownership).
Team list
The main teams page displays all teams in an editable table. Use the search bar to filter by name or code, or filter by parent team to focus on a specific branch of your hierarchy. Each row shows the team name, code, color, parent team, manager, and member count.
From the list view you can archive or delete teams using the row actions menu. Archived teams are retained for historical reference but no longer appear in assignment dropdowns across the platform.
Creating a team
Navigate to the creation form
Click New Team from the team list page, or navigate directly to Operating Model → New Team.
Fill in team details
Provide the following information:
| Field | Description |
|---|---|
| Name | The display name for the team (e.g., “Security Operations Center”) |
| Description | A free-text summary of the team’s purpose, scope, and responsibilities |
| Code | A short identifier used for quick reference (e.g., “SOC”, “GRC”, “IAM”) |
| Color | A color label for visual distinction across charts and lists |
| Parent Team | Optional. Select an existing team to establish a hierarchical relationship |
| Manager | Optional. Assign a user as the team’s manager |
Save the team
Click Save to create the team. You are redirected to the team detail page where you can begin adding members.
Team colors
Each team can be assigned one of ten colors for visual identification throughout SecureHive. Colors appear on team cards in the org chart, list view badges, and anywhere teams are referenced.
| Color | Use case suggestion |
|---|---|
| Blue | General security, default teams |
| Green | Compliance and audit functions |
| Purple | Architecture and engineering |
| Orange | Risk management |
| Red | Incident response and SOC |
| Yellow | Awareness and training |
| Pink | Privacy and data protection |
| Indigo | Identity and access management |
| Teal | Cloud and infrastructure security |
| Gray | Administrative or support functions |
These suggestions are not enforced — choose whichever colors best suit your organization’s conventions.
Team detail page
Click any team name to open its detail page. The detail view displays the team’s full information, including description, code, color, manager, parent team, and a list of all assigned members. From here you can edit the team’s details or manage its membership.
Editing a team
Click Edit on the team detail page to modify any field. You can change the team’s name, description, code, color, parent team, or manager at any time. Changing a parent team repositions the team within the hierarchy, which is immediately reflected in the Team Chart.
Managing members
Members are users assigned to a team with a specific role. Each team member record tracks who was assigned, when they were assigned, and who made the assignment.
Adding members
From the team detail page, click Add Member. Select a user from your organization and specify their role. The role field is free-text, allowing you to define titles that match your organization’s structure (e.g., “Security Analyst”, “Team Lead”, “GRC Specialist”, “Penetration Tester”).
Member details
Each member record includes:
| Field | Description |
|---|---|
| User | The assigned user from your organization |
| Role | Free-text role or title within this team |
| Assigned At | The date and time the member was added |
| Assigned By | The user who made the assignment |
Removing members
Remove a member from a team through the member row action menu on the team detail page. Removing a member does not affect their user account or their membership in other teams.
Team hierarchy
Teams support parent-child relationships to model your full organizational structure. When creating or editing a team, select a Parent Team to position it as a child within the hierarchy. A team can have one parent and multiple children, enabling you to build a tree structure of any depth.
For example, a top-level “Information Security” team might contain child teams for “Security Operations”, “Governance, Risk & Compliance”, and “Security Engineering”. Each of those can in turn have their own child teams for further specialization.
Parent-child relationships drive the layout of the Team Chart and the Members Chart, and they provide context when reviewing goals, projects, and risks at different organizational levels.
Archiving and deleting teams
From the team list view, use the row actions menu to archive or delete a team.
Archiving removes the team from active use — it no longer appears in dropdown selectors or assignment workflows — but preserves the team and its membership for historical records.
Deleting permanently removes the team. Deletion is only available for teams with no active assignments (goals, projects, or members). If a team has dependencies, you must reassign or remove them before deletion.
Permissions
Managing teams requires the appropriate team management permissions. Users with team management access can create, edit, archive, and delete teams, as well as add and remove members. Users without these permissions can view team information and org charts but cannot make changes.