[Feature Request] Allow assigning any child node to a user without granting access to the entire parent tree

[maghrebastro-cyber]

Current behavior
Currently, in Nodify Headless CMS, access rights based on nodes only work at the root node level (nodes without a parent).
When a user is assigned a root node, they automatically get access to all sub-nodes and content within that entire tree.

Problem encountered
It is currently impossible to assign a user a single child node (at any depth level) without also giving them access to the parent node and all its other siblings/subtrees.

Use case / Example
I have the following node structure:

text
📁 Blog (root)
├── 📁 Drafts
│ ├── 📄 Article 1
│ └── 📄 Article 2
├── 📁 Published
│ ├── 📄 Article 3
│ └── 📄 Article 4
└── 📁 Restricted
└── 📄 Article 5
I want to give User A access only to Article 2 (inside Drafts) and User B access only to Published.
With the current system, I have to give them access to the entire Blog root node, which exposes all drafts, published, and restricted content.

Expected behavior
It should be possible to assign any node (regardless of its depth or parentage) directly to a user.
The user should then:

Have access only to that specific node and its contents (if it's a container)

Be able to optionally access its children (configurable)

NOT have access to parent nodes, sibling nodes, or unrelated branches

Suggested solution
Modify the permission system to allow node assignment at any level of the tree

When a user is assigned a child node, restrict their navigation/view to only that subtree

Optionally, add a setting to decide whether a user can "climb up" to parent nodes (default: false for child-only assignments)

Benefits
More granular access control

Better support for multi-user workflows (editors, reviewers, contributors)

Allows building collaborative spaces without exposing entire content trees

Additional context
This feature would bring Nodify closer to enterprise-grade permission systems found in other headless CMS solutions (like Strapi, Directus, or Sanio).

Thank you for considering this improvement!

[zimademha-dev]

This is actually a very good idea – and the example you provided is exactly what I would want to do with a blog engine.

I think this evolution would propel Nodify light-years ahead of other Headless CMS solutions.

Right now, most CMS platforms either force you into rigid role-based access or require complex workarounds to achieve granular node-level permissions. Being able to assign any node (at any depth) directly to a user would be a game changer – especially for real-world use cases like:

• Multi-author blogs where each writer only sees their own drafts
• Editorial workflows with reviewers assigned to specific articles
• Client portals where each client accesses only their own content subtree
• Enterprise environments with strict data segregation

This kind of flexible, tree-aware permission system is rare in the headless CMS space. Implementing it would make Nodify stand out as truly innovative, not just another CMS following the same patterns.

I fully support this feature request and hope the team considers prioritizing it.

Thanks again for raising this – it's one of those ideas that makes you wonder why more systems don't work this way already! 🙌

[AZIRARM]

Thanks both for this detailed and thoughtful feedback! 🙌

You're absolutely right — this is an important evolution for Nodify. The ability to assign permissions at any node depth (not just root level) would be a game changer for multi-author blogs, editorial workflows, and client portals.

This feature request is now taken into account.

We'll announce it as soon as it's implemented. Stay tuned!

Thanks again for helping make Nodify better 🚀