Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • funkwhale funkwhale
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 384
    • Issues 384
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 16
    • Merge requests 16
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • funkwhale
  • funkwhalefunkwhale
  • Issues
  • #152

Closed
Open
Created Apr 05, 2018 by Agate@agate💬Owner

Permission management overhaul

Right now we use django's built in permission system, which is nice but also really complicated too, and really granular.

Having something less granular and easier to graps for instance admins would probably be better. I was thinking implementing a UserRole model, with a OneToOne field to User, that would store a few boolean:

  • librarian: can import tracks, correct them, follow other instances catalog
  • federator: can access instance-level and library federation setting, accept follow requests, etc
  • manager: can change other people's permission, delete user accounts, edit instance settings, etc

Don't mind the name, they can change.

User having the superuser flag to True would be able to do all of the above.

Assignee
Assign to
Time tracking