Skip to main content

Role-Based Access Control (RBAC) for Team Members

✨ Feature Request: Role-Based Access Control (RBAC) for Team Members

Description

Introduce Role-Based Access Control (RBAC) to allow workspace admins to manage access permissions for team members.
Admins should be able to create custom roles from the dashboard, assigning specific permissions (create, read, update, delete) across various resource types such as:

  • Projects

  • Services

  • Servers

  • Secrets
    ...and more.


💡 Motivation

  • Improve security and control within teams by restricting access to only what's necessary.

  • Prevent accidental modification or deletion of critical resources.


✅ Expected Behavior

  • Admins can create custom roles in the dashboard.

  • For each role, admins can define granular permissions for each collection/resource (CRUD).

  • When inviting a team member, an admin can assign role.

  • UI and API should respect the assigned permissions when rendering options or performing actions.


📌 Notes

  • Consider starting with predefined roles: Admin, Developer, Viewer, and allowing custom roles afterward.

Status: Completed

No comments yet

Be the first to share your thoughts.