User management
Introduction
In yeet, we distinguish between two contexts and different user types.
This section explains the different user groups and shows how they fit into your development and application flow.
User types
Users are always bound to a specific context and database.
They do not exist across multiple databases and cannot be shared between them.
We provide two contexts:
yeet context
Users in this context can only access the yeet platform itself and cannot work inside deployed applications.
yeetDeveloper
As the name implies, this role is intended for developers working inside yeet.
A yeetDeveloper can manage projects, themes and data.
They can also create new yeetAppUser accounts for their applications and edit their information.
yeetAdmin
This is the power user for platform administration.
A yeetAdmin can create new yeetDeveloper and yeetAdmin users.
They can only access the admin console; their sole purpose is managing developers and other admins.
app context
Users in this context can only access deployed applications and cannot work inside yeet itself.
yeetAppUser
Users with this role can only access applications (projects in the app context).
They cannot access any part of the yeet development platform.
yeetAppAdmin
App admins can create new yeetAppUser accounts and additional yeetAppAdmin users.
They can access the admin console for application-level administration but cannot access yeet itself.
Rights
This subsection describes functionality that has not been released yet.
Default rights
Default rights define standard permissions for a preset type such as entity, enum or action.
Each default right defines the baseline behavior for operations like reading, writing and deleting.
By default, unspecified rights are initially set to true.
This default behavior ensures accessibility and smooth operation, but it must be reviewed and adjusted carefully to match your intended access control model.
Always verify and, if needed, tighten these settings to prevent unintended access and to maintain secure, role-based access control.
Specific rights
Specific rights allow fine-grained control over permissions for individual objects in your application.
For the preset types entity and enum, the selection list is linked to the actual objects you have created in the Data section, ensuring consistency across your application.
The action category includes all server-side actions that you define yourself or that are provided by the platform.
For custom types, you can define the names of right objects yourself. It is important to keep these names consistent across different roles.
If a specific right is requested for an object that does not exist, the platform falls back to the value defined in the default right for that type.
Specific rights can only be created if a default right for the corresponding type is defined.
Password guidelines
For security reasons, password guidelines must be strictly observed.
Passwords inside yeet and in created projects must fulfill the following requirements:
- at least 8 characters