Administration, permissions, and advanced code

Configure PageDesigner settings, assign least-privilege permissions, understand license behavior, maintain the AI queue, and control page-level code.

This page is for the Paymenter owner, role administrator, or developer responsible for PageDesigner.

Administrative responsibilitiesCopy Anchor Link

• Install and upgrade the extension.
• Maintain the license and Hosted settings.
• Assign PageDesigner permissions.
• Run the queue worker for durable AI jobs.
• Review shared/public packages.
• Control MCP tokens.
• Review custom components and page-level executable code.
• Back up and recover PageDesigner tables.

Extension settingsCopy Anchor Link

Hosted and licenseCopy Anchor Link

UpdatesCopy Anchor Link

Direct AI providerCopy Anchor Link

PermissionsCopy Anchor Link

PageDesigner registers:

The default administrator role receives the PageDesigner permissions during install/upgrade unless it already uses wildcard access.

Recommended role patternsCopy Anchor Link

Page reviewerCopy Anchor Link

• View.
• Update only when the reviewer is expected to edit.
• No delete, sharing, custom component, AI Full access policy, license, or MCP management.

Page editorCopy Anchor Link

• View, create, update.
• Hosted view/download as needed.
• Custom component manage only for trusted component maintainers.
• AI use when the organization permits AI processing.

PublisherCopy Anchor Link

• View and update, with an organizational publishing approval process.
• Page sharing only when this role owns distribution.

PageDesigner administratorCopy Anchor Link

• All relevant permissions, including license, updates, and MCP.
• Limit this role to trusted administrators.

License and offline behaviorCopy Anchor Link

The locally stored signed grant is bound to the license-key hash and install UUID. It contains entitlement and timing data and is verified with bundled public-key material.

When the Hosted service cannot be reached, a previously verified grant can authorize management only through its signed offline-grace deadline.

Already-published local pages continue rendering when management is blocked. This avoids turning a licensing or Hosted outage into a storefront outage.

Queue worker for AICopy Anchor Link

AI runs dispatch ProcessAiRun jobs to Laravel's configured default queue.

Operational requirements:

• Run a persistent queue worker.
• Monitor failed jobs.
• Restart workers after relevant deploys.
• Allow jobs longer than the configured provider timeout; PageDesigner jobs allow up to 300 seconds.
• Avoid a restrictive queue allow-list that excludes the default queue used by the application.

Each job makes one model-response step, checkpoints it, and dispatches the next step when necessary.

Page-level Custom CodeCopy Anchor Link

The page record contains five slots:

Normal editor policyCopy Anchor Link

Leave these slots empty unless a trusted developer has provided and reviewed the exact content.

Review requirementsCopy Anchor Link

• Read the existing slot before changing it.
• Keep a backup of the previous value.
• Understand public execution and data exposure.
• Prefer append for a new independent script.
• Replace only with explicit intent and complete review.
• Use head scripts only when load timing genuinely requires it.
• Do not duplicate SEO tags already managed by PageDesigner.
• Avoid selectors or scripts that affect the Paymenter shell globally.
• Test signed-out, mobile, and both themes.

Page deletion and bulk deletionCopy Anchor Link

Deletion is permanent in the normal page list and MCP requires explicit confirmation. Before deletion:

• unpublish when temporary removal is enough;
• inventory inbound links;
• save a reviewed share/export or database backup when recovery may be needed;
• confirm the page is not a source for an active campaign;
• ensure bulk selection is correct.

Sharing governanceCopy Anchor Link

Define who may:

• share unlisted packages;
• publish a package to Page Marketplace;
• import community packages;
• approve custom code contained in a page package;
• redistribute media and copy.

Imported pages must remain drafts until review.

Backup and recoveryCopy Anchor Link

Back up the database before:

• extension upgrades;
• uninstall;
• bulk deletion;
• major MCP or Full access AI migrations;
• schema or infrastructure changes.

Retain the PageDesigner ZIP that matches the backup.

For rollback, restore the database and previous ZIP together. Do not selectively delete or recreate PageDesigner tables.

Audit and diagnosticsCopy Anchor Link

PageDesigner records hosted lifecycle, download, sharing, import, AI, and related events in its audit table when available. Application logs and the hosted diagnostic response are also important.

Do not include raw secrets in tickets or screenshots. Redact:

• license keys;
• custom AI keys;
• MCP tokens;
• Authorization headers;
• private package links;
• customer data.

Security checklistCopy Anchor Link

• HTTPS application URL is correct.
• Public server IP is correct when required.
• Stable update channel is used in production.
• Page editor roles have least privilege.
• Queue workers are monitored.
• Direct provider uses HTTPS.
• Custom components are reviewed as code.
• Page-level scripts contain no secrets.
• Each MCP client has a separate token.
• Unused MCP tokens are revoked.
• Public marketplace sharing has an approval owner.
• Database and previous ZIP backups exist.

---