Users
Accounts, roles and access to this workspace.
The authorization service did not answer, so the list could not be read. This is not the same as having no users.
Unauthorized
Why this table has its own screen
What it is. Accounts, roles and access. Technically these are rows like any other, and you can read them in the database browser.
Why it is not just a table. This is the one table where a careless edit locks you out of your own server. Granting the architect role, or taking access away, should be one obvious action with a visible consequence — not an UPDATE typed into a grid next to forty other tables. The authorization service owns these rows and keeps sessions in step with them; editing them by hand can leave a session alive for an account that no longer has the right.
How to think about it. Read users in the database browser when you want to understand. Change them here, where every action is named and confirmed.