Users

Files

• ApplicationRoleDto.cs

  This file defines a Data Transfer Object (DTO) named `ApplicationRoleDto` within the `GlassHopper.Definitions.Apps.Users` namespace. It serves as a lightweight contract for transferring role-related data, likely between a backend service and a frontend client or API consumer. The class contains two key components: a unique identifier (`Id`) of type `Guid` and a text-based name (`Name`) initialized to an empty string by default. This structure is typical in C# applications using Entity Framework or similar ORMs to decouple internal domain models from external interfaces.

• LoginUserResponseDto.cs

  This file defines a Data Transfer Object (DTO) named `LoginResponseDto` within the `GlassHopper.Definitions.Apps.Users` namespace. It serves as a structured response model for user authentication operations, encapsulating the outcome of a login attempt. The key components include an `IsSuccess` boolean flag and an optional `ErrorMessage` to indicate status, alongside `UserId`, `AccessToken`, and `RefreshToken` which provide essential credentials upon successful authentication. This DTO facilitates secure and standardized communication between the application's backend and client-side interfaces by bundling all necessary login data into a single object.

• OrganizationDto.cs

  This file defines a Data Transfer Object (DTO) named `OrganizationDto` within the `GlassHopper.Definitions.Apps.Users` namespace. It serves as a lightweight data structure for transferring organization information, likely between application layers or services. The key components are two public properties: `Id`, which stores a unique identifier as a GUID, and `CompanyName`, which holds the organization's name as a string initialized to null by default. This simple class facilitates clean separation of concerns by exposing only necessary data fields without business logic.

• UserOrganizationDto.cs

  This file defines the `UserOrganizationDto` class within the `GlassHopper.Definitions.Apps.Users` namespace, serving as a Data Transfer Object for user-organization relationships. It encapsulates key attributes including an associated `OrganizationDto`, an `ApplicationRoleDto`, and boolean flags for active status and administrative privileges. The primary purpose is to transfer structured data regarding a user's specific role and membership state within an organization across application layers. Key components include the nested DTOs for organization and role details, alongside simple property mappings that indicate whether the relationship is active and if the user holds admin rights.