Skip to content
v0.5.1GitHub

Using

Returns all created users (admins and regular users) with their domain permission matrix. API keys are not included.

applies to v0.5.1
GET
/store-api/auth/users
curl --request GET \
  --url https://example.com/store-api/auth/users \
  --header 'Authorization: Bearer <token>'

For role == "Admin", permissions is meaningless for access control: admins have unconditional access regardless of its contents. It is usually empty for an admin but not guaranteed to be — e.g. a user promoted to admin via luradb.toml keeps any permissions set before the promotion. Never read an empty array as “no access” or a non-empty one as a restriction on an Admin row.

The list reflects the permission table as stored — it is not cross-checked against existing domains, so an entry for a since-deleted (or not-yet-created) domain is shown unchanged.

Authorizations

Section titled “Authorizations”

Responses

Section titled “Responses”

200

Section titled “200”

List of all users (without API keys), including their domain permissions

Media typeapplication/json
Array<object>
object
created_at
required
integer format: int64
name
required
string
permissions
required

Domain permission matrix — see list_users doc for role == "Admin" semantics.

Array<object>

One entry of a user’s domain permission matrix. store_type/access are lowercase and match the write-endpoint vocabulary exactly (parse_store_type, access parsing in set_permission) — usable as-is in a follow-up request.

object
access
required

"read", "write", or "ddl".

string
domain
required
string
store_type
required

"kv", "json", or "rel".

string
role
required
string

Example generated

[
  {
    "created_at": 1,
    "name": "example",
    "permissions": [
      {
        "access": "example",
        "domain": "example",
        "store_type": "example"
      }
    ],
    "role": "example"
  }
]