Prepare a personalized client onboarding workspace

Implementation guide · untested

Source-supported actions are attributed evidence. Proposed steps, prompts, synthetic examples and checks are original editorial guidance; the workflow has not been run.

Why this agent / simpler alternative

Agent contribution

A service business can use an agent to track the same approved client attributes across a welcome document, project tracker and kickoff slides, then explain unfinished substitutions. The value is cross-file consistency and exception handling.

Simpler alternative

A manually copied template folder or a deterministic replacement script is sufficient when there are few files and every placeholder is uniform.

Unsuitable when

The template folder contains another client’s information, access inheritance is unclear, shared-drive restrictions are unknown, or the work needs confidential material not approved for Manus.

Source-supported scope

See the existing source-backed action summary on this page.

Setup — required, optional and unknown

Required

1. Editorial pilot: verify that the actual Manus account exposes the required copy, content-edit and inspection operations before using real templates.

2. A dedicated private test destination and synthetic client profile; a template owner who can identify the correct current kit.

3. A manifest naming every included file and a replacement dictionary; no broad search of the client drive.

Optional

1. Native Docs, Sheets and Slides copies for a later approved service-specific test.

2. A reviewer-approved sharing matrix kept as a proposal; no live recipients are needed for the dry run.

Unknown

1. Manus’s current connector documentation makes available services account-dependent; the earlier recipe alone does not establish current copy/edit/share tools in a particular account.

2. Shared-drive inheritance, linked assets, chart references and service costs were not verified.

Inputs and access

1. Name

   template_manifest

   Format

   CSV: template_id, file_type, version, expected_title, placeholders, protected_sections and linked_resource_ids

   Source or owner

   Onboarding operations owner

   Access scope

   Only the designated template kit

   Permission needed

   Permission to read and copy these files into the named private destination

2. Name

   client_profile

   Format

   JSON/text: fictional client_code, display_name, project_name, kickoff_date, owner_name and approved scope_summary

   Source or owner

   Account manager

   Access scope

   One synthetic client in the pilot

   Permission needed

   Real client data later requires approval for the named destination service

3. Name

   replacement_dictionary

   Format

   CSV with token, replacement, applicable_files and omit_if_missing

   Source or owner

   Template owner

   Access scope

   Named tokens only

   Permission needed

   Approval of the replacement values; no inferred commitments

4. Name

   destination_and_permissions_plan

   Format

   Text: exact parent folder ID, proposed new folder title, internal owner and intended recipient addresses/roles

   Source or owner

   Workspace administrator

   Access scope

   Private destination; preview permissions only

   Permission needed

   Creation/copy authority must be specific; actual sharing needs separate file, person and role approval

Documented source actions

1. 1

   Copy, personalize, share.

   Input: Templates

   Output: Workspace.

   Checkpoint: Review described.

   Source: third workflow example ↗

Proposed implementation steps — unexecuted

1. 1

   Confirm source IDs, file types, destination and intended operations. Compare the required operations with the actual account’s available connector tools; produce a plan without writing.

   Input: Template manifest and synthetic client profile

   Output: capability-checklist and destination manifest

   Checkpoint: If native copy or editing is unavailable, stop that action. A generic Drive connection does not prove these operations work.

2. 2

   For a separately authorized pilot, create one uniquely named test workspace and copies of only listed templates. Record source-to-copy IDs immediately; retain originals unchanged.

   Input: Approved manifest and private destination

   Output: copy_manifest with source_id, copy_id, file_type and parent_id

   Checkpoint: No extra files, external links or inherited access may be assumed safe; inspect the destination’s access before placing client material there.

3. 3

   Replace only approved tokens in each permitted location. Record each replacement and any token not found; preserve formulas, data validation, chart data sources and protected text.

   Input: Copies and replacement dictionary

   Output: replacement_log by file and location

   Checkpoint: Do not replace substrings inside formulas, URLs or embedded references blindly. Missing values remain marked for review.

4. 4

   Inspect each native format: read document headings, verify tracker formulas and validation, inspect slide text and layout. Search for leftover tokens and previous-client names; check links against the permitted-resource list.

   Input: Personalized copies and manifests

   Output: content_qa with one status per file and an exceptions list

   Checkpoint: A complete folder count is insufficient: each file must open, retain its intended structure and contain no cross-client material.

5. 5

   Prepare an access preview naming verified people, exact files/folder, requested roles and inherited permissions. Highlight public-link, domain-wide and edit-access expansion.

   Input: Reviewed workspace and intended recipient/role matrix

   Output: sharing_preview only; no permission changes

   Checkpoint: Require explicit approval of the audience and minimum role before a separate sharing action. Ambiguous recipients block sharing.

6. 6

   Create a completion packet showing ready, blocked and omitted items and exact workspace location. Keep all files private; record which source versions were used for a later retry.

   Input: Copy manifest, replacement log, content QA and sharing preview

   Output: review_packet with file links for authorized internal reviewers and release blockers

   Checkpoint: Stop at private review. Never describe onboarding as delivered until authorized sharing is completed and recipient access is verified in a later task.

Original starter prompt — proposed

Origin

editorial_proposal

Text

