← Back to blog

Multi-Property Permissions for Marina Groups

November 8, 2026
Multi-Property Permissions for Marina Groups

Multi-property permissions are the rules that decide which people can see and change which records at which marina in a group. Get them right and a dockmaster sees only their own docks, a regional manager sees several sites, and finance sees billing everywhere. Get them wrong and access either blocks daily work or stays open long after someone's role has changed. This guide shows how to design roles, scope them by location, test them and review them.

Atlantis Marina
Manage Marina Operations Across Properties
Atlantis Marina brings reservations, billing, customer records and daily operations together in one cloud-based system for multi-property marina groups.
Explore Atlantis Marina

TL;DR

  • Separate what a person can do (role) from where they can do it (property scope). Combining the two is the core of multi-property permissions.
  • Start from least privilege: each person gets the minimum access needed for their job, at the locations where they work.
  • Protect the records that carry real risk: customer identity data, payment data, vessel location and movement, and financial settings.
  • Review access on a schedule and every time someone changes role, season or employer. Seasonal staff and contractors are the usual gaps.
  • A single cloud platform for the whole portfolio makes one change take effect everywhere, instead of being repeated site by site.

Table of Contents

What multi-property permissions mean in marina operations

A single-site marina can get by with a handful of logins. A group with several marinas, a yacht club with satellite facilities, or a waterfront community with shared amenities cannot. People move between sites, vendors serve more than one location, and owners want portfolio numbers without being able to edit a slip contract.

In practice, multi-property permissions answer four questions for every user:

  1. Who are they? An employee, seasonal worker, contractor, owner or corporate finance user.
  2. What can they do? View, create, edit, approve, refund, export or delete.
  3. Which records and functions? Reservations, slip assignments, vessel records, documents, billing, ship store, fuel, lifts, cameras.
  4. At which properties? One marina, a chosen few, a region or the whole group.

The mistake most groups make is to answer only the first and last questions, handing out a generic "manager" title that works everywhere. That is convenient on day one and costly the first time a mistake or a departure exposes data nobody at that site needed.

Why the stakes are higher across a portfolio

Marinas hold more sensitive information than most operators assume. A March 2026 NexusTek article on marina data privacy lists personally identifiable information tied to memberships, long-term leases, emergency contacts and guest access, payment card data from slip fees, fuel, services and retail, and location and asset intelligence that can reveal vessel ownership, movement patterns and seasonal habits.

That last category is easy to overlook. A list of which boats are in which slip, and when the owners are away, is useful to a dockhand and valuable to someone with bad intentions. Permissions are how you make sure it only reaches people with a reason to see it.

Multiple properties add a second problem: drift. When each marina keeps its own accounts, a departure at one site does not propagate to the others. The same NexusTek piece points out that seasonal staff should not keep admin rights and contractors should not hold permanent access. In a group, those cleanups multiply by the number of locations.

The principle behind good permissions: least privilege

NIST defines least privilege as restricting users to the minimum access needed to accomplish assigned tasks. For a marina group, that translates into three habits:

  • Default to no access, then add what the job needs.
  • Grant by role, not by person. If you create custom access for each individual, nobody can later explain why a given person can do something.
  • Scope by location. A role is only half of a permission. The other half is the list of properties where it applies.

The payments world has the same idea built in. PCI DSS Requirement 7 limits access to cardholder data to people whose job requires it, which ISMS.online summarizes as a business need-to-know rule. If your marinas take card payments, your permissions model is part of your compliance story, not just an operations preference.

A role model you can adapt

The table below is a starting design, not a rulebook. Rename roles to match your organization. What matters is that each row has a clear purpose and a clear scope.

