Book access and permissions
Table of Contents
Summary
Every book carries a set of book currencies that constrains what may be booked into it, and is permissioned at a fine grain — read/write on the book, inherited by every trade booked within it. Access to a book is not permanent: it lapses without periodic renewal and must be re-requested. A proposed disk-usage-style visualisation lets a user drill from an aggregate book down into its children to see risk concentration.
Detail
Book currencies
See Book Currencies for the allowed-currency set that constrains what may be booked into a book.
Permissions
All objects in the system, books included, are permissioned at a fine grain — e.g. read/write on a book, inherited by every trade booked within it. Users can be grouped geographically (e.g. NY users can only see NY books), and the permission model must be capable of enforcing Chinese Walls between desks. See Book groups and rates centres for how centre ownership additionally functions as an access-control mechanism at the trade level.
Access review
Book access is not permanent: it must be periodically reviewed (monthly, quarterly, etc.). If nobody renews a user's access to a book, it is automatically invalidated and must be re-requested. This review cadence is part of the wider Book lifecycle, beginning during a book's opening workflow and continuing for as long as the book remains live.
Book tree visualisation
A disk-usage-style ("GNOME Baobab") zoomable tree has been proposed, letting a user drill from an aggregate book down into its children and see risk concentration as a pie-chart-like breakdown.
See also
- Book — hub note.
- Book lifecycle — the opening workflow's access-review step.
- Book groups and rates centres — centre ownership as trade-level access control.
- Book Currencies — the allowed-currency set in full, and the distinct per-book Accounting Currency field.