You see the error message “Database Cannot Be Locked” when a workspace member with a specific role tries to lock a database. This error occurs because Notion restricts the lock operation based on the member’s permission level, not because of a bug or corrupt database. This article explains exactly which roles can lock a database, why the error appears for other roles, and the precise steps to fix the problem by adjusting the member’s role or using an alternative locking method.
Key Takeaways: Locking a Notion Database Based on Member Roles
- Settings & Members > People > Change Role: Only Full Access members and workspace Owners can lock a database. Guests and Members with restricted permissions cannot.
- Database lock button (three-dot menu > Lock Database): This button is hidden or grayed out for roles that lack permission to lock. The error appears when a user without the required role attempts the action.
- Alternative: Duplicate database with locked views: If you cannot change the member’s role, create a duplicate database and lock only the views instead of the entire database.
Why Notion Shows “Database Cannot Be Locked” for Certain Roles
Notion enforces a strict permission hierarchy for database locking. The lock feature prevents any user from editing the database schema — adding, renaming, or deleting properties. Only workspace Owners and members with Full Access permission can lock a database. This is a security measure designed to protect database structure from accidental or unauthorized changes.
When a Guest or a workspace Member with a role below Full Access clicks the Lock Database option, Notion immediately blocks the action and displays the “Database Cannot Be Locked” error. The system checks the user’s role against the database’s permission settings before applying the lock. If the role does not include the “Edit database” permission at the Full Access level, the lock fails.
The error is not caused by a corrupt database, a sync delay, or a bug. It is a direct result of the user’s permission level. The fix requires either upgrading the user’s role or using an alternative approach that does not require full database lock.
Steps to Resolve the Lock Error by Adjusting Member Roles
The most direct fix is to change the member’s role to Full Access or Owner. Follow these steps exactly.
- Navigate to Settings & Members
Open your Notion workspace. In the left sidebar, select Settings & Members. This opens the workspace settings panel. - Open the People tab
In the Settings panel, click the People tab. You will see a list of all workspace members and their current roles. - Locate the affected member
Find the member who sees the “Database Cannot Be Locked” error. Their current role is shown next to their name, such as Guest, Member, or Full Access. - Change the role to Full Access
Click the dropdown next to the member’s name and select Full Access. If you are the workspace Owner, you can also promote the member to Owner, but this grants full control over the workspace. - Ask the member to lock the database
After the role change, the member should navigate to the database they want to lock. Click the three-dot menu at the top-right of the database view. Select Lock Database from the menu. The lock should apply immediately without the error.
Alternative Method: Lock Database Views Instead of the Entire Database
If you cannot change the member’s role due to workspace policies, you can lock individual database views instead of the whole database. This approach does not require Full Access permission and prevents view configuration changes.
- Open the database view
Go to the database and select the specific view you want to lock, such as Table View or Board View. - Access the view settings
Click the three-dot menu at the top-right of the view. This menu contains options specific to that view. - Select Lock View
In the dropdown menu, click Lock View. This locks only the view’s layout, filters, and sort order. The database schema remains editable by anyone with edit permission. - Repeat for additional views
If the database has multiple views, repeat steps 1 through 3 for each view you want to protect. The lock applies per view, not globally.
If the Error Persists After Role Change
Database is already locked by another user
If a Full Access member or Owner has already locked the database, other members cannot unlock or relock it. The lock is a toggle: only one user can apply or remove it. Check the database’s three-dot menu — if Lock Database is replaced by Unlock Database, the database is already locked. No further action is needed.
Workspace is in read-only mode
If the entire workspace is in read-only mode due to a billing issue or an admin setting, no member can lock any database. Verify the workspace status in Settings & Members > Workspace. If the workspace is read-only, resolve the billing or admin restriction first.
Guest role cannot lock any database
Guests never have the ability to lock a database, regardless of the database’s permission settings. The only way for a Guest to lock a database is to change the Guest to a Full Access member. If this is not possible, the Guest must rely on view locking instead.
| Item | Full Access / Owner | Member (below Full Access) / Guest |
|---|---|---|
| Can lock the entire database | Yes | No |
| Can lock individual views | Yes | Yes |
| Sees the “Database Cannot Be Locked” error | No | Yes |
| Can unlock a previously locked database | Yes | No |
Now you understand why the “Database Cannot Be Locked” error appears for members with specific roles. To resolve it, change the member’s role to Full Access in Settings & Members > People, or lock individual views as a workaround. Remember that view locking is available to all members with edit permission and does not require a role upgrade. For workspace Owners, always verify the current lock status before assigning new roles.