# Crudy Connected Apps  How It Works With Team Management and Roles

> How Crudy connects to the rest of NIZU Cloud: it uses your Team Management members and teams for per-connection access, your roles and permissions to control what each user can do, and your workspace…

- Page: https://dashboard.nizu.io/knowledge_base/view/153-crudy-connected-apps-how-it-works-with-team-management-and-roles
- Part of: [Knowledge base](https://dashboard.nizu.io/knowledge_base/llms.txt) on NIZU — https://dashboard.nizu.io/llms.txt
- Updated: 2026-10-25T11:50:03Z

## Crudy and connected NIZU modules

Crudy is a self-contained database tool it does not push or pull business records into Projects, Invoicing or Tasks. Instead, it connects to the parts of NIZU Cloud that govern **who** can use it and **what** they are allowed to do, so it fits naturally into the access model you already manage.

### Team Management (members & teams)

Each Crudy connection can be scoped to specific people. When you set a connection's **Access**, you pick from your existing NIZU **teams** and **members** the same directory used across the workspace. You can open a connection to all team members or restrict it to chosen teams and individuals. Administrators always have access, and clients are excluded from Crudy entirely.

### Roles & permissions

What a user can do in Crudy is governed by your workspace roles and permissions. Crudy adds its own permission set so you can grant capabilities independently per role:

- **Browse databases (read)** open connections and view records.
- **Create / Update / Delete records** make changes to data.
- **View the audit log** review who changed what.
- **View the trash** and **Restore trashed records** see and recover deleted rows.
- **Manage connections & settings** add connections, install agents, and configure Crudy.

This lets you, for example, give support staff read-only browsing while reserving editing and connection management for developers and administrators.

### Workspace identity & the audit log

Every action in Crudy is attributed to the signed-in NIZU user. The audit log, trash and error log all record the member who performed each insert, update, delete or restore, using your workspace identity so accountability lines up with the same people directory as the rest of NIZU.

### Your external databases

The one external system Crudy connects to is **your own MySQL or MariaDB database**, through the agent you install on its server. That database is not a NIZU module it is your data, kept on your infrastructure. Crudy simply gives your workspace a secure, audited window into it.

### Frequently asked questions

#### Does Crudy share data with Projects, Invoicing or other NIZU modules?

No. Crudy browses your external databases. It uses NIZU only for access control (teams, members, roles) and identity (the audit log).

#### Can clients use Crudy?

No. Crudy is for internal team members; clients are excluded.

#### How do I give a teammate access to one specific database only?

Scope that connection's Access to the right team or member, and grant them the Crudy browse permission in their role. Other connections remain hidden from them.