v0.24.0

Added

• New token scope create_vault: other projects can create their own vaults through the API and have all rights in
  them, and only there (up to 20 per token).
• Token permissions can be changed afterwards (name, expiry, permissions) without changing the token value.

Changed

• One permission system: tokens get one level per notebook (read, inbox, read_inbox, curate, write,
  write_curate, admin, also for all notebooks with *). Existing tokens keep working.
• User accounts use the same levels: the new role member gets one level per notebook, optionally limited to an area.
  The roles editor and viewer keep working and become members when edited.
• The web interface shows actions according to the rights in the open vault. Vault settings are available to anyone
  with admin in that vault.
• The file tree is now available to access limited to an area and shows only notes in that area.

Security

• A token with admin for individual vaults can no longer manage the server (users, tokens, webhooks). That now
  requires admin for all vaults.