Teams Settings is a powerful tool for organizations, giving administrators the flexibility to manage recruitment across multiple brands or divisions from a single platform. Teams admins can modify the teams hierarchy and assign any user to any team.
Steps for Teams Administrator
Manage Teams hierarchy
2. Assign each user to their designated team
Team Settings
The Teams administrator can configure various settings for the created teams through the Teams menu. In the team settings view, it is possible to modify the team's basic information and brand settings, which are added to the default domain via the Organization Settings menu.
If additional domains (hostnames) have been saved to the instance with the help of Teamdash support, team preferences can be set through the resulting dropdown menu.
Preferences set under team settings are applied when publishing job postings within the team's project, in the recruiter's email footer, and in the landing page address.
Publishing a job ad
If there are different teams within the instance with various settings, all information is inherited based on the project.
For example, if a recruiter from Team Brand1 creates a project and its landing page, the domain choice depends on the project's designated settings.
In the process of publishing a selection is made to determine which domain will be used for the active landing page:
If a recruiter does not make a selection in the Review panel for the project (Choose project), the landing page will be created with the default domain.
If a recruiter selects a public project (without belonging to a specific team) in the Review panel, the landing page will be created with the default domain.
When a recruiter changes the value in the Choose Project field in the Edit Landing Page view, the landing page URL updates according to the preference made.
In the Job Ads list, the Project column shows the affiliation of the landing page with the associated project. The visibility of landing pages depends on access rights granted through teams.
Team members
A member belonging to a team can:
create projects under the team they belong to
For example, a user with group-level access can create both public projects and projects under a specific team.
Only members belonging to a specific team can create public projects or projects exclusive to their own team
Please contact [email protected] for assistance with team settings. Enabling this feature involves preparation by a Customer Success Manager and setup beforehand.