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.