Granular user permissions (folder- and template-level access control)
under review
L
Lucas Laguens
Currently, access control in Stripo is limited to the project level, meaning that any user with access to a project can view and edit all templates within it.
For organizations operating with multiple teams (e.g., Marketing, CRM, Finance, Logistics), this creates significant governance and operational challenges, especially when templates from different departments are stored within the same project.
Use case
In our setup, several teams share a Stripo environment:
• Each team owns a distinct set of templates
• However, all templates must currently sit within the same project for operational reasons
This leads to:
• Risk of accidental edits or deletions across teams
• Lack of clear ownership boundaries
• Increased need for manual coordination and oversight
Requested improvement
Introduce granular access control within projects, such as:
• Folder-level permissions (e.g., users can only access specific folders)
• Template-level permissions (restrict visibility/editing per template)
• Role-based access (e.g., view-only, edit, admin at a more detailed level)
Expected benefits
• Improved data governance and security
• Reduced operational risk (e.g., accidental changes by other teams)
• Better scalability for enterprise use cases
• Ability to keep a cleaner project structure without artificial splitting
Additional context
Separating content into multiple projects (current workaround) adds complexity, duplication, and overhead, especially at scale.
More granular permissions would significantly improve Stripo’s suitability for large, multi-team organizations and support broader adoption.
L
Lucas Laguens
Hello Marina,
Thanks for the detailed feedback - let me lay out our setup so the limitation we're hitting is clear.
To protect our shared modules from accidental edits, we keep them in a separate, dedicated project and share them out to the templates that use them. Since each module is reused across many templates, an edit in one place would otherwise propagate everywhere - so as far as we've found, this is the only safe approach.
Each of our other projects maps to a single brand we manage, structured like this:
Brand (project) → Country (folder) → Template type (folder) → Templates
The issue is that we'd like to give colleagues access to the templates for their specific country only, but Stripo's access control stops at the project level, so that isn't possible today.
The natural workaround - restructuring so each project maps to a country rather than a brand - doesn't work for us either: we'd then have to re-share our modules across hundreds of templates in every country project, adding significant duplication and maintenance overhead.
That's exactly why folder or template-level permissions would make such a difference for us. Could you let me know whether there's a way to achieve country-level access today that we may have missed - and if not, whether more granular permissions are on the roadmap?
Thanks,
M
Marina Kryvenets
updated the status to
under review
M
Marina Kryvenets
Dear Lucas,
Thank you for your suggestion. In your request, you specified that separating content into multiple projects adds complexity, duplication, and overhead, especially at scale. Could you clarify this in detail? We would like to add that there are groups https://support.stripo.email/en/articles/8544471-what-is-group-and-how-to-use-it for updating settings for multiple projects, and there is template sharing https://support.stripo.email/en/articles/11712283-share-an-email-template for working with a template in multiple projects.