Connect. Secure. Manage.
Meraki Organisation Design
Structure Meraki organisations and networks around business ownership, licensing and operational boundaries before deploying or consolidating sites.
Devices supported
across the UK
Client locations
supported
Traffic handled
at peak time
Average
response time
Average response is not a resolution time or a contractual guarantee. Support scope and response commitments are agreed for each engagement.
Meraki organisation design sets the account, device and support boundaries before sites are added. We help you choose a structure that can cope with growth, a new provider or a business split. Each organisation and network has a clear purpose. The design should support today’s work and make future changes easier to plan.
Dashboard clarity
Structure organisations, networks and permissions around real operational ownership.
Consistent sites
Use repeatable standards without ignoring the differences between locations.
Practical operations
Keep cloud management connected to physical links, users and business services.
Start with ownership rather than geography
We find the companies, business units and service providers involved, then establish who should own and administer each part of the estate. Several offices may belong in one organisation, while two businesses sharing a building may need separate ownership. The decision should account for legal control, commercial responsibility and the ability to hand equipment or services back later. Physical proximity alone does not answer those questions.
Licensing and support arrangements are reviewed alongside access. We record the applicable subscription model, renewal duties and restrictions relevant to a proposed move. A new structure must not assume that devices, entitlements and historical information can all transfer together. Where a vendor or account team needs to confirm a commercial dependency, that confirmation becomes a prerequisite rather than a task left until the cutover.
Standards & partnerships
Confidence in the team behind your network.
Cisco Partner
Cisco Meraki
Cyber Essentials
Cyber Essentials PlusMCI Network Services is operated by Proxar Ltd. Certifications apply to the certified legal entity and the scope of its certificates. View accreditation information
Decide what a dashboard network represents
Within the organisation, we define how networks correspond to sites or services. A branch may use a combined network for its supported device types. But a campus can require a different arrangement. We consider operational visibility, setup ownership, templates and wireless mobility needs before selecting the boundaries. Dividing a campus purely to make the menu shorter can create inconvenient dependencies for teams managing the wireless estate.
The design includes naming conventions and stable identifiers that survive staff changes. Names should distinguish a building from a business unit and an operating setup from a project. We also document whether a tag describes a location, technical role or support group. Mixing those meanings makes filtering unreliable and increases the chance of applying a bulk operation to the wrong devices.
A useful starting point
Not sure where to start?
Bring the requirement. We will help you define the engineering work.
Model permissions and recovery
A proposed structure should be tested against everyday support tasks. Can a local engineer investigate one branch without receiving access to unrelated customer networks? Can the central team manage shared settings? Who can recover access if the usual administrator is unavailable? We turn those questions into a permissions matrix and review the relevant dashboard capabilities rather than assume that every desired boundary has a matching built-in role.
Identity integration is a separate design decision. An identity-provider group may grant access across several organisations, so changing that group can affect more than the immediate project. We set out the approval owner and recovery process for these links. Our dashboard access-control review can then check the resulting permissions against the intended model and expose privileges inherited through unexpected routes.
Different environments. The same care.
Built around the work
your network supports.
Finance, banking and the wider private sector. We start with the systems and people that depend on your connections.
Finance & banking
Market-data paths, routing and provider coordination on clients’ behalf.
Financial-market services ↗Offices & multi-site teams
Reliable access between people, workplaces and business applications.
Office network design ↗Data centres & cloud
Network boundaries, workload connections and operational ownership.
Data centre networks ↗Consider growth and separation together
The structure should accommodate new sites without requiring a fresh design every time. We develop repeatable site patterns while identifying the circumstances that justify an exception. A larger branch with local servers, a shared tenant network and a small sales office may share a naming convention but require different setup controls. Consistency should make differences visible, not conceal them beneath one universal template.
We also work backwards from a possible exit. A future divestment, provider change or relocation may require part of the estate to move. We identify dependencies that would complicate that move, including shared authentication, VPN relationships, integrations and licence ownership. This does not mean designing around every hypothetical acquisition. It means avoiding easily foreseeable dependencies that would make customer control unnecessarily difficult.
Validate before restructuring production
For a current rollout, we first capture the current organisation and network map. We compare the intended destination with settings that may not transfer automatically and agree what information must be retained for operational or audit purposes. A trial with non-critical equipment can expose unsupported assumptions before a large migration. Any destructive action, network removal or device reassignment needs a clear approval and a recovery plan.
Acceptance is more than seeing the devices in their new location. We check admin access, intended settings, alert delivery and representative service network access. We also check that previous access has been removed where agreed, while customer recovery access remains available. The final record explains which settings were retained, rebuilt or deliberately changed so that later fault investigations start from an accurate baseline.
What the design engagement delivers
You receive a proposed organisation model, network inventory, access duties and a rollout sequence with outstanding dependencies. Where the current structure is adequate, the recommendation may be to keep it and improve documentation rather than undertake a disruptive consolidation. Our Meraki organisation consolidation service covers the rollout assessment when a move is justified. MCI’s role is to leave ownership clearer and future administration more predictable, not to create extra organisations without a business reason.
Technical references
- Organisation settings — Cisco / Cisco Meraki
- Managing dashboard administrators and permissions — Cisco / Cisco Meraki
Talk to a specialist
What does your network need next?
Tell us what you are planning, changing or trying to improve. We will help define a practical next step and the engineering scope.
+44 203 196 6566Choose option 1
sales@proxar.co.ukUK-wide service.
Most of our engineers are based in Kent, with a focus on London, Sussex, Essex and Berkshire.
Existing customers should use their agreed support and escalation channels. This form is for service enquiries, not a monitored emergency ticket.
Tell us what you need.
A short outline is enough. Please do not include passwords or sensitive network details.
Thank you. Your enquiry has been submitted.
Please check your name, email and message, then try again.
Your form session expired. Please try again.
Please wait a minute before sending another enquiry.
We could not submit your enquiry. Please call or email us instead.