Skip to content
AgentZforiMIS®

Member portal and website recipes

Prompts for pages, portals, resources, navigation, publishing, design updates, and route audits. These recipes distinguish created content from published, verified member-facing pages.

Copy a request into your AI app and replace the words in square brackets with your own. See Using a recipe.

Create a new content page with a branded introduction

Section titled “Create a new content page with a branded introduction”

Recipe R-08-01 · Kind of request: Review then change · For: Digital team, Communications team

When to use it: Use this when staff need a new portal or website page and want it set up consistently. The digital team cares about location, naming, brand, and publish control.

What AgentZ does: AgentZ checks the site/folder context, drafts the content and page plan, and can create supported content records after approval. It should provide a publish and verification checklist instead of assuming the page is live.

Before you begin: Have the page purpose, audience, site/folder, desired URL, owner, and launch date ready.

Keep in mind: Creating content is not the same as publishing it. Verify permissions, navigation, and page rendering before launch.

Place a members-only resource list on a portal page

Section titled “Place a members-only resource list on a portal page”

Recipe R-08-02 · Kind of request: Guided handoff · For: Digital team, Membership team

When to use it: Use this when a team wants documents, downloads, or resources shown dynamically to members. Staff need the query, permissions, and page placement to agree.

What AgentZ does: AgentZ reviews the page and data source, proposes the query-backed display, and identifies what can be created or what needs native iPart placement. It should verify the member-facing page where possible.

Before you begin: Have the page, resource criteria, audience, columns, and access rule ready.

Keep in mind: A resource list is only member-only if page and content permissions are correct. Verify as a member where possible.

Build a member self-service dashboard page set

Section titled “Build a member self-service dashboard page set”

Recipe R-08-03 · Kind of request: Multi-step plan · For: Digital team, Membership team

When to use it: Use this when the portal should help members answer common questions themselves. The aim is fewer support tickets and a clearer member experience.

What AgentZ does: AgentZ identifies available member-specific data, designs the dashboard layout and required queries/content, and creates supported assets after approval. It should verify that the page respects member access and does not expose other members data.

Before you begin: Define the member audience, self-service goals, page location, KPIs, and launch owner.

Keep in mind: Member dashboards require careful permissions. Review logged-in and logged-out behaviour before launch.

Place a custom data-entry panel on a member profile page

Section titled “Place a custom data-entry panel on a member profile page”

Recipe R-08-04 · Kind of request: Guided handoff · For: Digital team, System administrator

When to use it: Use this when members or staff need to view or maintain custom profile information through the portal. The key risk is exposing the wrong fields or saving data in the wrong place.

What AgentZ does: AgentZ reviews the panel/source context and page structure, then prepares a placement plan and test cases. Where native iPart configuration is required, it gives a precise staff handoff.

Before you begin: Have the panel/source name, target page, fields, audience, and edit permissions ready.

Keep in mind: Custom data entry needs permission and writeback testing before launch.

Add a page to navigation and plan an old-URL redirect

Section titled “Add a page to navigation and plan an old-URL redirect”

Recipe R-08-05 · Kind of request: Review then change · For: Digital team, Communications team

When to use it: Use this when launching a new page, replacing an old page, or moving important member information. Digital staff need visitors to find the new content quickly, and they need old links from emails, search results, or bookmarks to keep working where possible.

What AgentZ does: AgentZ reviews the site navigation and route evidence, proposes label/order/redirect changes, and can help create supported updates after approval. It should verify routes in the browser where possible.

Before you begin: Have the page URL, navigation location, label, old URL, and launch date ready.

Keep in mind: Navigation changes affect public experience. Check mobile, logged-in, and logged-out behaviour if relevant.

Recipe R-08-06 · Kind of request: Multi-step plan · For: Digital team, Marketing team

When to use it: Use this for campaigns, services, events, or member journeys that deserve more than a basic content page. Staff want a page that is on-brand and built around the action visitors should take.

What AgentZ does: AgentZ uses the saved brand guidance, drafts the content structure, and maps the page to iMIS content/page assets. It should create or update supported assets only after approval and verify rendering.

Before you begin: Have the audience, offer, CTA, page location, brand constraints, and launch date ready.

Keep in mind: Good landing pages still need human review for copy, accessibility, and compliance.

Publish a page set and verify the routes are live

Section titled “Publish a page set and verify the routes are live”

Recipe R-08-07 · Kind of request: Guided handoff · For: Digital team

When to use it: Use this before announcing a new page set or portal area. Digital teams need a publish checklist that catches broken routes, missing permissions, and incomplete iParts.

What AgentZ does: AgentZ checks the page records and browser-visible routes it can reach, then separates live, draft, missing, and risky items. It should avoid claiming a route is live until browser verification supports it.

Before you begin: Have the page list, expected URLs, audience, and launch deadline ready.

Keep in mind: Page status, navigation, and browser rendering are separate checks. Confirm all three before launch.

Recipe R-08-08 · Kind of request: Guided handoff · For: Digital team, Brand owner

When to use it: Use this when a page looks off-brand or inconsistent with newer AgentZ-generated assets. Staff want design improvements without accidental layout damage.

What AgentZ does: AgentZ reads the design-system tokens and page context, produces a practical update plan, and can apply supported content/CSS changes after review. It should verify the page visually after changes.

Before you begin: Have the page URL, design concern, brand owner, and any protected content areas ready.

Keep in mind: Design changes should not hide content, break accessibility, or make member tasks harder.

Audit site routes before launch or cleanup

Section titled “Audit site routes before launch or cleanup”

Recipe R-08-09 · Kind of request: Look up · For: Digital team, Web owner

When to use it: Use this before website staff start a site launch, redesign, content cleanup, or migration. Web owners need to know what exists and what is risky before changing navigation or deleting pages.

What AgentZ does: AgentZ reads site and content evidence, checks reachable routes where possible, and turns findings into a cleanup/prioritisation report. It should keep the task read-only unless staff approve follow-up changes.

Before you begin: Have the site or section scope, launch date, and any protected pages ready.

Keep in mind: Route audits can find sensitive or old content. Review with the page owners before removing or redirecting anything.