Visionir is a workspace for creating and managing website content within your organisation’s brand, content and approval rules. You can create an individual section for an existing website page, or build a page draft from a reusable template.

Your everyday workflow

1. Choose a page. Find the existing website page you want to improve, or start a page draft.
2. Create the content. Choose a block type and layout, then describe what you need.
3. Review the result. Check the wording, references, links, images and responsive preview.
4. Complete approval. Resolve any failed checks and follow your organisation’s review policy.
5. Publish in your CMS. Copy the approved code into the correct page, preview it and publish.
6. Record and check. Record the deployment in Visionir and refresh the website page to check it.

1. Open your Visionir sign-in link. Enter your work email and password, then select Sign in.
2. Joining for the first time? Open your private invitation. New users create their own account; existing users sign in with their existing account. Keep invitation links private.
3. Check the organisation name. The header and dashboard identify your active workspace. If your account belongs to more than one organisation, use the organisation selector in the header.
4. Check your role. Your account menu and welcome card show whether you are a Creator, Approver or Administrator. The available actions reflect that role.

The top search helps you find pages, URLs, blocks, templates and workspace areas. Select a result to open it. On desktop, you can also use ⌘ / Ctrl + K.

Some workspaces offer a Product tour in the sidebar. You can skip the tour and return to it when available. Use Sign out when you finish on a shared computer.

Your workspace may arrive with prepared settings, website references and example blocks. Review those settings for your own organisation before activating the workspace.

1. Organisation. Confirm the organisation name, website, location and relevant profile details. Use the correct public website address.
2. Website & sources. Your saved website starts importing in the background. Review the page directory and reference material. To refresh or retry, select Import website. Add approved reference text where needed.
3. Approve the references. Read the material, select the single authorisation checkbox beneath the references and select Approve references. Importing a website alone does not approve its content for use.
4. Brand identity. Upload your logo file and review the suggested colours, fonts and visual style. Check Writing guidelines for tone, terminology and claims. Inspect the live preview before confirming.
5. Team & approvals. Where this step is shown, choose your approval policy and invite the people who need access. If independent review is required, make sure the necessary reviewers have accepted their invitations.
6. Review examples. Inspect the prepared examples or sample layouts on desktop, tablet and mobile. Check copy, links, branding and readability before confirming.
7. Activate workspace. Review the readiness list, complete any outstanding confirmations and activate the workspace.

Use Previous step and Next step to move through setup. Moving to the next step saves your entries; approval buttons provide the separate confirmations for each foundation.

The dashboard brings together recent page activity, recent block activity, the approval queue and a template snapshot. Select an activity item to open the relevant work.

Available counts and actions reflect your access. The governance score summarises checks in Visionir; it is not a certificate for your whole website.

Find it: Website in the sidebar

Pages

1. Find the page. Use Find a page to search page names, then select a result.
2. Check the destination. Use View live page to open the website. The CMS content shown in Visionir is read-only.
3. See its Visionir blocks. Review the linked blocks and their publication status. Choose Create block to start a new section for that page, or Add existing block to link a library item.
4. Refresh after publishing. Select Refresh page to read the public page again and check for recognised Visionir blocks.

Use Pages using Visionir to narrow the directory to pages with recorded or detected published blocks. Linking a block to a page is planning; it does not publish the block.

All blocks

Browse the blocks available to your account. Use Published blocks, or filter for blocks used on multiple pages, not linked to a page, or needing review. Open Details, Edit block or the published page from a block card.

Expand a block’s page-usage panel to see its destinations and recorded versions. A block can appear on more than one page, so check each location before updating or removing it.

Page drafts & website details

Page drafts shows pages being assembled inside Visionir. Use Website details → Update page list to refresh the imported directory when new pages have been added to your public website.

Find it: New Block on the dashboard, or Generate Block in the sidebar

1. Block Context

Enter a useful Block Name, such as “Business support overview”. Under What page will this block be used on?, select the intended website page. You can search by a page name, URL or a description such as “homepage”. Check the selected address, then choose Continue.

2. Block Type & Layout

Choose a suitable structure, such as linked cards, an FAQ or a hero. Review the suggested type and the layout previews, then choose the approved layout that best fits your brief. Select Continue.

3. AI Instructions

In AI Prompt, explain the purpose, audience, content to include and action you want the visitor to take. If the chosen layout supports images, choose the available image source, upload an appropriate image where offered and provide useful alternative text.

