Currently, there are no dedicated admin features in CasualOS. All features are related to users and their own management (comID, studios, records, etc.). The only way to provide support and break out of the paradigm is to use the API directly, but that is also limited.
This issue tracks work on adding the ability to specify a role that user accounts can have.
For now, there are only two roles: "none" and "superUser".
"none" is self-explanatory. It is the default and doesn't grant any additional features.
"superUser" is only granted to individuals who have database-level access and can be used to gain limited access to data that is not owned by the user themselves. For example, getting a user's info, updating subscriptions, or updating configurations.
Currently, there are no dedicated admin features in CasualOS. All features are related to users and their own management (comID, studios, records, etc.). The only way to provide support and break out of the paradigm is to use the API directly, but that is also limited.
This issue tracks work on adding the ability to specify a role that user accounts can have. For now, there are only two roles: "none" and "superUser".
"none" is self-explanatory. It is the default and doesn't grant any additional features.
"superUser" is only granted to individuals who have database-level access and can be used to gain limited access to data that is not owned by the user themselves. For example, getting a user's info, updating subscriptions, or updating configurations.
Super user permissions: