My migration (in test environment) is now completed.
Before I make a snapshot for the production server, I like to set the administrative user.
I picked an existing user and awarded it with the administrator role.
When I login with these credentials I see only the settings of this account, not the admin panel.
The key issue here is likely that simply assigning the “Admin” role in the WebUI is correct, but the user needs to log in via /admin (not /account) after the role is assigned. Let me also check if there’s anything about the WebUI login URL distinguishing admin vs. user.
The key insight is this line from the WebUI docs:
When an account without administrator permissions signs in at /admin, the console redirects to the Account Manager rather than rejecting the request outright.
This is exactly what you’re experiencing. The “Admin” role label in the account’s UserRoles field is indeed the built-in admin role and grants all permissions, but there are two things to check:
Make sure you are navigating to /admin, not /account. If you go to /account, you will always see only the personal account manager, regardless of your role.
Verify the role is correctly saved. The built-in admin role (the Admin variant in UserRoles) grants every permission on the server. If after saving you still get redirected to the account manager when visiting /admin, the role assignment may not have been saved properly. Open the account in the WebUI (Management › Directory › Accounts), confirm the role field shows Admin, and save again.
According to the docs, the admin role “grants every permission defined by the server, including configuration and principal management” - so once it is correctly assigned and you log in at /yourserver/admin, you should see the full administrator console.
@helpbot is it correct that there is a system administrator (that i can't choose while making a user and the Administrator role that i can choose while editing a user?
The most likely cause is that the access token you are still using was issued before the role change, and permissions are baked into the token, so the new admin rights will not show up until you fully log out and back in (or the token refreshes). Try that first.
If a fresh login still lands you on just your own account, then check the role itself: confirm the role you assigned actually includes the admin/registry permissions, and that it was granted to the right account.