Skip to main content

Manage projects

Group your experiences into projects and control which team members can view or edit the experiences in each one.

Written by Cody Iddings

Projects group related experiences together and control which team members can view or edit them.

Note: The Growth plan includes a set number of projects, as well as All access. For more, contact your account manager.

How projects work

Every Makeshapes organization starts with an "All access" project that contains all experiences by default. You can create additional custom projects to better organize your content and manage team access.

What projects are for

  • Organization: Group related experiences together

  • Access control: Control who can view or edit specific experiences

  • Team collaboration: Assign team members to relevant projects only

  • Dashboard filtering: Find experiences by choosing a project in the sidebar

Create a project

Only administrators can create projects.

  1. On the Your Experiences page, click Create a new project.

  2. Enter a Name, and choose an Icon and its color.

  3. Under Invite users, add the team members who should have access, and choose whether each one is an Editor or a Viewer. Administrators already have access.

  4. Click Create.

Change a project

Edit a project

  1. On the Your Experiences page, choose the project in the sidebar.

  2. At the top of the page, click the project's icon and name. The Edit project dialog opens.

  3. Change the name, icon or color.

  4. Click Save.

Add team members to a project

  1. In the Edit project dialog, under Invite users, search for the team member and select them.

  2. Choose their role: Editor can view and edit the project's experiences, and Viewer can view them but not make changes.

  3. Click Save.

Remove team members from a project

  1. In the Edit project dialog, find the team member.

  2. Click the remove button next to their name.

  3. Click Save.

Tip: You can also change a team member's project access in Organisation settings, on the Manage team tab.

Add experiences to a project

A new experience

When you create an experience, choose its project from the Project list. If you create it while a project is selected in the sidebar, that project is chosen for you.

An existing experience

Use one of these:

  • On the experience's card, open its ••• menu, point to Move to project, and choose the project.

  • Drag the card onto a project in the sidebar.

  • In the experience, open the Settings tab, and choose a project from the Project card.

The experience moves straight away.

Note: Each experience can only belong to one project at a time.

Filter the dashboard by project

The dashboard sidebar shows all your projects for easy filtering:

  • Home: Shows all experiences across all projects

  • All access: Shows experiences in the default project

  • Your other projects: Show the experiences in each project

Click a project in the sidebar to see only its experiences. At the top of the page, Can edit or View only shows your access to that project.

Roles and permissions

Organization roles

  • Administrator: Full access to all projects and can manage project settings

  • Editor: Can be assigned as Editor or Viewer on specific projects

  • Analytics: Can be assigned as Viewer on projects and access analytics

Project roles

  • Editor: Full editing access to experiences in the project

  • Viewer: Read-only access, marked View only

Project rules

The All access project

  • Cannot be deleted

  • Always exists in every organization

  • New experiences default to this project if no other is selected

  • Only appears for team members with the Editor role. Someone with the Analytics role but not Editor doesn't see it

Creating and deleting projects

  • Only administrators can create a project

  • A project with experiences in it can't be deleted. Move its experiences to other projects first, and then click Delete project in the Edit project dialog

Access

  • Analytics users can only have Viewer role on projects

  • Administrators automatically have Editor access to all projects

  • Users must have Editor organization role to be assigned as Editor on projects

Tips

  • Use clear names: Choose clear, descriptive names for your projects

  • Organize by purpose: Group experiences by topic, client, or campaign

  • Give the least access needed: Only give Editor access to team members who need to make changes

  • Use icons and colors: Visual identifiers help team members find the right project

  • Review regularly: Periodically review project membership and remove inactive users

Troubleshooting

Can't delete a project?

  • Check to ensure you are an administrator

  • Check if the project contains experiences

  • Move experiences to other projects first

Team member can't edit experiences?

  • Check they have the Editor role in your organization

  • Check they're an Editor on the project

Don't see a project in the dashboard?

  • Check if you're a member of that project

  • Contact your administrator to be added to the project

Did this answer your question?