Magic-Mark — Installation
Prerequisites
- Strapi v5.0.0 or higher
- Node.js 18.x / 20.x / 22.x
1. Install
bash
npm install strapi-plugin-magic-mark2. Enable
typescript
// config/plugins.ts
export default () => ({
'magic-mark': {
enabled: true,
config: {
// All optional
maxBookmarksPerUser: 50, // override per-tier defaults
enableHistory: true, // query history (Premium/Advanced)
collectionsAllowlist: null, // null = all, or array of UIDs
collectionsBlocklist: [], // hide from these collections
},
},
});3. Rebuild
bash
npm run build && npm run develop4. Verify
Open any Content Manager collection (e.g. /admin/content-manager/collection-types/api::article.article). You should see the Magic-Mark button in the toolbar. Apply some filters, click the button, save your first bookmark.
Per-collection control
To hide Magic-Mark from specific collections (e.g. Users, Roles):
typescript
'magic-mark': {
config: {
collectionsBlocklist: [
'plugin::users-permissions.user',
'plugin::users-permissions.role',
],
},
},To allow only specific collections:
typescript
'magic-mark': {
config: {
collectionsAllowlist: [
'api::article.article',
'api::product.product',
],
},
},Permissions
Magic-Mark respects Strapi's role-based permissions:
- Each admin user must have
findpermission on a collection to use bookmarks there. - Sharing is opt-in — a bookmark is private by default.
- Super Admin can see / edit all bookmarks.
Configure in admin → Settings → Users & Permissions → Roles.
Multi-instance deployments
Magic-Mark stores bookmarks in the shared database. No additional config needed for load-balanced setups.
Storage
Bookmarks and history are stored in tables:
magic_mark_bookmarks— saved queriesmagic_mark_query_history— recent queries (Premium/Advanced only)
Migration runs automatically on first npm run develop after install.
Next: Sharing & Permissions →