# Configure shared business and local restaurant settings

For the authorised owner and manager. Confirm the business and working location
before editing. Shared company identity, catalogue, roles and suppliers are not
separate copies for each branch; local service, address, devices and reports
have their own settings.

1. Review [Business General](/settings/business/general): identity, regional
   defaults, account contact and the entity invoiced for TablePort. Some fields
   are read-only for operators; use the authorised support route when needed.
2. Review [Legal entities](/settings/business/legal-entities) and each
   location's Accounting Profile. A shared owner does not establish another
   company's document, provider, billing, or data authority.
3. Find or [Add location](/settings/location/locations) through the supported
   form. A new location requires the appropriate legal entity and operational
   setup; check saved state before creating another after a timeout.
4. Configure [Local General](/settings/location/general),
   [Address/delivery](/settings/location/area-delivery), intended
   hours/channels, service/tip presentation and report recipients.
5. Set the [Shared restaurant brand](/settings/business/brand), then
   [Local storefront/QR/receipts](/settings/location/brand) where needed. Shared
   brand, wallet artwork and website publishing have separate saves/outcomes.
6. Connect only the [Authorised integrations](/settings/business/integrations)
   for this business and environment. Verify local assignment and actual
   capability rather than treating a saved record as readiness.
7. Configure menu, tables, stock, team and bookings using
   [First-service preparation](/guides/onboarding), then test the intended
   flows.

When adding a location, verify its name/type, legal entity, enquiry email and
device-login mobile. Staff credentials and public guest contact are different.
Do not copy another branch's integration, address, or policy merely to complete
an empty form.

After each save, reopen the same record and inspect the affected guest/staff
surface. A failed load should preserve the existing configuration, not lead to
saving blank defaults. Reset, deletion, provider disconnection and live-mode
changes are consequential actions—not generic error recovery.

Escalate with business/location, section, intended change, saved result and
exact error through an authorised channel. Keep company, guest, staff and
financial records within their proper access boundary.