Articles in this section

Projects Overview

In Iterable, an organization can have many projects. Each project is a separate entity, with separate data.

Create multiple projects if:

  • You would like a live, production project and a sandbox project (for testing purposes).
  • Your organization contains multiple brands or products with different user databases.
  • You're an agency that uses Iterable for multiple clients.

# In this article

# About projects

Iterable projects are separate entities that contain their own data and settings. Each project has its own set of users, lists, campaigns, and other data. This means that if you create a new project, it won't have any of the data or settings from your other projects. For example, if you create a new project, it won't have any of the users, lists, or campaigns from your other projects. This allows you to create separate environments for different purposes, such as testing, development, or production.

You can view and manage all of the projects you have access to by clicking on the top right corner of the screen, where you can see the name of the current project. You can also switch between projects from this menu.

When you create a new project, two main settings are configured that cannot be changed: data center and project type.

Other ways to customize a project include:

Additional configurations vary depending on your Iterable plan and the features you have access to. Talk to your implementation manager or Iterable customer success manager for more information about your Iterable plan and features.

# Data centers

All of an organization's projects must be hosted on the same data center — all in the US, or all in the EU. For more information, read Iterable's European Data Center (EDC).

# Project types

A project's type is determined by the unique identifier used in the project to identify the users that you send messages to. There are three types of projects in Iterable:

  • Hybrid projects: Use both email and userId as unique identifiers.

  • UserID-based projects: Use userId as a unique identifier.

  • Email-based projects: Use email as a unique identifier. (Limited availability: Only certain accounts have the option to create email-based projects - learn more.)

A project's type is a set property. Once you create a project, you can't change the project type.

For more information about project types and unique identifiers, see Project Types and Unique Identifiers.

# Project settings

Each project has its own settings, which determine how the project behaves. For example, each project has its own time zone, which determines when campaigns are sent.

For more information about project settings, see Project Settings.

# Project senders

Each project also has its own set of senders and channel configurations, which determine how messages are sent from the project.

To learn more about setting up each channel, see the following articles:

# Project data

Each project has its own data, which is separate from the data in other projects. This means that if you create a new project, it won't have any of the data from your other projects. For example, if you create a new project, it won't have any of the users, lists, or catalogs from your other projects.

To learn more about how to manage your project's user data, see Data Schema Management Overview.

To learn more about catalog data, see Catalog Overview.

# Project members and permissions

Project members are Iterable users who have access to view, edit, and/or manage a project. You can add project members to a project and assign them different roles. Each role has different permissions, which determine what the user can do in the project. For example, a user with the Admin role can do everything in the project, while a user with the Read Only role can only view the project.

A member may have different roles assigned to them in different projects. For example, a user may be an Admin in one project and a Read Only user in another project. This allows you to control what users can do in each project.

To learn more about project members and roles, see Members and Permissions Overview.

# Creating a project

To create a project, you'll need the Create Projects org permission.

To create a new project:

  1. Click the name of the current project in the top-right corner of the screen.

  2. Click New Project.

  3. Enter a name for your project, and select your project's default time zone.

  4. Under Unique Identifier, select the project type you prefer. This setting determines how users are uniquely identified in your project.

    • Hybrid projects use both email and userId as unique identifiers.
    • UserID-based projects use userId as a unique identifier.
    • Email-based projects uses email as a unique identifier. (Limited availability: Only certain accounts have the option to create new email-based projects - learn more.)

    After you make a selection, this setting can't be changed.

    To learn more about project types and unique identifiers and how to select a project type, see Project Types and Unique Identifiers.

  5. Click Create to finish.

Creating a new project

Next steps after creating a project:

# Editing a project

To edit a project's settings, go to Settings > Project Settings. Here, you can update the project's name, time zone, locales, and more. To learn more about the settings on this page, see Project Settings.

# Deleting a project

To delete or archive a project, please contact your Iterable customer success manager.

IMPORTANT

When a project has been archived for 30 days, all user data is automatically deleted from that project. Before archiving a project, make sure to back up any user data you want to keep.

# Want to learn more?

For more information about some of the topics in this article, check out this Iterable Academy course. Iterable Academy is open to everyone — you don't need to be an Iterable customer!

Related articles