RoleTypical scopeCan doShould not do
Group owner or executiveAll propertiesView portfolio reports, occupancy and revenueEdit contracts or issue refunds day to day
Regional managerAssigned propertiesApprove exceptions, view all operations, run reportsChange company-wide billing settings
Finance or accountingAll properties, billing onlyReview invoices, payments, refunds, accounting syncReassign slips or edit vessel records
General managerOne propertyFull operations at that site, manage local staff accessAccess other properties
DockmasterOne propertySlips, arrivals, departures, waitlists, service requestsBilling configuration, refunds above a set limit
Dry stack or lift operatorOne property, launch and lift functionsLaunch queue, retrieval requests, lift statusCustomer financial records
Ship store or fuel staffOne property, point of saleRing sales, restock, fuel transactionsReservation edits, document access
Seasonal staffOne property, time-limitedOnly the tasks of the seasonAdmin rights of any kind
Contractor or vendorSpecific jobs or areasAssigned service requestsCustomer lists, permanent access

Two patterns are worth copying. First, financial power is separate from operational power: the person who can reassign a slip is not automatically the person who can refund a deposit. Second, group-wide visibility is usually read-only. Executives need numbers, not edit rights.

How to organize roles and access across properties

Five steps for organizing marina access

Step 1: Map your functions before your people

List the areas of your operation that need protection: reservations and waitlists, vessel records, documents such as insurance and registration, billing and refunds, ship store, fuel, lifts and dry stack queues, cameras and utilities, and reports. Group them into read, write and approve levels. This list becomes the vocabulary for your roles.

Step 2: Define roles from the work, not the org chart

Titles differ between a yacht club and a commercial marina. Build roles from tasks: "handles arrivals," "approves refunds," "runs the lift." A dockmaster who also staffs the fuel dock gets two role assignments, not an inflated super-role.

Step 3: Assign scope per property

For each person, name the properties where each role applies. Someone can be a dockmaster at one site and a read-only viewer at the sister site. Keep "all properties" for the few people who truly need it, usually finance and executives.

Step 4: Set approval limits

Refunds, adjustments, write-offs and contract changes carry financial risk. Require a second approver above a threshold you choose, and keep that approver at a level above the person making the request.

Step 5: Decide how access starts and ends

Write down who requests access, who approves it and who removes it. Tie removal to a trigger: end of season, end of contract, role change, termination. If access depends on someone remembering, it will eventually be forgotten.

Special cases that cause the most problems

Seasonal staff. Hiring spikes in spring and ends in fall. Create the accounts with an end date in mind and remove or deactivate them at season close. Never give seasonal workers admin rights because it is faster during a busy week.

Contractors and vendors. Electricians, lift technicians, fuel suppliers and detailers need access to a job, not to your customer base. Limit them to the specific service requests or areas they need, and remove access when the work is done. A marketplace of service vendors is easier to govern when vendors are scoped to the requests assigned to them.

Staff who rotate between sites. A floating dockmaster or regional manager should hold role assignments at each property they cover, and nothing at the ones they do not. When their coverage changes, you change the scope, not the person's account.

Physical and digital access together. Gates, lifts, cameras and utility controls are part of the same story. If a person leaves, both their software login and their physical credentials should end together. Our guide to access control for marinas and our overview of mobile access in marina operations cover that side in more detail.

Boaters across properties. Customers are a different category from staff, but the same logic of one identity applies. A boater who keeps vessel details, insurance and registration documents in one account should not have to resubmit them at every marina in the group. The boater account platform is built around one account that travels across the Atlantis Marina Network, while each marina still controls what its own staff can see and do.

Special cases that cause the most problems

Security and compliance considerations

Access permissions are one of the cheapest and most effective controls a marina group has. Consider these areas:

  • Payment data. If you accept cards, PCI DSS applies. Limit who can view, refund or export payment information, and keep card data with the payment processor rather than in your own records. Our explanation of marina payment processing and our piece on preventing marina payment fraud go through what operators control and what the processor handles.
  • State privacy and breach laws. NexusTek notes that marinas may fall under state privacy laws and breach notification laws that are enforced in all 50 states. Requirements differ by state, so a group operating in several states should ask its attorney which rules apply to each property.
  • Multi-factor authentication. Require it for anyone with administrative, financial or multi-property access.
  • Audit trails. You need to be able to answer who changed a contract, who issued a refund and when. That matters for incident reviews and insurance questions.
  • Third-party access. As data moves between your marina software and service providers, visibility gets harder. Keep a list of every integration and who administers it.

Testing permissions before you rely on them

