Moxby / Setup option sheet

Build your team workspace setup request.

Build a team workspace setup inquiry around the work you want to discuss. Select shared context, browser-side work or both. The option sheet makes dependencies visible before you send anything to Moxby.

Scope, not a subscription tierCommercial scope is individual to the requested workspace or workflow and its environment. There is no published rate, automatic quote or payment here. Any later proposal uses USD, after the relevant availability and permissions are reviewed.

A user reviews an illustrative software setup option sheet and selection summary. — Illustrative workflow / Selection and reviewThe working option sheet below describes a request. It does not reserve product access.

Start smallTeam workspace is selected to begin. Change that choice if the browser assistant is the part you need. A count of selected areas is not a recommendation to select more.

Moxby / Austin, Texas, United States

Describe the work. Leave passwords out. Your notes belong to this inquiry, not a public share link.

The option sheet still works as a form without JavaScript. Choose at least one area and select Browser assistant yourself if you choose Local workflows or Website actions. Both optional scope-note fields remain visible. Repeat your selected areas and starting context in Inquiry notes so the request is clear without the generated summary. The server checks your submission.

The summary shown below is the starting example, not a live reading of your choices. Nothing is sent until you submit the inquiry.

Choose the work to discuss.

Use the square checkboxes to select product areas. You can change them in any order; this is not a step-by-step quiz. Keep at least one selected. The summary alongside the sheet follows the source controls.

01 / Product areas

These are requested areas of work, not confirmed licence bundles. Team workspace can stand alone. Local workflows and Website actions each bring Browser assistant into the request.

Team workspaceConnect a conversation with its task and working document. Select this for shared context, whether or not the request includes browser-side work. Browser assistantDiscuss assistance beside an active browser page. Define what should remain a user decision and which permissions need checking. Local workflowsDescribe a chosen input and the output a person reviews. Requires Browser assistant in this request. Local does not mean offline or free of external processing. Website actionsDescribe a bounded action on a named website, with a review point and a stopping condition. Requires Browser assistant; site permission and feasibility need review.

Team workspace can stand alone or accompany Browser assistant. Selecting Local workflows or Website actions also selects Browser assistant.

Starting selection: Team workspace. With live updates enabled, changes and required dependencies are announced here.

02 / Starting context

Choose the closer description. This changes the preparation guidance, not product availability or commercial terms.

Existing team routine New workspace routine

Start with one routine the team already uses. Describe where the conversation lives and where the handoff loses context. A redacted example is enough; do not send an account export.

Website name or public URL (optional; for Website actions)

Visitor note. Enter only a website name or public URL. This field is not opened or fetched. Leave private links, session identifiers and credentials out. Without live updates, fill this only if you selected Website actions.

Local environment note (optional; for Local workflows)

Visitor note. Describe the browser and operating environment to review, plus any known external connection. Do not include private file paths or account details. This is not a compatibility confirmation. Without live updates, fill this only if you selected Local workflows.

Your requested setup

1 product area selected

Team workspace

Questions to resolve

Which conversation should stay with the task, and which working document does it refer to?
Who reviews the work before it passes to someone else?

Setup summary

Requested areas: Team workspace. Starting context: existing team routine. Keep a shared conversation with its related task and working document.

This is a setup request, not a quote or an order. Selected areas are not confirmed licence bundles. Availability and permissions need review; any later commercial proposal uses USD. Edit the choices or visitor notes above to change this summary.

Send setup inquiry

The selected areas and starting context accompany this inquiry. Active website and environment notes are marked as visitor notes, not confirmed product facts.

Add your name and a way to reply. Phone and email are each optional, but at least one is needed. The address field is optional and does not determine whether the requested setup is available.

Name

Address (optional)

Phone (optional)

Email (optional)

Enter a phone number or an email address so Moxby can reply. You may provide both, but neither is required on its own.

Inquiry notes (optional)

Describe one piece of work and the result someone would review. For a website action, include its review point and stopping condition. Without JavaScript, repeat your selected product areas and starting context here. Do not include passwords, private links or other people's personal records.

Inquiry processingI agree to the processing of my details and request so Moxby can handle this inquiry.

Submitting asks for a discussion. It does not place an order, reserve access or accept a commercial proposal.

Read the dependencies

The assistant boundary travels with browser work.

A workspace with a browser assistant is a combined request, not a reason to blur their jobs.

Team workspace concerns shared context. Browser assistant concerns work beside the active page. You can select either alone, or ask about both when the conversation needs to connect with work a person carries out in the browser.

Local workflows and Website actions depend on Browser assistant in this option sheet. Their requests would be incomplete without the browser environment and permission discussion. Selecting either adds the assistant visibly; it does not silently add a charge.

If you try to remove Browser assistant while either dependent area remains selected, the assistant stays selected and the sheet tells you why. Remove the dependent area first. Your other choices are not discarded to make the selection fit.

The same rule prevents an empty request. Select a replacement area before removing the last one. You are not locked into Team workspace, and there is no scoring system behind the initial choice.

The source controls remain the way to edit the generated summary. Website and environment notes are included only when their relevant area is selected. The sheet does not save those notes in local storage or put them into a shareable URL.

Workspace only: A request about the conversation and document connected to a task. There is no browser-action request implied by this selection.
Assistant only: A request about assistance beside an active page, with the environment and user-decision boundary to confirm. It does not require replacing an existing team workspace.
Local workflows selected: Browser assistant is included. Preparation questions expand to cover the local input and output, plus any external processing or destination.
Website actions selected: Browser assistant is included. Questions expand to cover the target website, permitted action and conditions for stopping. Naming a website does not establish support.

Prepare the useful detail

One example can carry the whole request.

Existing team routine

Describe where context gets lost.

A task may point at a document while the decision behind it remains in a separate conversation. Explain the missing connection, not the entire history of your tools. A short non-sensitive example gives the scope discussion a concrete starting point.

For browser work, say where the person leaves the shared task and what they need to do on the website. The starting-context preference changes this preparation guidance; it does not confirm an integration with the tools you already use.

New workspace routine

Describe who starts and who reviews.

You do not need an existing workspace to explain the routine you want. Choose a piece of work that another person would recognise, then describe the handoff. Keep requested behaviour distinct from features you assume are available.

If the request also includes a local workflow, explain its input without sharing the source file. If it includes a website action, identify the intended review state before discussing any final commitment.

After the option sheet

A submitted request still needs review.

The option sheet organises the inquiry. It cannot decide website permission or product availability.

What does the summary establish?

It records the areas you selected and the starting context, with the active optional notes you supplied. It does not assert that a website is compatible, a browser is supported or an action has been authorised. Those are questions for the scope discussion.

What happens after sending?

An accepted submission records the inquiry. Keep any reference returned by the site for later correspondence. Acceptance of the message is not acceptance of the proposed work, and this page promises no reply deadline. The setup request process explains the distinction between inquiry and agreement.

What if sending fails?

Correct any identified field and keep your request text until receipt is confirmed. If a connection fails after you submit, do not assume the message was accepted or automatically send repeated copies. You can ask through Contact Moxby and explain the uncertainty without sending private account information.

Can you discuss a question instead of a full setup?

Yes. The contact page accepts a general inquiry, and Support chat is available for a question about the product. This sheet is useful when you already know which parts of the work need to be considered together.