Clients

Ghloria keeps client information connected to the agency workflow, so client records are not isolated contacts. Each client can hold profile data, ownership, activity metrics, related trips, documents, and direct actions for new work.

Client List

The Clients area gives the team a structured view of the agency's client base.

• Search clients by name or related client text.
• Filter by status: active or inactive.
• Filter by type: Corporate, Leisure, or Agency.
• Sort the table by name, status, type, country, trip count, and last trip date.
• Open a client record from the table.
• Create a new client from the page action.

The table shows the client name, type, country, status, total trips, and last trip date. Pagination and sorting are kept in the URL, which makes filtered views easy to revisit.

Creating a Client

Use New Client to add a client to the workspace.

The current form supports:

• Name
• Email
• Phone
• Type
• Owner
• City
• Country
• Notes

Client type defaults to a business-ready classification and can be set to Corporate, Leisure, or Agency. Owner assignment links the client to a member of the workspace, helping agencies keep accountability clear across sales and delivery.

Client Profile

Each client has a detail page with editable operational data.

You can update:

• Name
• Email
• Phone
• City
• Country
• Client type
• Owner
• Notes
• Logo or client image
• ERP link
• Active or inactive status

The header includes quick actions for sending an email, starting a new trip for that client, and editing the external ERP link. Users with manager-level access can delete a client from the detail page.

Trip Activity

Client records include trip context, so account history stays close to future work.

The detail page shows client activity metrics for:

• Total trips
• Active trips
• Trips in the last 30 days

The related trips section can be expanded when needed. It supports search, status filtering, and sorting by update date, title, proposal count, amount, or status.

Client Files

Client records include a files section for entity-specific artifacts.

The current implementation supports:

• Uploading files to the client record
• Searching files
• Browsing files by folder
• Moving files between folders
• Deleting files

Files are loaded on demand, which keeps the client profile fast while still making documents available when the team needs them.

Access Notes

Some actions depend on the user's role. Creating and editing client details is part of the client management workflow, while destructive actions such as deleting a client are limited to users with manager access.