Overview
Understanding teams and their implementation in the Thena platform
Teams in the Thena platform provide a structured way to organize members, manage workflows, and handle ticket routing within your organization. They serve as the primary unit for work distribution and collaboration.
Teams can be organized hierarchically, allowing for parent-child relationships that reflect your organizational structure. A member can belong to multiple teams, each with specific roles and responsibilities.
What is a team?
A team in Thena Platform represents a group of members who:
- Work together on specific projects or areas
- Share common workflows and processes
- Handle related tickets and tasks
- Have defined roles and permissions
Team structure
Team hierarchy
Parent teams
• Department level teams
• Broad responsibility areas
• Cross-functional groups
• Regional divisions
Sub teams
• Specialized units
• Project teams
• Product teams
• Support tiers
Team types
Public teams
• Visible to all organization members
• Open for viewing and joining requests
• Transparent workflows
Private teams
• Limited visibility
• Invitation-only membership
• Protected resources
Team settings
Basic configuration
Member management
Roles
• Team Admin: Full team control
• Team Lead: Operational management
• Member: Standard access
• Observer: Read-only access
Permissions
• Ticket management
• Resource access
• Configuration rights
• Member management
Best practices
Team setup
- Define clear team purpose
- Establish team hierarchy
- Set up access controls
- Configure routing rules
Member management
- Define role responsibilities
- Document access levels
- Set up onboarding process
- Maintain member roster
Operations
- Regular team reviews
- Performance monitoring
- Process documentation
- Resource allocation
API endpoints
Sample team
When creating a team, the system will add additional fields in the response such as uid
, organizationId
, createdAt
, updatedAt
, isActive
, and memberCount
.