One customer, many properties: give every person the right portal access

Keep the customer and each site distinct

Use the company account for the overall relationship and separate service locations for the places where work happens. Record useful location details consistently: building name, unit or equipment reference, access contact and the customer's work order or purchase order number when provided. That makes a request recognizable to both office teams.

CrewBarn supports customer service locations and equipment history across sites. A technician can open the relevant record before arriving, while the office can connect new work to earlier visits. Do not rely on a company's main mailing address to explain which building actually needs service.

Invite people around their responsibilities

List who reports issues, who approves work and who handles invoices. Those may be three different people. A front-desk employee needs a reliable way to submit a request; a manager needs visibility over the properties they oversee; accounting needs the records required to reconcile charges.

CrewBarn's customer portal supports company-team logins and role-based access. Review the permissions with the customer when inviting people. Keep individual accounts current when someone changes roles or leaves, rather than leaving an old shared login in circulation. Access should follow current responsibilities.

Make approval an explicit handoff

A maintenance request does not necessarily authorize every repair a technician discovers. Agree who can approve the scope and spending before dispatch. Keep the quote, customer reference and supporting photos together so the approver can make a decision without reconstructing the request from several messages.

CrewBarn connects requests, quotes, approvals and the job record. Office staff can see the work in context and follow up with the appropriate person. If a visit needs to change, keep the customer's request and the office's confirmed schedule separate until the change is approved.

Give billing a record it can reconcile

An invoice should identify the customer, service site and relevant job or purchase-order references. When one customer has many locations, that detail matters more than another summary email. Keep completed scope, approval and the financial record connected so questions can be answered from the same history.

Use the portal rollout as a small operating agreement: confirm the customer's contacts, test a request and approval, then walk accounting through an example invoice. CrewBarn can keep the record together, but clear responsibility still depends on the people using it. Review that arrangement as the customer's organization changes.

A handoff checklist for your team

• Is each property recorded as its own service location?
• Who can report work, approve scope and review invoices?
• Are customer work-order and purchase-order references captured?
• Does each person use their own account with appropriate access?
• Can accounting trace an invoice back to the site and approved job?