Skip to main content

Enable Web / Landing Pages per Instance (iCampaign)

As a Dazos administrator you can now switch the Landing Pages module on or off for each iCampaign instance from the client's plan settings, the same way you already control SMS or Social Media.

The change reaches the instance immediately, and every change is recorded with who made it and when.

Contents

1. Before You Start

2. Open the Client's Plan Settings

3. Enable or Disable Web / Landing Pages

4. See Which Instances Have It

5. What the Instance Sees

6. Audit Trail

7. Frequently Asked Questions

1. Before You Start

You will need:

Access to the Dazos Admin panel with permission to edit clients (Plans Management). The name of the instance whose plan you are changing.

Access requirements: any administrator who can edit clients can change the setting. Reading the audit trail (Logs) is limited to super administrators.

There is nothing to set up on the instance itself. If the setting is not visible in the client form, ask the Dazos team to confirm the admin panel has been updated.

2. Open the Client's Plan Settings

From the Dazos Admin, go to Plans Management → Clients. Click the instance name, or open its row menu and choose Edit.

The client form has these blocks:

Block

What it holds

Client Identity

Instance name, business and legal names, domain

Kafka

Configuration

Messaging prefixes used by the integration

Integration URLs

CRM and iCampaign addresses, SSO key

Features

The plan switches: SMS, MMS, Conversation, Forward, Social Media and now Active Web / Landing Pages

3. Enable or Disable Web / Landing Pages

Scroll to the Features block at the bottom of the form.

Control

Purpose

Active Web / Landing Pages (unticked)

The module is not available on the instance

Active Web / Landing Pages (ticked)

The module is available on the instance

1. Tick the box to enable the module, or untick it to disable it. There is no quantity to enter: the feature is either on or off.

2. Click Update at the bottom of the form.

3. You are returned to the Clients list. The instance follows the new setting right away; no deployment or restart is involved.

Tip: New instances start with the box unticked. If a client contracts Landing Pages later, come back here and tick it.

4. See Which Instances Have It

The Clients list now has an Active Web column that reads Yes or No for every instance.

To list only the instances with (or without) the feature:

1. In the filter row under the headers, open the selector under Active Web and choose Yes or No.

2. Click Search Data (the green magnifier at the left of the filter row).

3. Click Clear Filters (the eraser) to see the full list again.

Important: if you had saved your own column set for this list before this change, the new column is hidden for you. Open Manage Columns (the icon at the top-left of the table) and turn on Active web.

5. What the Instance Sees

Setting

What users of the instance get

Enabled

The Landing Pages module works normally: Pages, Templates, the builder and publishing.

Disabled,

never used

Landing Pages stays in the menu; opening Pages or Templates shows a "Landing Pages Module Disabled" message with a link to contact Sales. The builder cannot be reached, not even by typing its address.

Disabled

after use

Pages and Templates open in read-only mode with an amber notice. Users can review and preview what they built, but creating, editing, publishing, duplicating and deleting are greyed out with the reason. Nothing is removed, and pages that were already published keep working.

6. Audit Trail

Every time the box is changed and saved, one line is written to Logs (main menu, super administrators only):

Web / Landing Pages enabled for instance "acme" by admin (user #1) — with the date.

Saving the client form without touching the box writes nothing, so the Logs screen only shows real changes.

7. Frequently Asked Questions

Q: Does disabling the feature delete the client's pages? No. Their pages, templates and published versions are kept exactly as they were. They only lose the ability to create, edit, publish or delete until the feature is enabled again.

Q: Do I need to ask for a deployment after ticking the box? No. The instance reads the setting every time someone opens Landing Pages, so the change is effective as soon as you click Update.

Q: Can I limit the number of pages or domains? Not with this setting. Web / Landing Pages is a single on/off switch charged as one service; there is no per-page or per-domain quantity.

Q: What happens when I duplicate an instance? The copy starts with the same Active Web setting as the original. Review it in the new client's form if the new client has a different plan.

Q: Who can see who changed the setting? Super administrators, in the Logs screen. Each line names the administrator, the instance and the date.

Q: The column is missing from my Clients list. You saved a custom column set before this change. Open Manage Columns and turn on Active web.

Need Help?

If you run into issues:

Check the Logs screen to confirm the change was recorded. Contact the Dazos team with the instance name and the time of the change.

Did this answer your question?