User accounts
When setting up a PhotoDB / AudioDB instance you may create individual, role-based user accounts for your collaborators. Users of the application are identified by account names.
User accounts are optional; The application can be run either with login disabled or login enabled. This is configured in the config.yaml
file:
Login disabled
With config.yaml
entry
login: false
the application is used without user identification. All users using the application are named anonymous
.
There are no access restrictions, so anonymous
has admin rights.
Login enabled
With config.yaml
entry
login: true
the application is used with the need for user identification. Upon opening the web interface users will be prompted to login with their idividual user name and password.
Logged in users have access restrictions specified by the roles they are associated to.
On the newly installed application, there are no accounts registered, so a login is not possible. Start with Login disabled to create at least one admin account. Then you can enable login and use your created admin account to login.
Account management
Accounts can be managed by users logged in by accounts with associated admin role only. Or by disabled login, leading to admin rights.
The account management page is located at the AudioApp web interface.
Even for PhotoDB only projects, you need to open the AudioDB web interface to manage accounts:
Example: Application sever is accessible by web address:
http://localhost:8080
Then PhotoApp is at:
http://localhost:8080/web/photo
Then to switch to AudioApp, you need to replace the photo
part with audio
:
http://localhost:8080/web/audio
At AudioApp, click on the top left button to open the left navigation side panel and select the entry Project selection
. Then the left navigation side panel shows some entries. Click on the Accounts
entry to open the user accounts management page.
By create new account-button, new user accounts can be created. Normal users of AudioDB or PhotoDB do not need roles. So the roles selection box can be left empty. A user account privileged to manage user accounts needs the role admin
or some other more specific role.
Roles
Normal user accounts may not need roles.
Privileges and restrictions are specified by roles that are associated to user accounts by account management.
Roles:
admin
: Most privileged role, containsmanage_account
andcreate_account
.manage_account
: Able to only manage accounts, containscreate_account
.create_account
: Able to only create accounts.readOnly
: Restriction to view but not change, currently AudioDB only.reviewedOnly
: Restriction to only view already reviewed items, currently AudioDB only.