Building Applications
Authentication and roles
When your product needs sign-in, protected pages, or different kinds of users, DeplAI can generate that behavior from the request.
When your product needs sign-in, protected pages, or different kinds of users, DeplAI can generate that behavior from the request.
You describe roles in product language. You do not configure an authentication library.
What the generated product can include
Depending on the request, applications can support:
- sign-in and sign-out
- areas that require an authenticated user
- distinct roles such as customer, member, staff, or administrator
- an administrator area for managing the product
If DeplAI is unsure who should administer the application, it may ask before building.
Previewing signed-in experiences
Use the preview as each role would. If demonstration accounts exist, use them to reach protected pages. If you create an account in the preview, that account belongs to the preview environment, not to a production customer base.
What to write in the request
Be explicit about access:
> Patients book appointments without seeing other patients’ details. Staff need an admin area for managing appointments and availability.
Avoid describing cookies, session storage, or hashing. Those are implementation details DeplAI manages.
Related: Writing a good request | Application data | Security and data