Transcript
Welcome into our first lesson. Throughout this series, we're going to be building an inventory management application together.
I'm going to take you through every step to build this application. By the end, you'll not only have the final product, but you'll be able to customize it to your team's needs.
Before we start building, let's talk about the problems we're solving and how we're breaking down our users. We need to ensure each user can only access the data we want them to access.
As an inventory management application, we're building systems to view inventory, recent sales, and new purchase orders. We will also add and manage suppliers to see who you're ordering parts from.
[.blog-callout]
If you want to skip the manual setup, you can use the AI co-builder to generate your initial inventory management pages and database structure instantly.
[.blog-callout]
In our application, we'll have two main user groups. We have the warehouse manager, who acts as the app admin with full access to create and update everything.
They also invite sales managers to join. The sales managers will be able to see the sales process but won't be able to do other key aspects in the application.
I want to talk to you about a technical term called CRUD. CRUD stands for creating, reading, updating, and deleting data.
We use CRUD permissions within our application to decide which of our users can access each part of the application. Here is how each role breaks down.
Sales managers will be able to securely log into the portal. They can view inventory data, but they can only read that data.
They cannot create new inventory, new suppliers, or new purchase orders. However, we will allow them to view and manage sales orders with full CRUD permissions.
[.blog-callout]
For managing these different roles, Softr's user groups make it easy to define exactly what each person sees when they log in.
[.blog-callout]
We will also show them graphs related to revenue and reporting in a read-only capacity. These are the permissions for anyone in the sales manager user group.
Warehouse managers control the app-wide admin functionality. They can add new sales managers to the team and manage the supply of the inventory.
They can create and manage purchase orders and supplier information. This includes creating new suppliers or removing them as needed.
We'll give them full access to the inventory dashboard, including revenue and order stats. We can even show specific graphs for warehouse managers regarding team member performance.
Softr makes it really easy to show only the data relevant to each user who is logged in. Warehouse managers can also create or update sales orders just like the sales managers.
[.blog-callout]
Instead of using external tools to handle data updates, you can use Softr Workflows to trigger internal logic directly when a manager updates a record.
[.blog-callout]
They can also delete any outdated or incorrect data across the entire application. Generally, warehouse managers have full CRUD access, while sales managers have limited CRUD access.
When it comes to actual sales-related activity, sales managers have full CRUD access. That is the breakdown of our two user groups and their permissions.
In the next lesson, I'll show you how to structure your database with these two user groups in mind. Beyond that, it will be easy to implement visibility rules.
Keeping your data safe and organized is a big part of Softr. We make it really easy on you to ensure users only see what they have access to.
Now that we understand the users and the problems we are solving, we are ready to start structuring our database. I will see you in the next lesson.
