Setting Up Your Team

TeamBench is built for teams. Every account belongs to an organization, and all team members within that organization share reviewers, review history, knowledge bases, and chat conversations. Setting up your team correctly ensures everyone benefits from consistent quality standards.

To invite team members, go to Settings and navigate to the Team section. Enter the email addresses of the people you want to invite. They will receive an invitation email with a link to create their account and join your organization. If they already have a TeamBench account, they can be added directly.

TeamBench supports three roles: owner, admin, and member. The owner has full control over billing, team management, and all settings. Admins can manage team members and reviewers but cannot modify billing. Members can submit reviews, use chat, and access knowledge bases, but cannot change organizational settings. Assign roles based on each person's responsibilities.

Once your team members have joined, they automatically have access to all reviewers created within the organization. This is a key design decision -- reviewers are organizational resources, not personal ones. When someone creates a well-tuned blog post reviewer, every team member benefits from it immediately.

Before your team starts reviewing, take time to set up your core reviewers. Identify the content types your team produces most frequently -- blog posts, emails, social media posts, product descriptions -- and create a dedicated reviewer for each. Pre-loading these reviewers means team members can start getting scored feedback on day one.

Consider also setting up knowledge bases with your brand guidelines, style guide, and reference materials. When a knowledge base is attached to a reviewer, the AI has additional context about your brand's specific standards, terminology preferences, and quality expectations. This makes review feedback significantly more relevant and accurate.

Establish a clear workflow for your team: writers submit content for review, address the feedback, and re-submit until the score meets your threshold. This creates a measurable quality gate that replaces subjective "looks good to me" approvals with data-driven publishing decisions.

Finally, use the review history to track team performance over time. Identifying patterns -- which criteria consistently score low, which content types need the most revision cycles -- helps you focus training and improve your team's output systematically.