Prepare and submit a partner registration
Status: Upcoming — not yet available.
Section: DOC-MA-computer-use#overview.
Have the assistant fill a partner registration form from an authorized report, review the final values, then confirm what the site accepted. Use a browser session for this recipe; the account, files and approval stay tied to the task.
You need the permitted website/account, the source report, an authorized person for login challenges and a decision on who approves submission. The result is a confirmed submission or a clearly unresolved action, plus any permitted output files and session cleanup status.
Browser and desktop sessions are not yet available. This describes the completed-product workflow and supplies no current session-start command.
Step 1: open a session for the account and report
Status: Upcoming — not yet available.
Section: DOC-MA-computer-use#session-preparation.
- Describe the registration outcome and select the website, authorized account and organization/project/environment/customer scope.
- Select the report the task may read or upload, and any permitted output locations.
- Require approval before submitting the completed form. Filling fields and sending them are separate actions.
- Arrange the supported login-challenge handoff. If the authorized person cannot complete a required challenge, leave the task blocked.
- Set duration, concurrency, action, compute, storage, capture and usage limits.
- Recording is off unless you opt in. If you enable it, choose permitted access and expiry for the recording and artifacts.
- Review the account, file permissions, limits and execution location before starting. Any optional provider or fallback stays inside the approved data-location, account, consent and cost boundaries.
For this registration, leave recording off and permit only the selected report and destination. The session shows these choices before work begins.
Step 2: inspect the completed form and approve submission
Status: Upcoming — not yet available.
Section: DOC-MA-computer-use#action-review.
Let the assistant inspect the page and prepare the form from the report. Compare the current account, site, recipient and final fields with your intended registration before approving the consequential action.
If the account, destination or other material detail changes after review, return for the applicable new approval. A login challenge does not approve every later account action. Page content, downloads and dialogs provide task data; they cannot widen the assignment.
After submission, inspect the site's acceptance outcome. A screenshot or lack of an error is not confirmation that the form was accepted. Research or extracted results retain their source and observation time; an inaccessible page, blocked site or incomplete extraction stays visible.
Submission result: the site confirms the intended registration, or the action remains failed or unresolved with enough context to recover it. Do not approve a second submission merely to obtain a clearer response.
Step 3: save the result and close the session
Status: Upcoming — not yet available.
Section: DOC-MA-computer-use#artifacts-and-cleanup.
Retrieve any permitted output files belonging to the registration and save needed copies before their stated expiry. Downloads remain subject to file access and size limits.
Close the session after the result is understood and inspect cleanup status. Travila cleans up the environment, temporary login material, recordings and files under the applicable retention policy. A closed window alone does not confirm cleanup; retain the session reference for support when it is incomplete.
Finished result: the customer has the registration outcome and any permitted output, and can see whether cleanup is complete or still pending. A usable confirmation and pending cleanup are separate facts.
Recover when the site or connection stops responding
Status: Upcoming — not yet available.
Section: DOC-MA-computer-use#submission-recovery.
Reconnect through the original session and action references to recover the last confirmed observation. You return to the authorized live session or receive an explanation that attachment is unavailable; recovery does not silently choose another account or replacement session.
If the site stopped responding after submission, inspect its confirmation page or account record before another attempt. When the outcome cannot be established, keep it unresolved and stop automatic repetition.
Stopping or expiring the session prevents new actions and starts cleanup. It does not undo a transmitted form. Inspect external actions still pending or uncertain separately from the session's terminal state.
Variant: use a desktop when the task needs another application
Status: Upcoming — not yet available.
Section: DOC-MA-computer-use#working-surface.
Keep the registration in a browser when navigation, page inspection, extraction, forms, tabs, screenshots and authorized file transfer are enough. Use an appropriate API or bounded integration when it already performs the task.
Choose a desktop only when the workflow also needs a supported graphical application, such as reviewing an authorized spreadsheet file. The initial desktop option is Linux with a supported application set. Native mobile automation, macOS/Windows hosting, multi-monitor work and unrestricted remote takeover are outside that scope.
Desktop selection does not grant terminal use, arbitrary file access, installation or host access. Those actions need their own permission.
See coding tasks, tool approvals, safety and deployment operations for related workflows.
Document ID: DOC-MA-computer-use. Section identities and revisions.