Elcom CMS: public content and access controls
Assess Elcom CMS for retail publishing. Check public pages, editor workflow and permissions, while distinguishing internal portals and private records.
- Published
- Last updated
Elcom CMS supports public websites alongside restricted portals and intranets. For a retailer, it fits a publishing brief when the proposed templates let editors maintain buying guidance and store policies with controlled approval. Keep the public website’s content boundary explicit wherever the same platform also holds private information.
Identify the Elcom products in the proposal
Separate the public website from each restricted experience in the Elcom proposal. Elcom describes its Digital Experience Platform as the underlying CMS for websites, portals and intranets. Sharing a platform doesn’t give those experiences the same audience or publication rules.
The Elcom website CMS is the public publishing part of this assessment. A customer or member portal is a signed-in destination for its defined users. An intranet holds staff-facing material. A retailer can need more than one, but the contract must name each component and its purpose.
Use a scope sheet with one row per experience. Record its audience, domain, content owner and included modules. Add the proposed platform version and any custom templates. This prevents a portal demonstration from being treated as proof of the public website’s finished editorial workflow.
For example, public delivery guidance and a supplier portal can sit within one wider programme. The delivery page needs readable instructions for any shopper. Supplier price schedules belong behind the access rules agreed for suppliers. They need separate acceptance checks even when one team maintains both.
Review the retail publication workflow
Assess Elcom’s publishing workflow through a representative buying guide in the proposed page template. Elcom’s CMS features describe templates linked to master pages, article review before publication and version control with rollback. Structured Authoring is listed as an optional module that creates articles from form values and can use approval workflows.
Those capabilities support an editorial process, but your configured fields and permissions decide what editors can actually publish. Use the implemented guide template to follow this sequence during acceptance.
- An editor creates a draft guide. Its fields capture the shopper’s question, category advice, images and links to the relevant range. Decide which fields are required and which an editor can change.
- A reviewer checks the advice against the products and policies it describes. Route approval to the person responsible for that category. Keep an ordinary author from bypassing the agreed approval step.
- The publisher releases the approved guide. Open its public URL without signing in and compare the displayed text with the approved content. Include headings, image descriptions and any linked policy documents.
- Change one instruction and follow the same review route. Confirm which version visitors receive after publication, then practise restoring the earlier approved version.
Consider an illustrative guide to choosing a dining table. The editor can explain seating capacity and care requirements in the guide’s fields. The template must display that advice beside the intended range links. A blank care field needs an agreed outcome, such as stopping publication or omitting the empty section. Leaving that decision to each editor creates inconsistent pages.
Keep the acceptance evidence tied to the actual template and author role. A feature demonstration on a different site doesn’t establish the result for your retailer.
Keep public knowledge separate from restricted records
Public store knowledge must reach shoppers without carrying staff, customer or member records with it. Elcom’s portal documentation says modules respect configured permissions and access levels. It also describes permissions on folders and documents that limit what user groups see in search.
Treat those controls as something the implementation must preserve across every route to content. Test the public page and its attachments as an anonymous visitor. Repeat with an ordinary staff or member account where relevant. A restricted document must remain restricted when someone opens its direct address, not only when they browse the portal menu.
For downstream search or generated answers, define the permitted public source set before connecting retrieval. Approved sizing advice and public returns rules can enter that set. Customer correspondence, supplier terms and staff procedures stay outside it. Use a connection identity whose access matches that public-only job, and test what the connection can retrieve.
An illustrative error is a public buying guide that links to an internal care manual containing supplier terms. The safe publication is a separately approved public care guide, with its own public attachment if needed. Removing the internal link leaves the original manual’s access controls necessary.
Also define withdrawal behaviour. If a policy leaves the public site, a connected index must stop returning its old text. Put that requirement beside the broader CMS security controls in your acceptance plan.
Scope integrations and ownership
Assign an owner to each content connection and each operating responsibility in the Elcom agreement. Elcom documents a REST application programming interface (API) and a Microsoft .NET software development kit (SDK) for custom integrations. Their existence establishes a development route, not a ready-made connection for a particular shopping service.
For each proposed connection, specify the content objects it reads or changes, its direction and its authentication. Record how permissions are applied, how changes reach the destination and how deletions are handled. Include linked documents in that scope. A page export that omits attachments can leave a buying guide incomplete.
Elcom’s frequently asked questions describe vendor hosting, internal hosting and hosting through another provider. Its hosted subscription model includes ongoing maintenance, security upgrades, upgrade services and support. The responsibilities in your proposal must match the hosting model you choose.
Get written ownership for backups and recovery, platform updates, custom-template compatibility and support escalation. Define who fixes a broken publication or integration after an upgrade. Agree the export deliverables too, including content, documents, metadata and the information needed to preserve public URLs.
Compare the proposed scope with other CMS platforms on those same responsibilities. Select Elcom when its configured public publishing workflow and access boundaries meet the retailer’s requirements, and the agreement names who maintains them.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.