PlatixAgency workflows

Agency workflow answer

How should agencies manage team access to client trips?

Give every teammate their own account and the least powerful role that lets them do their work. Keep client trips, proposals, intake, exports, and integrations scoped to authorized agency members.

Why it matters

The agency process has to stay clear before the client sees the plan.

Travel agencies handle client preferences, schedules, budgets, and sometimes sensitive context. Role boundaries make audit trails clearer and reduce the blast radius of mistakes or team changes.

Common agency workflow

  • Invite each teammate with their own email and role.
  • Use owner/admin for workspace administration, manager for review, advisor for assigned client work, and billing for subscription tasks.
  • Reassign active client work before removing a teammate when needed.
  • Review access after role changes, departures, or incidents.

Where this step can go wrong

  • Teams share one login.
  • Billing users get unnecessary client-trip access.
  • Departing advisors keep access longer than needed.
  • Client work is stored under personal accounts instead of the organization.

Platix example

How Platix supports this step.

  • Platix agency work belongs to the organization, not an advisor's personal trip library.
  • Role-based controls determine which workspace areas and actions a member can use.
  • Removal, workspace closure, exports, and support access are handled as organization-level controls.

Boundary

What Platix does not replace.

  • Roles do not replace the agency's own HR, compliance, or client-communication process.
  • Support access and API credentials should be scoped, time-bounded, and monitored.

Product guides

Use the exact Platix controls.

Questions

Should advisors share an agency login?

No. Shared logins weaken audit trails and make offboarding risky.

Can billing users see client trips?

They should not need broad trip access just to manage subscription tasks.

What should happen when an advisor leaves?

Remove access promptly and reassign active client work when needed.