📝 Overview
Database permissions in Yoom are valid only within the target database. These permissions are useful when you want to:
Grant access to specific users for individual databases
Invite guests to a particular database.
For more information about inviting guests, check the guide here.
🔒 How Database Permissions Work
1️⃣ If no specific database permissions are set:
The database will inherit permissions from the project tt belongs to.
🔗 Project Permissions - View Guide Here
2️⃣ If individual database permissions are configured:
These permissions will override project permissions for that specific database.
This allows for more precise control over who can access or edit certain databases.
⚖️ Types of Database Permissions
There are three types of database permissions:
| Edit | View | No Permission |
Database | Edit | View only | No access |
Record | Create, Edit, Delete | View only | No access |
Table | Create, Edit, Delete | View only | No access |
View | Create, Edit, Delete | View only | No access |
CSV Import / Download | Allowed | Not allowed | Now allowed |
Data Connect | Create, Edit, Update, Delete | View & Update retrieved data only | No access |
Flowbot | Based on project permissions | Based on project permissions | No access |
Granting Permissions | Allowed | Not allowed | Now allowed |
‼️ Key Notes:
No Database Permissions?
Even if a user has project-level permissions, they cannot view or edit the database if "No Permission" is set at the database level.
Same Permissions for Project & Database
If both the project and the database have identical permissions, the user will have the same level of access as defined by the project.
Related Keywords
Related Keywords
Settings, workspace, permissions, database access, role management, permissions, change