Demo multi-role tour

For a complete screenshot-based exercise, start with the LandWeave learner tutorial.

Demo only: one learner can view several roles

The multi-role launcher exists only to make a demonstration easier. It lets one learner see the Viewer, Editor, Reviewer, and Approver perspectives in separate Firefox tabs.

This is not how the real application is used. In a real installation, each person has one personal account and one assigned role. People do not share accounts, and one person does not perform all stages of the same workflow.

What you need

  • Mozilla Firefox for desktop. This browser requirement applies only to the tutorial/demo multi-role launcher. The normal application is not Firefox-only and can be used with other supported browsers.
  • The HTTPS address of the demo.
  • A current demo ticket from the trainer.

Use only synthetic training information. Do not enter real parcel, client, personal, or production data. The demo may be reset or deleted without notice.

Install the launcher

  1. Open the demo login page in desktop Firefox.
  2. Select Install Firefox demo launcher.
  3. Firefox shows an installation confirmation. Select Add.
  4. If the launcher icon is hidden, open Firefox's extensions menu and select LandWeave Demo Launcher. You may pin it to the toolbar for easier access.

The extension is signed by Mozilla. It is distributed by the demo because it is an unlisted teaching extension, not a public Firefox Add-ons listing.

Open the role tabs

  1. Select the LandWeave Demo Launcher icon in Firefox.
  2. Enter the exact HTTPS demo address supplied by the trainer. It may already be filled in after your first successful launch.
  3. Enter the ticket exactly as supplied, including the hyphen.
  4. Select Launch.
  5. Firefox asks whether the extension may access this demo. Approve only the named demo address.

The launcher opens separate tabs for the roles included in the ticket. Each tab uses its own Firefox container, so its login session remains separate from the others. The container label includes the demo host and role name.

Know which perspective you are using

Check the Firefox container label before acting. You can also point to the profile icon in the application toolbar to see the account and role.

Perspective What to observe in the demo
Viewer Inspect the parcel map, lists, attributes, history, and completed work. This perspective is read-only.
Editor Prepare or change a draft, save it, and submit it for review.
Reviewer Inspect submitted work and either accept it for approval or reject it with a reason.
Approver Inspect reviewed work and either give final approval or reject it with a reason.

The application deliberately separates workflow decisions. A higher role does not replace the exact role required for an action.

A simple learning sequence

  1. Start in the Viewer tab. Find the parcel or prepared example and note its current official state.
  2. Move to the Editor tab. Create or open the assigned draft, make the exercise change, save it, and submit it.
  3. Move to the Reviewer tab. Find the submitted item, inspect it, and follow the exercise instruction to accept or reject it.
  4. Move to the Approver tab. If the item was accepted for approval, inspect it and follow the exercise instruction to approve or reject it.
  5. Return to the Viewer tab and refresh the relevant page to observe the result from the read-only perspective.

Always follow the trainer's exercise instructions. Shared tutorial accounts may contain work from other learners, so use only the parcel or example assigned to you.

Keep the sessions separate

  • Do not copy cookies or one-time login addresses between tabs.
  • Do not use a role tab for an action assigned to another role.
  • Signing out in one container should not sign out the other role tabs.
  • Closing a tab does not create another ticket launch. Using Launch again does, and tickets have an expiry time and a maximum number of launches.
  • Treat the ticket as temporary access information. Do not post it publicly.

If something does not work

  • The install link is missing: reopen the demo login page in desktop Firefox. Other browsers show a Firefox installation link instead.
  • Firefox downloads the file instead of asking to install: confirm that you used the install link on the demo login page. You can also open the downloaded signed .xpi file from Firefox.
  • The launcher rejects the demo address: use the exact HTTPS origin, without an extra path.
  • The launcher rejects the ticket: check the characters and hyphen. The ticket may have expired or reached its launch limit; ask the trainer for a new one.
  • A role tab is signed out: do not enter another role's credentials. Ask the trainer whether to relaunch with a valid ticket.

For ordinary application navigation, see Navigation and Toolbar. For the workflow itself, see ParcelDraft Workflow.