Select Generate Block. Once generation finishes, review the content and preview before submitting it for approval.

Find it: after generation, or Website → All blocks → Edit block

1. Read the content. Edit the headings, body copy, card text, button labels and other fields available for the selected block type.
2. Check the references. Review the content references against the wording. Confirm factual claims rather than assuming a source label proves every sentence.
3. Open every link. Make sure each button or card leads to the right approved page. Use a descriptive label that explains the destination.
4. Check images. Confirm that the image is relevant, you have permission to use it and any required alternative text describes it properly.
5. Review each screen size. Switch between Desktop, Tablet and Mobile. Check wrapping, spacing, image cropping and readable button text.
6. Refine if needed. Use Refine with AI for a specific change, then review the result again. Manual editing remains useful for exact wording and destinations.
7. Save and submit. Use the save control where shown to retain your draft. When ready, select Submit for approval. Check for confirmation before leaving the screen.

Use Undo and Redo while editing where available. Expand the linked-page container with View to see where the block is intended to appear.

Find it: Block Types in the sidebar

Browse the available types and layouts before creating content. Select Create Block from a suitable type to use its approved structure.

Request a new reusable structure

1. Select Create Block Type if your role permits it.
2. Describe the type’s name, purpose and the content it needs to hold.
3. Define the fields, such as headings, text, images, links or repeated cards, using the available controls.
4. Configure the offered layout variants and governance rules. Check the preview.
5. Select Submit for approval. An authorised reviewer approves the type or requests changes before it becomes available for general use.

A new type defines an approved structure. You create individual blocks from it afterwards. For a routine text change, edit the block rather than changing the reusable type.

Find it: Templates in the sidebar

Open a template to review its Overview, Structure, Rules and Preview. A template describes the order of sections and which block types each section allows.

Create a template — Administrators

1. Select New template or the create action in Templates.
2. Add a clear name, page purpose, audience and any default AI guidance.
3. Start from an available preset or arrange your own sections.
4. Set the required sections, allowed block types, permitted counts and order or skipping rules.
5. Review the structure and preview, save it as a draft and publish the template when it is ready for the team to use.

Publishing a template makes it available for page creation inside Visionir. To put content on a live website, create a page from the template and follow its separate content, approval and CMS publishing steps.

Find it: New Page on the dashboard, or Website → Page drafts

1. Choose a template. Pick a published template that fits the page’s purpose.
2. Add page details. Enter the page name and slug, then create the draft.
3. Build the sections. Open Sections. Generate a compatible block for each required section, or attach an existing compatible approved block where offered.
4. Review each block. Check and approve the attached content through its normal workflow. Follow the template’s required-section, order and allowed-type rules.
5. Preview the page. Use Overview, Sections and Preview to check the details, completion and combined result.
6. Submit the page. Complete the page’s separate approval workflow. Approved blocks alone do not approve the whole page.
7. Publish through the page screen. Once ready, copy the page’s CMS code into the authorised CMS embed area, preview the full page and publish it. Use the page screen’s completion control after that publication.

Find it: after Submit for approval, or Approvals in the sidebar

The approval screen progresses through the configured checks. Read any issue and make the required fix before trying again. The checks cover:

When a separate reviewer is required

A Creator’s submission waits for an authorised Approver or Administrator. The reviewer opens the item, inspects the content and checks, then chooses Approve or Request changes. If changes are needed, give clear feedback; the author edits and submits again.

When your own submission approves automatically

An Administrator or Approver can have their own valid block submission approved automatically when the organisation allows self-approval. The checks still run. An independent-review policy continues to require a different authorised reviewer. This rule does not automatically approve every page or template.

What the main statuses mean

Find it: the approved block’s publishing screen, or Website → Publish block

You need access to the destination CMS and publishing permission in Visionir. Ask your website administrator which approved HTML or embed area to use if your CMS uses a different label.

1. Confirm the destination page. Check the website page shown on the deployment screen.
2. Copy the approved code. Select Copy HTML Code.
3. Open the page in your CMS. Edit the page where the block belongs.
4. Select a Custom HTML block. Add a new Custom HTML block, or your CMS’s approved equivalent, in the page content area.
5. Paste the code. Paste all of the approved output into the new block. Keep its Visionir identifiers so website checks can recognise it.
6. Position, preview and publish. Move the block between the sections where you want it. Check the full page on different screen sizes, test links and interactions, then publish when you are happy.
7. Record the deployment. Return to Visionir and select Record deployment after the CMS page is published.
8. Check the live page. Open Website, select the destination and choose Refresh page. Review the page-usage details and open the public page yourself.

