---
title: "Managing access to shared travel agency accounts"
description: "Manage agency account access with clear ownership, authorised users, recovery planning and offboarding checks. Includes an inventory template and Nowah example."
canonical: https://nowah.xyz/blog/travel-agents-managing-access-to-shared-travel-agency-accounts
lastModified: "2026-11-20T15:07:16.157Z"
---

# Managing access to shared travel agency accounts

Manage agency account access with clear ownership, authorised users, recovery planning and offboarding checks. Includes an inventory template and Nowah example.

Set up an authorised [Nowah](https://app.nowah.xyz) planning workflow with clear account ownership, then use a fictional brief to practise itinerary research and handoff. Advisers can evaluate conversational planning and editable days without sharing credentials or private case files. Keep each product's actual sign-in and administration options subject to verification rather than inferring permissions from the planning interface.

The task is operational as well as technical. An adviser may be able to complete a trip-planning exercise but still lack authority to use a particular account or access a private case. Make those responsibilities clear, with a named owner and a legitimate recovery route for each service.

## Inventory accounts by purpose and owner

List the services the agency actually uses and the work each supports. Identify the person or business role responsible for the account, billing contact and appropriate recovery arrangement. Do not put passwords, authentication codes or recovery secrets in the inventory itself.

Distinguish ownership from everyday use. A colleague may operate a service without being the person authorised to change its settings or agreement. Record who can make those decisions and who should be contacted when a problem occurs.

Check whether an account is tied to personal contact details that make continuity uncertain. Resolve ownership and recovery through the provider's legitimate process and the agency's approved arrangements. Do not assume that a shared agency purpose permits any particular login or transfer method.

## Verify the product's actual access options

Review current terms and supported account arrangements for each service. Where individual user access or roles are available and appropriate, use the authorised configuration. Where a requirement is not supported or remains unclear, seek clarification rather than inventing a workaround based on shared sign-in details.

Review Nowah's current [terms](/terms), privacy information and actual account options before assigning use, then test its [planning features](/features#plan) on a fictional brief. Use the [planning-assistant versus CRM comparison](/blog/travel-agents-comparing-a-travel-planning-assistant-with-an-agency-crm) to define the intended role. The useful account decision supports a concrete travel task while wider administration requirements remain independently verified.

Keep the intended workflow explicit. Who prepares the brief, who reviews the itinerary and where is the authoritative client record? Verify the actual handoff method instead of assuming a specific integration, export or collaborative account capability.

## Use an access inventory template

Maintain this inventory through the appropriate agency process:

| Field | What to record |
| --- | --- |
| Service | Product and business purpose |
| Account owner | Person or role authorised to maintain the arrangement |
| Approved users | People permitted to perform the relevant tasks |
| Access scope | Necessary role or supported permission arrangement |
| Recovery route | Appropriate contact and procedure, without secrets |
| Information | Categories of data needed for the task |
| Review trigger | Joiner, role change, departure or service change |
| Last review | Date and responsible reviewer |
| Open issue | Unresolved requirement and next action |

Keep the inventory accessible only to the people who need it. Even without passwords, it describes the agency's services and responsibilities. The record should support continuity and review, not become another uncontrolled list copied into every team conversation.

## Apply appropriate sign-in protection

Use current authoritative guidance and the options actually available for the service. [NIST's account-security guidance](https://www.nist.gov/cybersecurity-and-privacy/how-do-i-create-good-password) recommends multifactor authentication where available and a password manager for accounts requiring passwords. It also discusses passkeys and the limitations of relying on passwords alone.

Ask the agency's appropriate technical owner to establish and maintain the supported protection. Do not assume that a particular product exposes a setting simply because it is generally recommended. Follow the provider's current instructions and the agency's approved process for recovery and administration.

Keep sign-in secrets out of client records, planning prompts and ordinary messages. A colleague needing a case handoff should receive the appropriate information and authorised access, not an improvised copy of someone else's authentication details. Resolve the access requirement through the proper route.

## Use a joiner, mover and leaver checklist

When someone joins, identify the tasks they need to perform and establish appropriate authorised access. Explain the service role, information handling and route for questions. Use fictional training cases where they can answer the learning need without exposing client records.

When responsibilities change, review access against the new task. A person who no longer handles an account may not need the same permissions, while a new responsibility may require an approved change. Record the decision and verify the actual configuration through the supported process.

When someone leaves, assign ownership of active cases, review their access and check the continuity of legitimate recovery and administration. Preserve current client decisions and service records through the appropriate process. Do not depend on an individual's memory or personal contact details to keep the agency functioning.

## Work through a hypothetical departure

Imagine a fictional agency discovering that an important service account uses a departing employee's personal recovery details. Other colleagues have been relying on that person's availability whenever an access issue arises. The agency has active cases that need continuity.

The responsible owner reviews the service's actual terms and account options, then follows its legitimate process to establish the appropriate business arrangement. They do not ask the colleague to send authentication codes into a group message or assume that changing a password alone resolves ownership.

In parallel, active case responsibilities are handed over through the agency's designated records. The receiving adviser can identify the current brief, proposal, approval and service status with authorised access. Any unresolved account issue has a named owner and a documented next step.

The agency updates its inventory and departure checklist so future changes trigger the review earlier. This fictional example illustrates a continuity method, not a claim that any named product has a particular transfer or administration feature.

## Keep Nowah planning inputs appropriate to the task

Give Nowah the relevant route constraints and inspect the resulting days, without including credentials or unrelated private history. The [intake questionnaire](/blog/travel-agents-creating-a-travel-client-intake-questionnaire) helps identify the planning inputs actually needed. A complete fictional exercise can show how the adviser develops and reviews a route, while account secrets and real identity documents stay in the approved processes designed for them.

Try this prompt for a training exercise:

Explore a fictional travel plan for two adults who prefer a compact base and a slower daily rhythm. Compare two itinerary structures and identify the questions an adviser should verify before a real recommendation. Use no personal identifiers or account details. Do not invent prices, available services, supplier confirmations, client authority or bookings.

Review the output using Nowah's actual planning views and record the checked recommendation through the agency's process. The exercise can demonstrate planning fit without using real credentials or private documents. Any broader account or information requirement must be verified separately.

Explain the handoff to colleagues in terms of the work: current priorities, reviewed plan, open questions and next action. Do not describe a planning conversation as proof that another person has access or that a supplier has been notified. Keep the real access and service records authoritative.

## Test continuity without sharing secrets

Ask another authorised colleague to continue a fictional case from the agreed records. They should find the current information and know whom to contact if access fails. If the exercise depends on an unavailable person's credentials, resolve that process gap before relying on it for live service.

Review recovery procedures with the appropriate owner without exposing the recovery secrets in training material. The objective is knowing the legitimate route and responsibility. Follow the provider's current process if an actual incident or loss of access occurs.

Record issues and corrections in the inventory. If several services share the same ownership gap, address the pattern rather than treating each access problem as an isolated inconvenience. Keep the action proportionate to the actual service and supported arrangements.

## Keep client authority separate from system access

Being able to use an account does not establish the client's instruction for a particular action. A product may allow an authorised user to research or initiate a process while the agency still needs a specific approval before committing the traveller. Keep the actual decision record linked to the current arrangement.

Use two questions in a training case: who may access the system for this task, and who may approve the proposed service or additional expenditure? The answers may differ. Check both through the agency's actual process rather than letting technical access become an informal substitute for client authority. This distinction is especially useful during coverage handoffs and role changes.

## Maintain access as the agency changes

Use staff changes, role changes and new service use as review triggers. Check that account ownership, approved users and recovery responsibility remain accurate. A dated inventory is useful only when someone follows through on the open actions.

Practise a fictional Nowah itinerary handoff with the [agent-cover checklist](/blog/travel-agents-planning-cover-when-a-travel-agent-is-away), recording the reviewed plan and open questions in the agency's designated process. Keep account ownership and sign-in protection explicit when people change roles. This gives the team a workable route to continue planning while actual product permissions and human responsibility remain verified rather than assumed.

## Related guides for travel agents

- [Creating a travel agency team communication rhythm](/blog/travel-agents-creating-a-travel-agency-team-communication-rhythm)
- [Building a travel agency process improvement backlog](/blog/travel-agents-building-a-travel-agency-process-improvement-backlog)
- [Choosing travel agency software from actual workflow needs](/blog/travel-agents-choosing-travel-agency-software-from-actual-workflow-needs)
