The Team Management section in Stood CRM Admin View provides comprehensive capabilities for creating teams, configuring deal flows, setting up team transitions, and managing team-specific settings. This guide covers all team-related operations.
Navigate to the Admin section in the main navigation
Only users with admin privileges can access this view
Select "Teams" from the dropdown in the admin header
The admin view displays the current app version at the bottom of the page
The admin interface uses a dropdown menu in the header to switch between three views:
Teams: Team management and configuration
Users: User and group management
Global Settings: Application-wide settings
When viewing teams, you can use toggle buttons to show/hide different sections:
Topology: Team structure, categories, and workflow connections

Members: Team members and access groups
Connectors: API keys, webhooks, and integrations

Click the "Team" button (with + icon) in the admin header
Fill in the required information:
Team Name (required): Descriptive name for your team
Category: Select from:
Pre-sales: Initial customer engagement and qualification
Sales: Core sales activities and deal progression
After-sales: Post-sale support and customer success
Next Team (optional): Select which team receives deals when they reach final (s3) stage
Click "Create"
Pre-sales: Handles initial customer contact, qualification, and lead nurturing
Sales: Manages the core sales process, proposals, and deal closure
After-sales: Provides post-sale support, onboarding, and customer success
Each team card displays comprehensive information and management options organized into collapsible sections.
Team Name
Editable via the pencil icon
Click to rename the team
Team name cannot be empty
Team ID
Unique identifier (copyable)
Click to copy to clipboard
Used for API integrations and references
Category
Displays current category with badge
Click the category badge to change it
Categories: Pre-sales, Sales, After-sales
Teams can customize their deal stage labels (s0, s1, s2, s3, s4):
Stage Configuration
Stages are displayed in two groups: [s0, s1, s2] and [s3, s4]
Click any stage button to edit its label
Labels are team-specific and stored in Firebase
Changes take effect immediately
Stage Labels
s0: Initial stage (e.g., "Lead", "New")
s1: Qualification stage (e.g., "Qualified", "Contacted")
s2: Proposal stage (e.g., "Proposal", "Quoted")
s3: Closed - won (e.g., "Won", "Released")
s4: Closed - lost (e.g., "Cancelled", "Lost")
Purpose: Defines which team receives deals when they reach s3 stage
Setup:
Click the pencil icon next to "Next Team"
Select the target team from the dropdown
Select "No Next Team" to end workflow at this team
Click "Save"
Workflow Behavior:
When a deal reaches s3 in the current team, it can be transferred to the next team
This creates automated workflow transitions
Optional: Teams can have no next team (workflow ends there)
How Team Access Works:
Team membership is determined by group matching, not direct assignment
Users belong to teams based on their groups matching the team's access groups
To give a user access to a team, add their group to the team via the "Access Groups" section
Viewing Team Members:
Team members are automatically displayed based on group matching
Shows user avatars, names, and IDs
Members are calculated dynamically from users whose groups match the team's access groups
Purpose: Control which user groups have access to this team and their sharing level
Sharing Policies:
R1 - Restricted: Only deals the user owns are visible + associated accounts
G1 - Group Sharing: All deals from group members + all accounts/contacts
O1 - Open: All deals of the team + all accounts
Managing Access Groups:
Click the "+" icon to add a new group
Select a group from available user groups
Choose a sharing policy (R1, G1, or O1)
Click "Add" to save
Click the trash icon to remove a group
Click the policy badge to change sharing policy
Default Behavior:
If no groups are configured, users with no groups have O1 (Open) access
Purpose: Enables MCP (Model Context Protocol) integration for the team
Operations:
Generate: Create a new API key for the team
Copy: Copy existing API key to clipboard
Regenerate: Create a new API key (invalidates the old one)
Delete: Remove the API key entirely
Usage: API keys are used for MCP server authentication and team-specific data access
Purpose: Enables webform submissions to be associated with this team
Operations:
Generate: Create a new webform API key
Copy: Copy existing webform key to clipboard
Regenerate: Create a new key (invalidates the old one)
Usage: Webform keys allow external forms to submit data directly to this team
Edit Team Name:
Click the pencil icon next to the team name
Enter new name and save
Update Category:
Click the category badge
Select new category from dropdown
Changes take effect immediately
Delete Team:
Click the delete icon (trash)
Confirm deletion
Warning: This action cannot be undone
Team labels are stored in Firebase Firestore under:
{teamId}/labels.json
Each team has its own isolated label collection, allowing complete customization without affecting other teams.
Access label management via the gear icon on the team card.
1. Search Mode (Default)
Search for specific labels by key or value
Edit individual labels by clicking on them
Add new labels via the "+" button
View filtered results with edit capabilities
2. JSON Editor Mode
Edit all labels as a JSON object
Full control over the entire label structure
Syntax validation ensures proper JSON format
Switch between modes using the toggle buttons
Adding Labels:
Click the "+" button in the header
Enter label key (unique identifier)
Enter label value (display text)
Save to add to the team's label collection
Editing Labels:
Search Mode: Click on any label card to edit its value
JSON Mode: Modify the JSON directly in the text editor
Saving Changes:
Click "Save" to persist all changes to Firebase
Changes are immediately available to the team
Other teams are unaffected by your changes
Deal Stage Labels:
s0: Initial stage label
s1: Qualification stage label
s2: Proposal stage label
s3: Negotiation stage label
s4: Closed stage label
Common Labels:
teamMembers: "Team Members"
accessGroups: "Access Groups"
nextTeam: "Next Team"
dealFlowStages: "Deal Flow Stages"
Setting up your organization's workflow is simple and can be modified at any time:
Create teams for each stage of your sales process
Assign appropriate categories (Pre-sales, Sales, After-sales)
Name teams descriptively (e.g., "Lead Qualification", "Proposal Team", "Closing Team")
For each team, click on the deal stage buttons (s0, s1, s2, s3, s4)
Customize the stage labels to match your process
Example: s0="Lead", s1="Qualified", s2="Proposal", s3="Negotiation", s4="Closed"
Click the pencil icon next to "Next Team" for each team
Select which team should receive deals when they reach s3 stage
This creates your workflow: Team A → Team B → Team C
For each team, add access groups via the "Access Groups" section
Assign sharing policies (R1, G1, or O1) to each group
Users with matching groups will automatically have access to the team
Lead Team (Pre-sales) → Sales Team → After-sales Team↓ ↓ ↓s0, s1, s2 s0, s1, s2 s0, s1, s2Next: Sales Next: After Next: NoneGroups: [sales] Groups: [sales] Groups: [support]
Purpose: Synchronize all teams with the latest reference labels
Access: Click the refresh icon (arrows rotate) in the admin header
Process:
Loads reference labels from web/labels.json (or language-specific files)
Compares with each team's current labels
Adds missing labels to teams that don't have them
Preserves existing team customizations
Detects team language from existing labels
Safe Operation: Only adds missing labels, never overwrites existing ones
Result: Shows summary of labels added per team and language statistics
Displays current app version at the bottom of the teams list
Helps with troubleshooting and support requests
Start Simple: Begin with 2-3 teams and expand as needed
Clear Naming: Use descriptive team names that reflect their role
Logical Flow: Design workflow that matches your actual sales process
Category Alignment: Assign categories that match team responsibilities
Test Changes: Workflow modifications are safe and reversible
User Communication: Inform users when workflow changes
Documentation: Keep track of your workflow design decisions
Iterative Improvement: Start with basic workflow and refine over time
Group-Based: Use groups to manage team access, not individual assignments
Sharing Policies: Choose appropriate sharing levels (R1, G1, O1) based on team needs
Security: More restrictive policies (R1) for sensitive teams, open (O1) for collaborative teams
Consistent Naming: Use consistent label keys across teams when appropriate
Descriptive Values: Make label values clear and user-friendly
Regular Updates: Update labels as your process evolves
Backup: The sync function helps maintain consistency across teams
No Data Loss: Changing team configurations doesn't affect existing deals
Reversible: All changes can be undone or modified
User-Friendly: Interface is designed for non-technical users
Real-time: Changes take effect immediately
Label Changes: Only affect display text, not data structure
Team Reorganization: Users and deals remain intact
Workflow Updates: Existing deals continue with their current assignments
Access Group Changes: Users automatically gain/lose access based on group matching
Firebase Storage: All configurations are stored in Firebase
Version Control: App version tracking helps with support
Sync Function: Helps maintain consistency across teams
No Local Dependencies: All data is cloud-based and accessible
Labels Not Updating: Ensure you clicked "Save" in the label management dialog
Users Not Appearing: Check if users have groups that match team access groups
Workflow Not Working: Verify "Next Team" is properly configured
API Key Issues: Regenerate API keys if integration problems occur
Access Problems: Verify user groups match team access groups and sharing policies
Check the app version in the admin view for support requests
Use the sync function to resolve label inconsistencies
Contact your system administrator for team access issues
Review this guide for step-by-step instructions
The Stood CRM Team Management provides powerful yet user-friendly team configuration capabilities. The 4-step workflow setup process is designed to be simple and safe, allowing organizations to:
Create and configure teams with appropriate categories and settings
Customize deal flow stages with team-specific labels
Set up team transitions to create automated workflows
Configure access groups to control team membership and sharing levels
All operations are designed to be easy and harmless, with no risk of data loss or system disruption. Teams can be reorganized, labels can be customized, and workflows can be modified at any time to match your evolving business needs.