All applications need roles, but not every application needs rules. However application functionality can be greatly enhanced by the introduction of few rules.
Roles
Roles are key to defining who can do what within an application, and are a key element of Role-Based Access Control (RBAC). Each Role is defined by a grid that contains the data models within an app, and the basic operations of create, read, updated & delete (CRUD). For example, an admin role might look like this:
Admin
- DataModel-1: Create, Read, Update, Delete
- DataModel-2: Create, Read, Update, Delete
While a Read-Only role would look like this:
Read-Only
- DataModel-1: Read
- DataModel-2: Read
In this lesson we’ll explore two roles for the Time Report app: Admin and User.
Rules
Rules are a set of conditions that can trigger a specific action. For this reason, when discussing Rules we really mean Rules & Actions, as Rules by themselves don’t really do anything.
Rules & Actions can be defined for nearly any type of scenario. In this lesson, we’ll learn how the Time Report app automatically sends emails and push notifications in response to two different triggering Rules.
