Skip to content

Groups or Role-based authorization #68

Closed
@joepio

Description

@joepio

The current Hierarchy #18 model allows for setting read and write rights, but it is very basic and definitely not good enough for more complex usecases.

Must haves:

  • Define Roles and define how these grant rights in specific contexts
  • Add and remove Roles to users, which in turn grant rights to sets of Resources
  • See which Roles a users possesses in some context (Maybe a Drive?)

Nice to haves:

  • Set durations for Roles, so they are temporary

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions