Building a login page in an application typically starts with basic user data storage, like a database table for email and password. Initially, this data might be managed directly in the database. As application requirements evolve, user management features such as creating, updating, and deleting users are added within the application itself. This leads to code duplication when new projects with similar login and user management needs arise. Copying and modifying existing code across projects creates inefficiencies and potential bug propagation. For instance, a bug fixed in one project must be manually fixed in all others that inherited the code. This pattern highlights the challenge of repeated development for common features like authentication and user management. To address this, two main approaches are proposed: creating a reusable module/library or developing a separate, dedicated application for these services. The latter is often more efficient, allowing projects to focus on their core features and centralizing maintenance. Ready-made solutions like Auth0 and Firebase Authentication already exist for this purpose. The text introduces "Roled" as a specific platform for centralized user and role management, offering authentication as a feature. Roled allows applications to delegate authentication and permission management to a single platform, avoiding code duplication and simplifying maintenance. This approach enables each application to have its own isolated user and role system.