Skip to content

[Feature] Implement Policy-Based Access Control System #2

Description

@grudge007

Hey there! 👋

AuthD is a simple identity management service (v1.0.0). We currently have basic roles (owner, admin, member) but would love to add a more flexible permission system.

What we need

Right now, if you're an "admin" you can do everything admins can do. It'd be nice to be able to say things like:

  • "User X can add members but not delete projects"
  • "User Y can view only"
  • "User Z can manage settings but not billing"

What to do

  1. Design a simple permission model (e.g., project:create, members:add, etc.)
  2. Store permissions in the database
  3. Check permissions when users try to do things

Don't worry about

  • Making it perfect
  • Supporting every possible use case
  • Breaking existing code (we'll keep roles working)

Just something that works and makes sense. If you have questions, just ask!

Thanks for checking this out! 🙏

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions