website logo
ChartHop documentation
Carrot reference
Release notes
Navigate through spaces
ChartHop documentation
Carrot reference
Release notes
⌘K
Welcome
Welcome to ChartHop documentationšŸš€
Available ChartHop packages
Getting Started
ChartHop Video Library
Navigating ChartHop
ChartHop terminology
Markdown formatting
Filtering data
Home page
Visualizing your organization
Org Chart
Map
Data Sheet
Employee Profiles
Setting up ChartHop
Creating your ChartHop org
Importing spreadsheet data
Configuring your Org settings
User management
Permissions and security
Creating and managing groups
Customizing ChartHop
Forms
Fields
Customizing employee profiles
Document templates
ChartHop apps and bundles
ChartHop apps
ChartHop bundles
Performance management
Performance reviews
Org management
About org management
Working with jobs
Working with people
Working with job history
Announcing org changes
Planning
Scenarios
Headcount planning
Compensation reviews
Legacy compensation reviews
Compensation bands
Viewing your people data
ChartHop reports
Partners
Sequoia getting started
Accessing ChartHop as a Sequoia customer
ChartHop first run guide for Sequoia customers
ChartHop features available to Sequoia customers
Troubleshooting common sync errors
Developers
ChartHop connect
Developer basics
Events
Syncing data to/from ChartHop
Resources
ChartHop Standard Terms and Conditions
ChartHop Basic Agreement
Data Processing Addendum
Privacy policy
Security statement
Subprocessors
FAQ
Docs powered byĀ archbeeĀ 

Group names and aliases

Packages: Basic | Standard | Premium

Groups are how you identify groupings or divisions of your organization. For example, you create a group to represent a department.

Group names

You can use a group name to uniquely identify a department, team, or location. Group names are unique identifiers and may only be used once in your organization.

Group aliases

You can use group aliases to consolidate multiple group names into a single group. When group names change such as a department being renamed, you can create an alias for a group that encompasses the old names and still lets you maintain historical data.

Group aliases are also helpful to help you consolidate different department names used in your payroll system. For example, your payroll system may use "customer success", "CS", and "customer service" to refer to the same department. With ChartHop, you can set up a group alias that combines these group names into a single department. For example, you can create a department called Customer Sucess and add two aliases to that department. In this case, a person or job that is assigned to "CS" or "customer service" in your payroll system will be a part of the "customer success" department in ChartHop. This helps you eliminate "extra" groups in your org chart without needing to update your payroll system.

Create aliases to map like-named departments to the same department.
Create aliases to map like-named departments to the same department.

If you use a term as an alias, you cannot also use it as a group name.

Differences between Parent groups and aliases

Parent groups are specifically used to organize child groups according to your organization's structure in ChartHop. Aliases, however, are best used as tie-ins to the department names used in your payroll system and ATS.

For example, in your payroll system, you could have a department named "Support", while in ChartHop that same department could be referred as "Customer Support".

Updated 23 Nov 2022
Did this page help you?
Yes
No
UP NEXT
Departments
Docs powered byĀ archbeeĀ 
TABLE OF CONTENTS
Group names
Group aliases
Differences between Parent groups and aliases