CityEngine coordinates the network
CityEngine connects city websites, business identities, assigned markets, customer activity, media, and publishing. Network staff use the existing controls to manage shared access, approvals, and operations.
How it works
Shared relationships. Independent city operations.
Each city has a complete local website, content tools, business workspaces, and a Wire newspaper edition. CityEngine connects the shared business and publishing work while each city keeps its local operation.
The operating architecture
Clear responsibility at the network, business, and city levels.
Each city operates locally
The local platform keeps its own domain, business community, content management, and newspaper edition. Its team manages local information and the workspaces assigned to businesses and editors.
The client works across markets
One business, one login, one office, many markets. Master business identity and market assignments connect the client relationship with the cities involved.
Choose the relevant markets.
Use the network map or directory to find the city websites involved. Visit their public pages and Wire editions, then choose the communities your business or story actually serves.
Describe the business or project.
Tell us which business or publication is involved and what you want to manage: website content, images, offers, customer requests, email follow-up, or a Wire story for selected editions.
Confirm scope and responsibilities.
Discuss the participating markets, business relationship, proposed activity, account access, timing, and commercial details. Identify the network responsibilities and the local city responsibilities involved.
Use the appropriate entry point.
Existing CityEngine clients use Client Login. Authorized editors use Editor Login. Staff with network authorization use Network Control. A city-issued business account may use that city's own login.
Keep the work connected to its local context.
Review business identity, market assignments, local details, media permissions, and the intended customer action. Updates and support requests should identify the business, affected market, and relevant lead, booking, campaign, or content.
A clear route for each role.
Business owners and clients
Use your existing client access for the business relationship and markets assigned to it. The multi-market model is one business, one login, one office, many markets.
Client LoginLocal city teams
Keep responsibility for your city’s local operation while coordinating shared relationships and activity with the network. Use the access already assigned to your role.
Discuss a cityEditors
Use the separate Wire editor workspace for the newsroom work assigned to you. Story destinations, publisher approval, and each edition’s publication status determine where content appears.
Editor LoginNetwork operations staff
Use Network Control when authorized for network operations. Include the relevant city, business relationship, and operational or audit context in your request.
Network ControlA local website with the right access for each role.
Visit a city website to explore its local businesses and newspaper. Business account access, campaign availability, and published Wire stories follow their own permissions and release status.
A displayed market does not automatically confirm a business placement, campaign, editor assignment, or account permission. Confirm the work and availability with the team before planning around it.
Read common questionsBring the right context to the conversation.
A business name, city domain, and short description of the work are a useful starting point.