Skip to main content

Onboarding to TestChimp

When you first start using TestChimp, you'll set up your team and projects. Here's how TestChimp's organizational structure works:

Step 1: Create a Team

The first step in onboarding to TestChimp is to create a team. A Team is a set of users who work together on multiple projects. The team represents your organization or company.

Team Characteristics

  • Multiple users: A team consists of multiple users who collaborate together
  • Multiple projects: Teams can have multiple projects under them
  • Unified access: All users in a team have access to all projects within that team
  • Team-level management: Users are added at the team level, not to individual projects

Step 2: Create Projects

After creating your team, you can create projects. A Project is typically for a single product or application your team is working on. Projects are organized under a Team.

Project Characteristics

  • Product-focused: Each project typically represents one product or application
  • Team-wide access: All team members automatically have access to all projects
  • Independent testing: Each project has its own tests, bugs, and Atlas SiteMap
  • Multiple projects: A team can have multiple projects for different products

Team and Project Workflow

The typical workflow is:

  1. Create a team: Set up your team with your organization's users
  2. Add team members: Invite users to join your team (see below)
  3. Create projects: Create projects for each product or application you want to test
  4. Start testing: Begin creating SmartTests and running explorations within your projects

Adding Users to Your Team

To add users to your team (team administrators only):

  1. Go to Settings → Team Settings
  2. Click on the Team Members tab
  3. Scroll to the "Invitations" section
  4. Enter email addresses in the text area, separated by commas (e.g., user1@example.com, user2@example.com)
  5. Click "Invite Members"
  6. If the user is not part of the organization yet, an invitation email will be sent

Note: All team members will have access to all projects within the team. There are no project-level permissions - users are managed at the team level.