In the digital world, permissions are pretty important when it comes to making software secure – and not allowing people without access to do something they aren’t supposed to do, or see information they aren’t supposed to see. Even more so when that software is not installed locally on a user’s machine. It’s extremely important that if someone isn’t supposed to be able to reach inside the proverbial cookie jar to take that cookie, they really shouldn’t be able to do it. Fortunately, READynamic™ was designed and built with a robust permission system for many different situations. In this article, I’ll discuss the three most important permission sets within the eBook solution.
When an account is created through the self-serve sign-up portal, it inherits the ‘student’ permission set. Keep in mind that READynamic was originally conceptualized as a solution for academia situations and the naming reflects as such; but, the names are arbitrary. The ‘student’ permission set is the most basic in READynamic. Those with the ‘student’ permission set will minimally be allowed to read a public or assigned book, create annotations and navigate through basic UI items. Basically, just enough to experience the core of the system and fulfill their ‘student’ role.
The next available permission in the system is the ‘publisher’ permission set. This permission gives the user the ability to upload their own books into the system. They then maintain control of the book and can create overlays and annotations to create rich content for other readers of the book. Publishers can assign books to others, or loan them temporarily, where the assigned user only has access to the book for a limited time. This permission set also grants access to the reporting section in the UI to run reports available to that account. Typically, a teacher might have this permission set to upload books for their class. It might also commonly be used to give an actual publisher or distributor access to a reseller’s system to upload books of their own.
The most important permission set in the system is ‘admin’. This grants the user access to everything in the system, including the administration console. This permission set allows a user to create and delete other accounts, upload and delete books, run reports, see active system process, and more. It’s exceptionally important that unintended accounts don’t get assigned this permission set.
Permission sets attached to a user’s account can be modified in the admin control by editing a user and selecting which set should be on it. An account can have only one permission set or they can have all of them at once. You can do this by holding down the control button and clicking each permission set.
Hopefully you’ve learned a little more about READynamic permissions, and now know how best to apply them to your users!