Publish an update

1. Open the block, make your changes and submit the updated content for approval.
2. After approval, choose Publish update where offered and copy the new approved code.
3. Replace the existing Visionir code in the CMS, rather than adding a duplicate section.
4. Preview and publish the CMS page, record the deployment and refresh the page in Visionir.

If the block is used on several pages, review and update each intended location. Editing it in Visionir does not replace code on those pages automatically.

Mark one page as unpublished

1. Remove the Custom HTML block from the CMS page and publish that change.
2. In Website or Organisation → Deployments, open Manage block → Mark unpublished.
3. Review the selected page, confirm the CMS removal and select Mark unpublished.

The block stays in the library for later use. Other pages using it keep their own publication records.

Delete the block from Visionir

Remove it from every CMS location listed, then choose Manage block → Delete block. Review the confirmation carefully. If a Visionir page draft still uses the block, remove that page reference first.

Administrators can delete any block. Creators and Approvers can delete their own eligible drafts or blocks needing changes. Publication and audit history are retained, and there is no user-facing undelete control.

Find it: Organisation at the bottom of the sidebar

Use Organisation for the profile, website, approved destinations, reference material and setup status. Users with the required permissions can update the settings and refresh website references.

Use Governance for the detailed rules. The current settings are organised into:

Confirm the real brand colours, fonts, visual treatment, approved wording and permitted link destinations. Review website-derived suggestions rather than assuming every extracted value is correct.

Save changes using the controls shown. If the workspace asks for renewed source, brand or example confirmation, complete it before continuing. Changed governance can require an existing block to be reviewed again before publication.

Find it: Organisation → Access & security — Administrators

1. Enter the person’s name and work email.
2. Choose Creator, Approver or Administrator.
3. Select Create invitation. If email delivery is configured, the invitation can be emailed. Otherwise share the private invitation link with the intended person.
4. Ask them to accept the invitation. A pending invitation does not yet provide an active reviewer.

Review pending invitations and revoke any that are no longer needed. Invitations expire after 72 hours. Administrators can change member roles and disable or restore access using the controls beside a member.

Use individual accounts for your team so actions can be attributed to the right person. Use an approved demonstration account only for its intended demo workspace.

Find it: Organisation → Deployments or Organisation → Audit trail

Deployments

The Published view shows current publication records. Use All history to see previous releases, unpublished entries and records for deleted blocks. Open the destination link to inspect the real website.

Expand Release details for the method, version and recorded checks. Record manual check records your own verification; it is separate from the public-page reading performed by Website → Refresh page.

Restore version, where available, brings a recorded version back as a new draft for review. Review and approve it, then replace the CMS code and publish if you want it live. Restoring a draft does not roll back your website automatically.

Audit trail — Administrators

Use the audit trail to review recorded activity such as content changes, approvals, invitations and deployments. Check the actor, time and item details when investigating a change.

Choose Help beside your account icon. In the right-hand panel, select Speak to technical support → Start a conversation, add a subject and explain the issue. Return to that conversation to read replies or add more detail. Select Mark resolved when it is sorted.

Include the page or block name, what you were trying to do and any error message. Keep passwords, API keys and confidential material out of support messages. Replies appear in the conversation; do not assume an immediate live-chat response.

Use an approved demo workspace and a separate CMS demonstration page you are authorised to edit. Use example content and review it before the session.

1. Introduce the workspace. Show the organisation branding, dashboard and governance overview.
2. Start from a real task. Open Website and choose a relevant page, such as a Business or Services page.
3. Generate one useful section. Choose a block type and layout, then use a clear brief. The example prompt in Create your first block is a useful starting point.
4. Show the review. Edit a sentence, inspect a relevant link and switch between desktop and mobile previews.
5. Show the checks. Submit the block and explain the results. Describe the actual approval policy, including automatic author approval when enabled.
6. Demonstrate publication. Copy the approved code into the authorised CMS demonstration page, position it, preview and publish. Return to Visionir to record and check that deployment.
7. Show ongoing control. Open the published block’s page usage and deployment history. Briefly show Templates, team roles and Help if relevant to the audience.