A permissions model that has never been tested is a guess. Before rolling it out to the group:

  1. Create a test user for each role and sign in as them.
  2. Try what they should be able to do, and confirm it works without a call to the office.
  3. Try what they should not be able to do, such as opening a different property or issuing a refund, and confirm it is blocked.
  4. Check exports and reports. Data leaves through reports as often as through screens.
  5. Test a departure. Deactivate a sample user and confirm their access ends everywhere they held it.

Repeat the test after major changes: a new property, a new module such as dry stack or fuel, or a reorganization.

Reviewing access as people and responsibilities change

NexusTek recommends role-based permissions, MFA and quarterly access reviews as part of a sound approach. A review does not need to be elaborate:

  • Quarterly: export the list of users with their roles and properties. Ask each general manager to confirm every name still belongs.
  • At season change: deactivate seasonal accounts and review contractor access.
  • At every role change: treat it as a removal plus a new grant, not an addition. People who get promoted tend to keep old access they no longer need.
  • After incidents: review who had access to the affected records.

Keep the review result: a dated list of who was checked and what was changed. It is the evidence that your policy runs in practice.

Perspective: why one platform beats site-by-site accounts

We built Atlantis Marina for operators who run more than one dock, and permissions are where a unified system pays off fastest. When every marina in a group lives in one cloud platform, with slips, lifts, dry storage, billing, documents, customer accounts and connected devices in the same place, access can be managed once and applied consistently.

The alternative is fragmented tools. One system for reservations, another for payments, a separate lift controller, a separate camera dashboard. Each has its own user list, and each needs its own cleanup when someone leaves. That is where forgotten accounts come from.

Our view is that operators should think of access as part of operations, not as an IT chore. A dockmaster who sees exactly what they need works faster. A finance lead who sees billing across the group closes the month faster. An executive who sees portfolio numbers makes better decisions. And the less manual entry and duplicate accounts you have, the less there is to go wrong.

If you manage a group, begin with roles built from tasks, scope them by property, and review them on a schedule. Then choose software that makes that model easy to keep.

John R

Run your whole group from one platform

Atlantis Marina brings marina management, boater self-service, billing and payments, ship store POS, lift and dry stack operations and connected devices into one cloud system for independent marinas, yacht clubs and multi-property groups. You can see how it works on our marina management solution page, or review the published plans, which start at $150 per month for Micro, $300 for Small, $500 for Medium and $900 for Large, with Enterprise on request, on the pricing page.

Atlantis Marina

If you manage several properties, talk to us about marina management software and we will walk through how your roles and locations would be organized.

A starting checklist for your group

  • List every function that handles customer, payment or vessel-location data.
  • Define roles from tasks, and keep financial approval separate from daily operations.
  • Assign every user to named properties, and reserve "all properties" for finance and executives.
  • Require MFA for admin, finance and multi-property users.
  • Set end dates for seasonal staff and contractors when you create their accounts.
  • Test each role, including a departure, before launch.
  • Review access quarterly and at every role or season change.
  • Align physical credentials with software access so both end together.

FAQ

What is the difference between a role and a property scope?

A role defines what someone can do, such as view reservations or approve refunds. A property scope defines where that role applies. A dockmaster role scoped to one marina gives full dock operations there and nothing at the other sites.

How often should we review access across properties?

At least quarterly, and also whenever someone changes role, a season ends or a contractor finishes a job. Quarterly reviews are a common recommendation, as in the NexusTek guidance. Ask each general manager to confirm their own site's user list.

Who should have access to all properties?

Only people whose job truly spans the group, typically executives for read-only reporting and finance staff for billing. Everyone else should be scoped to the specific marinas where they work. Keeping the all-properties list short makes reviews fast and limits exposure.

Should contractors get accounts?

If they need system access, give them a narrow role limited to assigned jobs and remove it when the work ends. They should not see customer lists or hold permanent logins. Tying their access to specific service requests keeps it contained.

Do permissions affect payment compliance?

Yes. PCI DSS expects access to cardholder data on a business need-to-know basis. Limiting who can view, refund or export payment information supports that. For how it applies to your marinas, consult your payment processor and a qualified compliance professional.

Sources