Plan a private onboarding workspace for fictional client {client_code} from {template_manifest}. Confirm the available native copy and editing tools before proceeding. Use only {replacement_dictionary}, preserve protected sections, formulas and linked-resource restrictions, and list every proposed write to {test_destination}. Do not write until that plan is explicitly approved. After approval limited to private copies, produce a source-to-copy manifest, replacement log and per-file QA. Treat missing values and cross-client references as blockers. Show {recipient_matrix} as a permission proposal only; do not share, send invitations, publish links, enable connectors or schedule anything.

Placeholders

1. client_code

2. template_manifest

3. replacement_dictionary

4. test_destination

5. recipient_matrix

Limitations

Original proposed two-stage prompt. It does not claim all Manus accounts support native edits or that a private copy preserves access safely. A write approval does not grant sharing permission.

Synthetic worked example — not an agent run

Status

synthetic

Label

Invented onboarding QA packet; no workspace was created

Artifact url

Not specified.

Content

Client code

DEMO-NORTH-01

Workspace title

Northstar Demo - Onboarding - TEST

File checks

1. File

   Welcome document

   Copy id

   synthetic-doc-01

   Replacement count

   3

   Leftover tokens

   0

   Status

   ready_for_internal_review

2. File

   Project tracker

   Copy id

   synthetic-sheet-01

   Replacement count

   2

   Formula check

   B7 retains SUM(B2:B6)

   Status

   ready_for_internal_review

3. File

   Kickoff deck

   Copy id

   synthetic-slides-01

   Replacement count

   4

   Leftover tokens

   1

   Status

   blocked

   Issue

   Slide 4 still contains {kickoff_date}; approved value absent

Sharing preview

1. Recipient

   client-reviewer@example.invalid

   Role

   viewer

   Verified

   No

   Applied

   No

Release status

BLOCKED: kickoff date and recipient identity unresolved; no links published.

Costs and effort — unmeasured

Verified prices

Setup work

1. Clean and version the reusable template kit; enumerate tokens and protected formula/linked-resource locations.

2. Verify actual account capabilities and arrange a private destination before a pilot.

Recurring work

1. Check source versions and exact recipients for each client.

2. Review layout, leftover placeholders, formulas and access inheritance before release.

Unknowns

1. Manus usage credits, Workspace charges, native-edit fidelity and reviewer time were not measured.

2. No measured reduction in onboarding duration, client outcomes or willingness to pay is established.

Failure modes

1. Signal

   A template contains a previous client’s logo, notes or hidden sheet.

   Consequence

   Copying spreads cross-client material into the new workspace.

2. Signal

   A replacement modifies a formula or linked-resource URL.

   Consequence

   The tracker or slides silently refer to the wrong data.

3. Signal

   The destination inherits broad access.

   Consequence

   A private-looking folder may expose client material.

4. Signal

   Only some files were copied before a tool error.

   Consequence

   A blind retry can create duplicate workspaces or mixed versions.

Recovery steps

1. Trigger

   Missing capability or denied file access

   Action

   Return the exact missing operation and file ID for the workspace owner; keep the remaining plan read-only.

   Stop condition

   Do not bypass the restriction with another account, export or custom connector.

2. Trigger

   Partial copy

   Action

   Compare existing copy IDs to the manifest before retrying only the missing authorized item; obtain approval before deleting any extra copy.

   Stop condition

   Stop if the original-to-copy mapping is uncertain.

3. Trigger

   Corrupted formula or cross-client content

   Action

   Quarantine the affected draft from release and compare it with the untouched source; have the template owner correct the kit, then recopy that file if authorized.

   Stop condition

   No sharing while any contamination or formula error remains.

4. Trigger

   Unexpected inherited access

   Action

   Pause before placing real client information in the folder and ask the administrator for an approved private destination.

   Stop condition

   Do not silently change production permissions.

Source-observed and proposed approval boundaries

Source observed

Source describes user-specified permissions and review/approval.

Editorial recommendations

1. Approve exact template IDs and private copy destination before writes.

2. Treat any new connector authorization separately; the guide is not consent to persistent access.

3. Sharing requires verified people, named folder/files and minimum roles; no public links or invitations during the pilot.

Unexecuted validation plan

Fixture

Proposed fixture: three synthetic native templates, one cross-client-name trap, a tracker formula and validation list, a slide with a missing kickoff-date token, and an unverified recipient at example.invalid. No fixture created or run.

Acceptance checks

1. Every authorized source maps to exactly one private copy; originals remain unchanged.

2. The cross-client trap and missing token are reported, not silently removed or invented.

3. Tracker formulas, validation and intended links survive; native files open with readable layout.

4. Permissions remain unchanged, no invitations are sent, and the report identifies inherited access explicitly.

Stop conditions

1. A required native operation is unavailable.

2. Cross-client content survives unflagged or protected formulas change.

3. The agent attempts sharing, public publishing or a broader data search.

Executed

No

Limits

1. Official recipe evidence supports the use-case concept, not a measured or reproduced run.

2. Do not rely on an undo promise as a recovery plan; copying, editing and disclosure require different controls.

3. Canadian suitability, bilingual fidelity and data residency were not established.

Guide source links

https://www.manus.im/blog/deep-dive-google-drive-connector ↗
Original recipe or report; see documented_steps locators.

https://www.manus.im/features/connectors ↗
Current connector services and actions depend on the account; Sheets availability is conditional.