A new teammate should only see the areas they need and should understand how drafts, approvals, customer records, and public publishing work in the workspace.

What this guide helps you do

• Choose the right access level before inviting someone.
• Prepare onboarding context for customers, website, posts, Money, plugins, and AI usage.
• Reduce accidental sends, publishes, or edits during the first week.

Before you start

• Know the teammate role and which business areas they should access.
• Review sensitive areas such as Money, customer inbox, integrations, and settings.
• Prepare a short list of first tasks and review rules.

Do it manually

1. Review current team members and roles.
2. Decide which modules the new teammate needs.
3. Clean up any confusing draft, test, or private items before onboarding.
4. Invite the teammate with the appropriate role.
5. Walk through Workspace, Customers, Website, Posts, and any plugins they will use.
6. Create first tasks or assign draft review work instead of giving open-ended access.

Ask Faster AI

• Create an onboarding checklist for a new marketing teammate. Include what they can review and what requires approval.
• Summarize the workspace areas a support teammate should learn first, based on customers, inbox, tasks, and forms.
• Prepare a first-week task list for a new admin user without changing permissions.

Review before saving or publishing

• Do not grant admin access just to unblock a single task.
• Confirm the teammate understands draft versus published states.
• Review AI usage expectations, especially around private customer data and public content.

Common issues and fixes

• If a teammate cannot open an area, review their role and workspace selection.
• If they can see too much, reduce access and audit recent activity.
• If they edit the wrong item, use review history or drafts to understand the change before publishing again.

Use it in daily operations

• Use a repeatable onboarding checklist for each role.
• Pair first-week tasks with a reviewer so new teammates learn approval patterns.
• Review access after the first project or after role changes.

Team handoff

• Write down what changed, who owns the next review, and which page, customer record, campaign, or plugin record should be checked next.
• If the work affects customers, include the public URL, test result, and any unresolved placeholder media in the handoff note.
• When Faster AI helped prepare the change, ask it to summarize the draft and review checklist so a teammate can approve the work without retracing every click.

Placeholder media

• Screenshot placeholder: add an annotated screenshot of prepare a workspace for a new team member with private customer, payment, and workspace details blurred.
• Video placeholder: add a short walkthrough that shows the manual path, the Faster AI prompt, and the review step before anything goes live.

Related help

• Set up your Faster workspace
• Manage integrations