Team Collaboration

How Consultants and Managers work together in Ghloria across proposals, trips, and client management.

Ghloria is built for agency teams. The two-role system (Consultant and Manager) maps to how agencies actually operate: consultants do the proposal work, and managers oversee commercial progress and control the workspace.

How Roles Divide the Work

Task	Consultant	Manager
Create and edit proposals	✓	✓
Manage client records	✓	✓
Create and manage trips	✓	✓
Delete a trip or client	—	✓
Request / approve proposal deletion	✓ (request)	✓ (approve, deny, or delete)
Access Suppliers section	✓	✓
Use the AI Assistant	✓	✓
Export PPTX and email	✓	✓
View full team pipeline (dashboard filter)	—	✓
Invite and manage team members	—	✓
Change workspace settings	—	✓

→ Full permissions: Roles and Permissions

Consultant Workflow

A consultant's day-to-day work in Ghloria:

Create proposals for assigned clients and trips
Enter service details: flights, accommodation, extras, itinerary
Set the budget using the standard margin calculator
Import supplier documents to populate pricing faster
Use the Travel Assistant to draft destination content, or request a proposal deletion when one needs to be removed from the pipeline
Generate versions when the proposal is ready for the client

Consultants see only their own pipeline on the dashboard. The dashboard is scoped to their proposals and trips automatically, they do not see other consultants' work unless a Manager shares it directly.

Manager Workflow

Managers use Ghloria to oversee the team's commercial pipeline:

Filter the dashboard by agent to see any consultant's active trips, proposal activity, and value in play
Review proposals built by consultants before they go to clients
Approve or deny pending proposal-deletion requests from the notification bell, or delete a trip outright
Change proposal statuses from trip and proposal tables to track commercial progress
Invite and manage team members from Settings, including changing roles
Configure workspace settings: company identity, brand, contact records, and template images

Assigning Proposals to Agents

Every proposal can be assigned to a specific agent (consultant or manager). The agent assignment:

Determines whose name appears in the proposal header and client-facing outputs
Determines which consultant's pipeline the proposal appears in on the dashboard

Any user can reassign the agent field on a proposal. If the new agent belongs to a different team member, Ghloria confirms the reassignment before saving.

Proposals are workspace-scoped, not user-private. Any workspace member can open any proposal. However, the dashboard only shows each consultant their own active pipeline by default.

To hand off a proposal to another consultant:

Open the proposal
Change the Agent field to the new consultant
Save, the proposal now appears in the new consultant's pipeline

Common Team Patterns

Senior consultant + junior consultant The senior creates the client and trip. The junior builds the proposal content. The senior reviews and sends.

Manager review before sending Consultant builds the proposal, sets it to Draft, and notifies the manager. Manager reviews the budget and itinerary, approves, then the consultant changes the version status to Open and sends.

Manager handles delivery Consultants build proposals. The Manager reviews the final PPTX or email output, checks the branding, and approves it for the client. This centralizes quality control over exported materials.

Workspace vs Multi-Workspace

A single Ghloria workspace is one agency (or one branch). If your organization operates multiple brands or entities, each can have its own workspace. Managers can belong to multiple workspaces and switch context using the company switcher in the navigation header.

Each workspace has its own:

Member directory
Client and supplier records
Proposals and trips
Templates and brand settings

Data does not cross workspace boundaries.