Dazos enables it for the instances that have contracted it. This guide explains what you see when it is not part of your plan, what happens to pages you had already built, and what changes when it is enabled.
Contents
1. Before You Start
2. When Landing Pages Is Not in Your Plan
3. If Your Instance Had Already Built Pages
4. When the Feature Is Enabled
5. Frequently Asked Questions
1. Before You Start
You will need:
An iCampaign user with access to the Landing Pages module (the same role permissions as before).
Access requirements: the module is available when your instance's plan includes Web / Landing Pages. Your own role permissions still apply on top of that: a user who could not create pages before still cannot.
If Landing Pages is not part of your plan and you want it, contact Dazos Sales; the feature is switched on for your instance without any change on your side.
2. When Landing Pages Is Not in Your Plan
The Landing Pages entry stays in the left menu. If your instance has never created a page, opening Pages or Templates shows the message below instead of the module, with a link to contact Sales.
Typing the builder's address directly shows the same message: the builder cannot be reached while the feature is off.
3. If Your Instance Had Already Built Pages
If your instance created pages before the feature was switched off, Pages and Templates still open, in read-only mode, in every workspace of the instance.
Control | What it does now |
Amber notice at the top | Explains that the module is disabled and how to enable it again |
New Page, Create Page, Delete | Greyed out; hovering shows the reason |
Row selection boxes | Greyed out; hovering shows the reason |
Preview (row menu) | Still works: you can open any page in a new tab |
Edit, Publish, Duplicate, Save as template, Use template, Delete (row menu) | Greyed out; hovering shows the reason |
Page names | Shown as text, no longer a link to the builder |
Important: nothing is removed. Your pages and templates are kept exactly as they were, and pages you had published keep working at their public addresses.
The Templates screen behaves the same way: you can preview templates, but Use template, Duplicate and Delete are greyed out.
A workspace of the same instance that has no pages of its own shows an empty list with the same notice.
4. When the Feature Is Enabled
1. Reload the page.
2. The notice disappears, New Page and every action in the row menus work again, and your previous pages are in place.
There is nothing to configure on your side; the change is made by Dazos and applies immediately.
5. Frequently Asked Questions
Q: I see Landing Pages in the menu but it says the module is disabled. Is something broken? No. The entry is always shown; the message means Landing Pages is not part of your instance's plan and your instance has not built pages yet. Contact Sales to enable it.
Q: We used Landing Pages before and now everything is greyed out. Did we lose our pages? No. You are in read-only mode: your pages and templates are kept, published pages keep working, and you can still preview everything. Only creating, editing, publishing, duplicating and deleting are paused until the feature is enabled again.
Q: Why is Preview the only action that works? So you can keep reviewing what you built. Preview reads the page; the other actions would change it.
Q: My workspace shows an empty list with the notice. Why? Your instance has pages in another workspace, so every workspace keeps read access. Yours simply has no pages of its own.
Q: Do we need to do anything when Dazos enables the feature? Just reload the page. No settings, no restart.
Q: Does this affect campaigns, subscribers or social media? No. The setting only concerns the Landing Pages module.
Need Help?
If you run into issues:
Confirm with your administrator whether Web / Landing Pages is part of your instance's plan. Contact Dazos support with your instance name and a description of what you see.