2
Hierarchical roles
Source: twentyhq/twenty#11559 · opened by @eduardohartz
Hey! I know this is quite a bit, and I totally understand it's a lot to implement, but I wanted to share an idea that could really streamline how users and data are managed across roles in the system. It’s a suggestion that ties together three concepts: Hierarchical roles Let’s say there are three roles: Director → Manager → Agent Each user is assigned one of these roles. A toggleable feature could allow users in higher roles to manage users in the roles directly beneath them. For example, a Manager can manage their Agents, and a General Manager can manage both Managers and their Agents. This could help with visibility and delegation of tasks. These roles can also have permissions, so essentially its the current system but with hierarchy. Restricted access to entries For example, if we have a Leads object, each lead would have an “owner” (or similar) field (assigned to a workspace user), and only that user would have access to view or interact with the lead. But here’s whe…
No pledges yet. Be the first to back this.
Comments
Similar requests
📤 Permissions: record sharing
1 vote · 0 comments
Field's Editability control across the platform limited to Workflows and API
1 vote · 0 comments
🔄 Round-robin
2 votes · 0 comments
Guide to success for this project. Invoicing, Stable/pre-release, automation, Messaging.
4 votes · 0 comments
MCP: add a file upload tool so AI agents can attach real files to records
0 votes · 0 comments
No comments yet.