Skip to main content

Team - Employee relationship workflow

Only administrators have the ability to manage teams. This includes:

  • Creating new teams (e.g., "Marketing", "Backend", "Customer Success")
    ​

  • Editing existing team names and details
    ​

  • Deleting teams no longer in use
    ​


Assigning Employees to Teams

  • An employee can be assigned to one or multiple teams.
    This allows flexible grouping for employees working across departments or on cross-functional initiatives.
    ​

  • Admins can manage team membership at any time when adding or editing an employee.
    ​

  • When assigned to multiple teams, the employee will appear in each team's overview and calendar.
    ​


Approval Flow Considerations

Although an employee may belong to multiple teams, they can only have one active approval flow assigned to their absence requests.

This means:

  • Approval responsibility does not change based on which team the absence originates from.
    ​

  • The approval chain is configured per employee, not per team.
    ​

Example:

John Smith is part of both the Design Team and the Frontend Team.

His assigned approval flow routes requests through the Design Team Lead.

Even if his time off affects a project in the Frontend Team, the Design Team Lead is still the one responsible for approval.


Best Practices

  • Clearly define approval flows when onboarding employees who belong to multiple teams.
    ​

  • Assign team membership based on visibility and collaboration needs — not approval logic.
    ​

  • Keep team structures lean and relevant to avoid confusion in calendars and reporting.

Did this answer your question?