> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nexalytica.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How Nexalytica Is Organised: Orgs, Depts & Resources

> Learn how Nexalytica structures your workspace into Organisations, Departments, and Resources — and how ownership and visibility work.

Nexalytica organises everything you work with into a clear three-level hierarchy: your **Organisation** sits at the top, **Departments** group people and work into teams, and **Resources** are the individual items — dashboards, data sources, chats, agents, files, and folders — that you create and share every day. Understanding this structure helps you know where things live, who can see them, and how to keep your workspace tidy as your team grows.

## The Three-Level Hierarchy

<Steps>
  <Step title="Organisation">
    Your Organisation is the top-level container — think of it as your company or tenant inside Nexalytica. It has a name, a URL slug, a description, and a logo, plus company-wide settings such as the external sharing toggle. The person who creates the Organisation becomes its permanent **Owner** and cannot be removed or demoted.
  </Step>

  <Step title="Department">
    Departments sit inside your Organisation and represent teams or divisions. Each Department has a name, a description, and a colour to make it easy to identify at a glance. Most resources are scoped to a Department, so members always know which team's work they're looking at.
  </Step>

  <Step title="Resource">
    Resources are the building blocks you work with directly. Every resource belongs to a Department and is created and owned by a specific person.

    <CardGroup cols={3}>
      <Card title="Dashboards" icon="chart-bar">
        Visual analytics views built from your connected data.
      </Card>

      <Card title="Data Sources" icon="database">
        Connections to the underlying datasets powering your dashboards.
      </Card>

      <Card title="Chats" icon="message">
        AI-powered conversation threads for exploring your data.
      </Card>

      <Card title="Agents" icon="robot">
        Automated AI workers you configure to run recurring tasks.
      </Card>

      <Card title="Files" icon="file">
        Documents and data files uploaded into your workspace.
      </Card>

      <Card title="Folders" icon="folder">
        Containers for organising files and other resources.
      </Card>
    </CardGroup>
  </Step>
</Steps>

## Creator vs. Owner

Every resource records two distinct people: its **creator** and its **owner**.

| Role        | What it means                                                     | Can it change?                                       |
| ----------- | ----------------------------------------------------------------- | ---------------------------------------------------- |
| **Creator** | The person who originally created the resource                    | Never — permanently fixed at creation                |
| **Owner**   | The person who currently controls sharing, deletion, and transfer | Yes — ownership can be transferred to another person |

When you create a resource, you start as both creator and owner simultaneously. The two roles only diverge if you — or an Org Admin — later transfer ownership to someone else. The creator field is a permanent audit record; the owner field represents current accountability.

<Note>
  Even after transferring ownership, the original creator's name remains on the resource. This is intentional — Nexalytica preserves a full lineage so you always know who first built something.
</Note>

## Private by Default

Every resource you create is **private** the moment it exists. Only you (as the owner) and anyone you explicitly share it with can see it. Nothing is ever visible to your whole Department or Organisation automatically.

<Warning>
  Do not assume that placing a resource inside a Department makes it visible to Department members. You must share it explicitly — the Department just determines where the resource is scoped, not who can see it.
</Warning>

This default protects sensitive work-in-progress. When you are ready to collaborate, use the **Share** button on any resource to grant access to specific people, a Department, or your whole Organisation.

## The Tabbed Workspace

Nexalytica presents your open resources as **tabs**, similar to a browser. You can have multiple dashboards, data sources, or chats open at the same time without losing your place.

<Tip>
  To open a resource in a **background tab** without switching to it immediately, use **Cmd-click** (macOS) or **Ctrl-click** (Windows/Linux), or click with your **middle mouse button**. This lets you queue up several resources to review without interrupting your current view.
</Tip>

## Who Can Create Resources

<Tabs>
  <Tab title="Org Owner & Org Admin">
    Org Owners and Org Admins can create resources inside any Department in the Organisation.
  </Tab>

  <Tab title="Dept Admin & Dept Manager">
    Department Admins and Managers can create resources inside any Department they belong to.
  </Tab>

  <Tab title="Employee">
    Employees (the base working role) can create and own resources, but only **inside a Department they are a member of**. If you are not yet a member of any Department, ask your Org Admin or Dept Admin to add you.
  </Tab>
</Tabs>

<Info>
  All roles — Owner, Admin, and every Department role — use the same Organisations → Departments → Resources building blocks. The difference is in what each role can manage, not in how the structure itself is laid out. See [Roles & Permissions](/concepts/roles-permissions) for the full breakdown.
</Info>
