Teams, folders, projects

How work is organised — a team holds folders, folders hold projects, and data sources are shared across the whole team.

A team is the top level: members, roles, permissions, billing, and the shared data catalogue all live there. Inside it, folders group projects, and projects hold the actual work.

Text

Team  (members · roles · billing · AI settings)
│
├── Data catalogue          global to the team
│     sources · datasets · mappings
│
└── Folders
    ├── Internal/
    │   ├── Weekly revenue          ← project
    │   └── Dealer performance
    ├── Demos/
    │   └── Customer walkthrough
    ├── Auto dīleriem POC/
    │   └── Campaign attribution
    └── WP testi/
        └── Scratch

Connect a source once, use it anywhere in the team

Sources, datasets, and mappings are team-global. Every project in the team draws from the same catalogue — you never reconnect a database per folder or per project. Access to the data is still granted deliberately; see Roles and permissions.

Teams

A team is a self-contained Chartizer environment. You can belong to more than one, and they share nothing: separate members, separate catalogue, separate billing.

Property	Behaviour
Members and roles	Per team
Data sources and datasets	Global within the team
Billing and plan limits	Per team
AI settings	Per team
Embeds and share links	Issued per team

Two teams means two of everything

A database connected in one team is not visible in another — it must be connected again, with its own credentials, and it counts against that team’s source limit. Split into separate teams only when the separation is genuinely wanted.

Folders

Folders group related projects. They are organisational, not a permission boundary — access is granted on the project inside them.

Good folder	Why
`Internal/`	Recurring dashboards the team maintains
`Demos/`	Shared, external-facing examples
`Auto dīleriem POC/`	One customer engagement
`WP testi/`	Experiments, safe to break

Name folders for the audience, not the author

Demos/ and Internal/ tell everyone what is safe to share. Gustavs stuff/ tells them nothing and outlives whoever made it.

Projects

A project holds the work and is the unit of access.

Item	Description
Charts	Bound to a dataset; refresh when it syncs
Dashboards	Arrangements of charts with shared filters
Files	Uploads, exports, notes attached to the work
Members	People and their roles on this project

Being on the team is not being on the project

Team membership lets you see that a project exists and request access; it does not open it. Each project is granted explicitly, which is what lets a customer engagement sit in the same team as everything else without every member seeing the customer’s data.

Adding data to a project

Open the project, click Add dataset, and pick from the team catalogue. You will only see datasets you personally have access to.

Because the catalogue is team-global, one dataset commonly feeds projects in several folders at once. The dataset’s Projects counter shows that total — which is why it can be higher than the number of projects you can open.

Deleting reaches beyond your folder

Removing a dataset breaks charts in every project reading it across the whole team, not just the folder you are working in. Chartizer names them before you confirm; read that list rather than assuming your own work is the only consumer.

Mode	Who can open	Use for
Private	Named project members	Default
Team	Anyone on the team	Internal dashboards
Link	People an admin approves, one by one	Demos, external stakeholders
Embed	A signed iframe on your site	Customer-facing charts

Link sharing is gated per person

A link does not grant access on its own — each person who opens it is approved individually by a team admin, and forwarding it does not pass access along. Revoke an individual from Share → Access, or invalidate the link entirely with Share → Reset link. See Sharing and embedding.

Moving things

Action	Effect
Move a project between folders	Nothing else changes; access follows the project
Rename a folder	Links to projects inside it keep working
Move a project to another team	Rebuilt from scratch — the new team’s catalogue has different datasets

Moving between teams is not a move

Teams share no catalogue, so a project’s charts have nothing to bind to in the destination. In practice you recreate the work against that team’s own datasets. Plan folder structure within a team rather than splitting work across teams you will later want to merge.

Recent files

Recent files in the sidebar is a cross-folder view of everything you opened or edited, newest first — it ignores the folder structure and is scoped to you, not shared.