Departments help you organize your company's structure inside Fabritec.They group users into organizational units, identify department managers, and establish parent-child relationships between teams. These relationships form the department hierarchy used by the default task-assignment rules.Use the Departments page to review team membership, maintain reporting lines, and keep your organizational structure aligned with how your company works.
Where to Find Departments#
User Management → DepartmentsThe page provides two views:| View | Purpose |
|---|
| List | Review departments in a table, check their managers and users, and access editing and deletion actions. |
| Hierarchy | Review departments as an organizational tree showing parent-child relationships. |
Use List and Hierarchy in the upper-right corner to switch between the views. Add Department is available beside these controls.
List View#
The List view displays department information in a table.Table Columns#
| Column | Description |
|---|
| Name | The department's name. |
| Manager | The manager associated with the department, when configured. |
| Parent Department | The department directly above this department in the hierarchy. A department without a parent is a top-level department. |
| Users | User icons associated with the department. |
| Actions | The Edit pencil icon and Delete trash icon. |
Understanding the Users Column#
User icons let you review department membership from the list.When there are more users than the individually displayed icons, an additional indicator appears. For example, +3 represents three additional users beyond the icons shown; it is not the number of child departments.A dash appears where no users are shown.Manager and Parent Department Are Different#
Manager identifies a person associated with managing the department. Parent Department identifies another organizational unit above it.For example, Production Department can be the parent of Maintenance. The person managing Maintenance is a separate detail shown in Manager when configured.A blank Manager cell means that no manager is displayed in that row.Search, Filters, and Table Controls#
| Control | How to Use It |
|---|
| Search | Enter text, such as a department name, to find relevant departments. |
| Column filters | Use the filter icons in Name, Manager, or Parent Department to narrow the list. |
| Clear filter | Remove applied table filters. |
| Columns | Choose which table columns to display. |
| Excel Export | Export department data to Excel. |
| PDF Export | Export department data to PDF. |
| Items per page | Choose how many departments to display on each page. |
| Page navigation | Move between pages when the list spans more than one page. |
For example, use the Parent Department filter to find departments directly linked to a particular parent.To return to a broader list, clear the search text and use Clear filter to remove the applied column filters.The toolbar also includes Reset cache.
Hierarchy View#
Click Hierarchy to view the organizational tree.Each department appears as a card. Connecting lines show the relationship between a parent department and its children.Use this view to check which departments report to another department and whether the structure matches your intended reporting lines.Understanding the Hierarchy#
| Term | Meaning |
|---|
| Top-level department | A department with no parent selected. |
| Parent department | The department directly above another department. |
| Child department | A department linked beneath a selected parent. |
The Parent Department value in List view corresponds to the connection shown in Hierarchy view.To change a relationship, return to List, edit the department, and update Parent Department.Example Relationships#
Selected relationships in the illustrated hierarchy are:| Department | Parent Department |
|---|
| Projects Department | None — top-level department |
| Production Department | Projects Department |
| Maintenance | Production Department |
| Quality Control Department | Projects Department |
| Welding Department | Quality Control Department |
| Planning Department | Projects Department |
| Sales / Business Development | Planning Department |
| Shipping Department | Projects Department |
For example, Maintenance is directly beneath Production Department, while Welding Department is directly beneath Quality Control Department.These are example relationships from the illustrated configuration, not a required structure for every company. Select parents that match your organization's reporting lines.Why Hierarchy Matters#
The hierarchy provides the organizational structure used by default task assignment. A user's department and its position in the hierarchy help determine the available assignment flow.Review the task-assignment implications before changing a department's parent. The default rules and the need to check explicit assignment permissions are described in Task Assignment Rules below.
Add a New Department#
Click Add Department to create an organizational unit.Complete the following fields.Department Name — Required#
Enter a clear name that identifies the department.Examples include Production Department, Quality Control Department, Planning Department, and Maintenance.Before creating a department, search the list to check whether the same team already exists under a similar name.Parent Department — Optional#
Select a parent department to place the new department beneath it in the hierarchy.| Selection | Result |
|---|
| A parent is selected | The new department appears as a child of that parent in Hierarchy view. The selected parent is also shown in the Parent Department column. |
| No parent is selected | The new department is created at the top level. |
For example, when setting up Maintenance beneath Production Department, select Production Department as its parent.Choose the parent based on the intended reporting relationship, and review the resulting task-assignment flow.
Save the Department#
Review the department name and parent selection, then click Add.After successful creation, the department appears in List view, is reflected in Hierarchy view, and becomes available for user assignment.Check its Parent Department value in the list, then switch to Hierarchy to confirm that it appears in the intended position.Creating a department and assigning users to it are separate steps. Add the department first, then assign users through the Users page.
Editing or Deleting a Department#
Use the controls in the department's Actions column in List view.Edit a Department#
1.
Find the department and click its pencil icon.
2.
Update the department name or Parent Department as required.
4.
Review the updated row and switch to Hierarchy to check the relationship.
Changing the parent changes the department's position in the organizational structure. Review the affected teams and their task-assignment needs before reorganizing the hierarchy.Delete a Department#
Click the department's trash icon to remove a department that is no longer needed.Deletion may be restricted when users are assigned to the department or when it contains child departments.Before deleting, review the Users column and check for child departments in Hierarchy view. Reassign users or update the parent relationships of child departments where required.If Fabritec prevents deletion, review the displayed message and resolve the stated dependency before trying again.Important: Review membership and hierarchy relationships before deleting a department. Do not assume that deleting it will automatically place its users or child departments in an appropriate replacement department.
Assigning Users to Departments#
Users are assigned to departments through:Create or edit the relevant user account, select its Department, and save the user record.Return to User Management → Departments → List to review the user icons associated with the department.A user's department places them within the organizational structure and is used by the default task-assignment rules. Review department assignments when users move between teams or their responsibilities change.Departments and Roles#
Department identifies the user's organizational membership. Role defines the system permissions assigned to the user.Review both when setting up an account. A position in the department hierarchy is not a substitute for reviewing the user's role permissions.
Task Assignment Rules#
Department hierarchy supports a structured default assignment flow.The default rules described for department-based task assignment are:| Target User's Department | Default Rule |
|---|
| The user's own department | Tasks can be assigned within the department. |
| A department below the user's department in the hierarchy | Tasks can be assigned down the hierarchy. |
| A department above the user's department in the hierarchy | Upward assignment requires explicit permission. |
Assignments to Other Departments at the Same Level#
Check the configured task-assignment permissions before assuming that users in different departments at the same hierarchy level can assign tasks to one another.The hierarchy diagram shows organizational relationships; it does not show the full assignment permissions configured for an individual user.Example Using the Illustrated Hierarchy#
Under the documented downward-assignment rule, users in Projects Department can assign tasks to users in departments below it, such as Production Department and Planning Department.Users in Production Department can assign tasks to Maintenance, while users in Quality Control Department can assign tasks to Welding Department in this configuration.A user in Maintenance does not have default upward-assignment access to Production Department or Projects Department without explicit permission.When an intended recipient is unavailable, ask an authorized administrator to review the user's department, the parent-child relationships, and the applicable task-assignment permissions.
Best Practices#
Plan the Structure Before Creating Departments#
Identify the main departments and their reporting relationships before adding them. Keep the hierarchy logical and avoid unnecessary levels.Use Parent Department to reflect your actual structure rather than copying an example that does not match your organization.Use Consistent Names#
Choose names that are easy to distinguish and recognize. Check for existing entries before adding a department so that one team is not unintentionally represented by several similarly named departments.Review Membership and Assignment Flow Together#
Review the department's users, manager information, and parent relationship when responsibilities change.Before moving a department, check the expected task-assignment flow with the affected teams. Review explicit assignment permissions rather than assuming that chart position explains every user's access.Check Both Views After Structural Changes#
Use List to review department details and Hierarchy to confirm the reporting structure.Review the structure periodically as teams grow, and resolve user assignments and child-department relationships before removing obsolete departments.#
🔗 Related Articles#
Modified at 2026-09-16 08:25:02