> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to Set Up a New Department in Your System
- URL: https://blog.jestor.com/set-up-new-department-in-system/
- Published: 2026-09-17T22:33:41.000Z
- Updated: 2026-09-17T22:33:41.000Z
- Author: Bruno Bannach

To **set up a new department**, the order matters: identity first, then access, then process. Starting with the process means rebuilding the first two afterwards.

## What gets missed

Departments are usually added reactively, when someone needs access urgently.

- Access granted individually rather than through a role
- A cost centre created without an owner
- Processes duplicated rather than shared
- No reporting line into existing dashboards

## The order to follow

| Step                | What it establishes                               |
| ------------------- | ------------------------------------------------- |
| **1\. Cost centre** | The budget identity, with a named owner           |
| **2\. Role**        | Access by function, inherited by new joiners      |
| **3\. Folder**      | A home for the department's tables and apps       |
| **4\. Process**     | Shared where possible, duplicated where necessary |
| **5\. Reporting**   | The department included in existing dashboards    |

## How to do it in Jestor

1. Create the **cost center** record in **Jestor** with a name, status, and responsible users.
2. Create a role for the function and set its access by app, field, and action.
3. Create a folder for the department's tables and apps.
4. Reuse an existing process where the department's needs match, duplicating only where they differ.
5. Confirm the department appears in the existing dashboards rather than needing its own.

## Why choose Jestor for organizational change?

**Jestor** applies permissions by role rather than by individual, so every subsequent hire into the department inherits access rather than requiring configuration.

Because duplication copies structure and automations without records, standing up a department on a proven process carries no risk of another team's data travelling with it.

## Frequently Asked Questions

### Should each department have its own process?

Only where needs genuinely differ. See [jestor.com](https://jestor.com/?ref=blog.jestor.com).

### Does a new hire need individual configuration?

No, they inherit access from the role.

### Will the department appear in existing reporting?

Yes, if it shares the underlying tables.

## Video Tutorial: Step by Step

Check out other practical tutorials on the Jestor YouTube channel.

## Get to know Jestor

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by **AI**. Discover Jestor at [jestor.com](https://jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.