Teams: Secure Your Entire Flock

# Overview This walkthrough introduces StackHawk Teams, a feature designed to help organizations group and organize their applications while ensuring team members follow the principle of least privilege by accessing only the features and applications necessary for their roles.

# Key Topics - **Role-Based Access Control and the Member Role**: StackHawk previously supported Owner (access to all settings) and Admin (access to all settings except billing). The presentation introduces the "Member" role, which restricts users from organization-level settings such as audit logs, integrations, user management, and team setup, leaving them access only to their personal profiles. - **API Key Role Restrictions**: API keys generated by individual users automatically inherit and are bound by the permission restrictions of that user's assigned role. - **Teams Organization and Scoping**: The Teams capability enables administrators to group specific applications together and assign designated users to those teams. Once assigned, users and admins can use a teams dropdown selector to filter views and interact strictly with applications assigned to that team. - **Application Access Scoping for Members**: Demonstrating from the account of a user named Jordy, members only see and access the specific applications mapped to the team they belong to, preventing unauthorized access across broader organizational assets. - **Enterprise Availability**: The Teams functionality is provided to customers on the Enterprise plan and is also accessible during trial periods with Enterprise features enabled.

# Technical Details - **Roles Breakdown**: - **Owner**: Complete access to all account settings, including administrative and billing controls. - **Admin**: Complete access to all settings except billing. - **Member**: Restricted from organization-level controls (audit logs, integrations, user management, team setup); restricted to personal profile management. - **API Enforcement**: Inherited role permissions apply down to generated API keys. - **Interface Workflow**: Setup occurs via an admin account to create a team, map specific applications into it, and add users. A teams dropdown filter updates the console UI to isolate the scoped applications.

# Takeaways StackHawk Teams enables organizations with growing teams to maintain tight access controls over their application security testing workflows. By combining the Member role with team-level application assignments, organizations ensure team members can only test and view the applications required for their specific work. Support is available via in-app chat or at support@stackhawk.com.