Coder Social home page Coder Social logo

Import all users from Plex about overseerr HOT 13 CLOSED

sct avatar sct commented on September 3, 2024 16
Import all users from Plex

from overseerr.

Comments (13)

fenixjr avatar fenixjr commented on September 3, 2024 3

Currently a user's permissions can not be set until they have logged in, but in addition there is only the default "request" permission enabled upon creation. Being able to alter the default would save time from individually editing each user if you know you want every user to have "auto-approve" or "vote" settings etc.

from overseerr.

XTechLabs avatar XTechLabs commented on September 3, 2024 1

How would should re shares be handled? Meaning let's say a user is shared with the server. We remove them but now they are re shared with the server.

Probably the safe bet is to disable the user instead of removing them.

from overseerr.

zZebrahz avatar zZebrahz commented on September 3, 2024

Importing the users before their initial login could also be used to allow or deny certain users to be able to use the app which would be helpful.

from overseerr.

XTechLabs avatar XTechLabs commented on September 3, 2024

Be able to manage users before they log in. I believe a sync job to Plex to collect all the users will be needed and should be ran periodically.

It would be nice to automatically remove users when they leave a Plex Server as well.

from overseerr.

TheChrisK avatar TheChrisK commented on September 3, 2024

This would be a nice option. I had a friend test out the interface and he only showed up as a user after he logged in. Only then was I able to edit his profile.

from overseerr.

samwiseg0 avatar samwiseg0 commented on September 3, 2024

How would should re shares be handled? Meaning let's say a user is shared with the server. We remove them but now they are re shared with the server.

from overseerr.

samwiseg0 avatar samwiseg0 commented on September 3, 2024

This would be a nice option. I had a friend test out the interface and he only showed up as a user after he logged in. Only then was I able to edit his profile.

This is the current workflow. I do agree this list should be all the active shared users.

from overseerr.

samwiseg0 avatar samwiseg0 commented on September 3, 2024

I like that idea. Same as how Tautulli handles it.

from overseerr.

douglasparker avatar douglasparker commented on September 3, 2024

How would should re shares be handled? Meaning let's say a user is shared with the server. We remove them but now they are re shared with the server.

Probably the safe bet is to disable the user instead of removing them.

I agree, this is the best way to handle this.

I think accounts should be automatically enabled again when readded to the server as well.

from overseerr.

sct avatar sct commented on September 3, 2024

Currently a user's permissions can not be set until they have logged in, but in addition there is only the default "request" permission enabled upon creation. Being able to alter the default would save time from individually editing each user if you know you want every user to have "auto-approve" or "vote" settings etc.

Great idea. We can have a configurable default.

from overseerr.

sct avatar sct commented on September 3, 2024

Referencing #388 here

from overseerr.

doob187 avatar doob187 commented on September 3, 2024
var plexWrapper = require("plex-wrapper");
var client = new plexWrapper.PlexAPIClient("clientId", "username", "password");
 
client.getUsers().then(result => {
    // The result contains a JSON array with all the shared library users
    console.log(result);
});
 
client.getPendingUsers().then(result => {
    // The result contains a JSON array with all the pending shared library users
    console.log(result);
});
 
client.getAllUsers().then(result => {
    // The result contains a JSON array with both shared and pending shared users (Keep in mind that the properties may vary from the 2 types of user)
    console.log(result);
})

var plexWrapper = require("plex-wrapper");
var client = new plexWrapper.PlexAPIClient("clientId", "username", "password");
 
client.removeUser("userId");
client.removePendingUser("userId");


from overseerr.

github-actions avatar github-actions commented on September 3, 2024

🎉 This issue has been resolved in version 1.12.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

from overseerr.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.