VF StudioVFUSION STORAGE WORKSPACE
ADMINISTRATION

Accounts

Everyone with access to Studio. Manage roles, passwords and account access here.

0Total accounts
0Active admins
0Marketing members

New user setup

  1. You choose a username, role and temporary password.
  2. The user signs in and chooses their own password.
  3. They scan their own MFA QR code and save their recovery codes.

Role permissions

Marketing manages SEO and Google tools.

Admin manages content, accounts, integrations and release approval.

Account changes require your password and a fresh authenticator code. Each verification authorises one account change. Password resets keep the user's existing MFA.

Create an account

Choose the initial sign-in details. The user must replace the temporary password and set up their own MFA before accessing Studio.

Reset password

The user must change this password at their next sign-in. Their existing MFA stays active. Previous sessions will be signed out.

Change account role

Marketing manages SEO and Google tools. Admin can manage all CMS functions. Changing a role signs out the user's existing sessions.

SEARCH VISIBILITY

SEO

Manage search titles and descriptions. Page content and layout stay protected.

Choose a page

Search appearance preview

An admin reviews drafts before release. Publishing remains your existing deployment workflow.

VFUSION STUDIO

Sign in to your workspace.

Individual accounts. Private drafts. You control the release.

Local trial on this machine. No content is uploaded.

REVIEW BEFORE RELEASE

Inspect the saved changes

Approval copies this draft into the approved release content. It does not publish the website.

Revision history

Restore an earlier version as a new draft. Approved releases are not overwritten by a restore.

Your account

Authenticator verification is mandatory for every account. Store your recovery codes privately. Factor replacement requires the offline owner recovery process.

MARKETING WORKSPACE

Google Marketing

Choose your tools. Keep control of credentials, consent and website releases.

Setup documentation   Open in Google

Private credentials

Encrypted in the private Studio store. Saved values cannot be viewed or exported. Leave blank to keep; select Remove to clear.

Preview approved visitor choices

Connection and reporting

Tracking is disabled inside Studio and all local previews. Live tags require visitor consent. Enabling a shortcut does not implement an API connection. Google account permissions, approvals and API quotas still apply.

Review public Google settings

Only these public IDs and switches enter the website build. Private credentials stay in Studio. This does not deploy anything.

Currently approved

Proposed release

WEBSITE DESIGN

Appearance

Choose your website colours. The layout, content and image sizes stay the same.

Website theme

Animated accents and entrance effects are available in both themes. Reduced-motion preferences are respected.

Preview selected theme ↗

Discard this theme selection?

Your saved website theme will stay as it is.

Verify your identity

Complete the verification steps below. Your pending action will continue automatically when verification is finished.

Information saved

WEBSITE INFRASTRUCTURE

Cloudflare

See what protects your site. Prepare changes with a clear approval boundary.

Private connection

Use a zone-scoped read-only API token. Saved secrets are masked; blank keeps the stored value.

Website integrations

Use manual beacon installation in Cloudflare. Automatic injection would duplicate it. Review your visitor notice before release.

The PHP host needs the matching secret outside its web root. Enabling locally does not install it on your host.

Include in the proposed edge configuration

These choices prepare a plan. They do not change live settings.

Observed Cloudflare configuration
Proposed edge changes

Cloudflare tools and integration status

Review public Cloudflare settings

Only public beacon/site IDs and switches enter the build. Turnstile requires matching private configuration on the PHP host before deployment. No edge changes or uploads happen here.

Currently approved

Proposed release

Discard unsaved Cloudflare settings?

Saved settings and the approved website remain unchanged.