Bases Read Only helps you guard chosen Bases views against accidental edits

Lock supported controls in a saved base.

MIT · no telemetry · core features free

Six sample projects in a locked table with the desktop lock badge.
Open larger
version
1.1.0
released
downloads
43
review
Passed
health
Excellent
license
MIT
listed for
Desktop, Mobile
obsidian
1.13.4 or later

App tests used macOS with a local sponsorship reply. Real iOS and Android touch interactions were not tested.

Directory facts fetched from community.obsidian.md/users/theluckystrike.

About Bases Read Only

You want to guard chosen Bases views against accidental edits in your vault.

Lock your saved base before reading a project table or showing it to someone. Bases Read Only guards supported cell edits and hides controls that change the view. Your linked notes remain available.

A sample project table changes from unlocked to locked, then shows two separate embeds.Play demo

Free features

A lock for each base file

Run Toggle lock for current base or use the file menu. The desktop badge shows the lock, and saved manual paths follow file moves.

Read cells without an accidental edit

Locked cells block typing, paste, checkbox toggles and supported edit keys. Copy shortcuts, scrolling and navigation remain available.

The separate unlocked scratch base retains its normal toolbar and editable cells.
Open larger

Links and separate embeds

File and property links can open notes from a locked base. Separate saved base embeds keep their own lock states within one editable note.

A weekly review contains a locked project base and a separate unlocked scratch base.
Open larger

Keep cards and view controls fixed

Locked views block supported card and column drag starts. Mutable toolbar controls disappear, while the saved-view switcher stays visible.

Six project cards in a locked base with its view-switch menu visible.
Open larger

Pro features

Pro costs $5 a month or $15 one time through GitHub Sponsors. One sponsorship turns on Pro in every plugin that has it.

Folder and glob rules Pro

Pro locks matching saved base paths using folder or glob rules. Rules are case sensitive, and a matching rule can retain the lock.

Plugin options show the Archive rule and the GitHub Sponsors status with a local sponsor reply.
Open larger

Editable properties Pro

Pro lets named properties remain editable when the rendered cell exposes a known property ID. Unknown cells stay locked, and drag guards remain active.

The project table stays locked while its done checkbox has a Pro edit exception.
Open larger

Kiosk mode Pro

Pro kiosk mode locks saved base files, including later files. Turning it off leaves manual locks in place.

The scratch base is locked by kiosk mode with its mutable toolbar controls hidden.
Open larger

Set up Bases Read Only

needs

  • Obsidian 1.13.4 or later
  • The core plugin Bases, turned on

steps

  1. Create your base and configure its saved views.

  2. Open the .base file in a tab.

  3. Run Toggle lock for current base and check the desktop badge.

  4. Follow file links to read the underlying notes.

If the app can't find a new plugin yet, try again later. Obsidian says a plugin that passes the review shows in the app within 24 hours.

How to lock Obsidian Bases against accidental edits

Known limits of Bases Read Only

  • The lock guards supported interface controls and does not set file permissions.
  • Inline fenced base blocks are outside the lock scope.
  • Bases DOM classes can change with an Obsidian update and require new selectors.
  • Editable property exceptions need a known property ID; otherwise the cell stays locked.
  • Native Kanban requires Obsidian 1.14 or later; third-party kanban layouts were not tested.
  • Real mobile touch interactions, pop-out windows, custom themes and sync between devices were not tested.

Need a change for your team? I build custom Obsidian plugins and features.

Questions about Bases Read Only

Does this set file permissions?

The lock guards the Obsidian interface. A note editor, sync service or another plugin can still change the files.

Why does a base stay locked?

A Pro rule or kiosk mode can keep it locked after you remove its manual lock. Check those settings before editing.

Can I lock a fenced base block?

Inline fenced base blocks have no source file path. They are outside this lock scope.

What happens when Pro turns off?

Manual locks continue to work. Saved rules and property exceptions remain stored, but the free guard ignores them.

Network use

After you select Sign in with GitHub, the plugin sends its client ID, read:user scope and device-flow requests to github.com. Due checks and Refresh send your token to api.github.com to read your sponsorship tier and total payment. No note text, filenames or other vault data goes to either host.

Read the full network disclosure

Questions or ideas?

Tell me what is broken in Bases Read Only, or what it should do next.

Send feedback

Bases Read Only 1.1.0, MIT license

MIT · no telemetry · core features free