Why we need roles
Besides the two main types of accounts in this solution, it's important to include clear roles for both account types. Defining roles helps keep the system secure by controlling who can access what. It also ensures that users can work efficiently within the database by having the right permissions for their tasks.
With a well-defined Roles System, the app can prevent unauthorized actions and confusion, making it easier to manage access and keep everything running smoothly. This approach supports safe and effective work inside the database solution for all users.
Any unauthorized access or security risk will be blocked to maintain the integrity of the Role System
Home page
On the home page, the main account is the primary administrator of the database unit and performs the most crucial actions and operations there.
- Manage environment for both account types
- Can upgrade current plan
- Can edit account appearance and data
- Change the appearance and visuals of the overall environment
- Can change their password
- Add, create, and remove members from the database
- Create all three types of components
- Assign members to specific components
- Edit the look of any component
- Mark components as favorites
- Open any component at any time
- Delete any component
When the main account deletes a component and its items, members linked to that component will encounter serious errors.
On the home page, member accounts have their access to components restricted by the main account, but they can still perform other actions within their permissions.
- Can edit their account appearance and data
- Can change their password
- Can customize environment visuals
- Can access only components attached to their account
- Can favorite components attached to them
Component loader
Just like on the home page, the main account remains the administrator in the component loader, manages permissions for members, and has more actions available.
- Can create items
- Can delete items
- Can edit items appearance
- Can add viewers and editor
- Can change or remove editor and remove viewers
For members, just like on the home page, they can only access items that are specifically linked to their account by the main account and nothing more.
- Can view only attached items
- Can access only attached items with correct role
If the main account deletes an item, downgrades a user's role, or completely removes them from the item, any member currently inside that item will encounter errors.
Cell content
For cell content within a cell item, there are no administrators or members. Instead, access is defined by three distinct roles, each determining the level of permissions for actions and operations.
- Can create, delete, set favorite, and edit columns and modules — Master
- Can add, edit, delete child elements like rows and entries — Master and Editor
- Can only see the whole data of cell content — Viewer
- Can see stats of cell content — Master and Editor
- Can print content — All
- Can apply favorite filters — All
Frame content
For frame content within a frame item, it follows the same role structure and defined rules as the previous cell content, but with different actions and operations.
- Can attach cell item - Main account as Master
- Can create and delete frame elements — Master
- Can edit all frame elements — Editor and Master
- Can only use and see frame elements — Viewer
- Can reorder element positions — Master and Editor
- Can change widget attachments — Master and Editor
Operator content
For operator content within an operator item, all roles and structures are defined the same as the two previous content types, but with different actions and operations.
- Can attach cell item - Main account as Master
- Can use all functions in both operator types — All
- Can use created operations — All
- Can create operations with functions — Editor and Master
- Can delete operations — Editor and Master
Operations created by a Master can only be deleted by the Master, while those created by an Editor can be deleted by both the Editor and the Master.