Hi, now I am able to create the applications, but my main problem is that I don’t know how to create roles and how to create usernames and passwords. Is there any possibility to view the username and password?. After a days, I learned how to create user and admin roles, but I still don’t know how to create usernames and passwords. So someone could help me to make clear
hallo @Shakeel Ahamed ,
you need to use EncryptPassword then use the hashed password in create user
Hello Shakeel,
I’ve attached an OML. Check the Common UI flow, then the Register screen you’ll find the registration flow there. It’s a simple example that should help clarify things. (Ignore the tenant part)
Hope this helps
Thank you Mr.Sherif
You’re very welcome anytime 😉
In OutSystems, you don’t manually create passwords in your application, and you can never view a user’s password. Passwords are encrypted by the platform for security reasons.
1. Creating Roles
Roles are created inside Service Studio:
Open your module
Go to Data → Roles
Create a new Role (ex: Admin, User)
Assign that role to screens or logic under “Roles” property
Use CheckRole() to verify permissions in logic
2. Creating Users
Users are not created inside your app. They are created in OutSystems User Management:
Go to Users application (built-in)
Menu Users → Create New User
Set:
Username / Email
Generate or set a Password
Assign Roles (including the roles from your module)
The platform automatically saves the password securely.
3. Can you view the password?
❌ No. OutSystems does not allow you to view any user’s password. Passwords are encrypted (hashed) and cannot be retrieved.
If needed, you can only:
✔ Reset a password
✔ Send a password recovery email
✔ Change it manually in the Users app
But you can never view the original password.
4. Logging in
Once the user is created in the Users app, they can log in to your application using:
Their Username (or Email)
The Password you set (or the password they reset)
Your application uses the built-in OutSystems Authentication automatically.
Peter Hieu.
Thank you so much Peter