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 Experiences page, click Create project.

    The Experiences page, with the Create project button highlighted.
  2. Enter a Name, and choose an Icon and its color.

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

    The Create project dialog, with a name and icon chosen and the Invite team members field highlighted.
  4. Click Create.

Change a project

Only administrators can change a project.

Edit a project

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

  2. In the project's heading, click Edit project. The Edit project dialog opens.

    The Onboarding project's page, with the Edit project button in its heading highlighted.
  3. Change the name, icon or color.

  4. Click Save.

Add team members to a project

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

    The Edit project dialog, with the Invite team members field highlighted and the team members already in the project listed under it.
  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 under Organisation in the sidebar, on the Manage team page.

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

Only administrators can move an experience to another project. Use one of these:

  • On the experience's card, click its more button, named More for and the experience's name, such as More for Safety drill. Then point to Move to project, and choose the project.

    An experience card's menu open, with Move to project highlighted and the list of projects beside it.
  • Drag the card onto a project in the sidebar.

  • In the experience, click Settings in the experience's sidebar, and then choose a project from the Project card. The experience's sidebar starts folded to icons and stays the way you leave it: hover an icon to see its name, or click the logo or drag its edge to open it.

    The Settings page of Mentally healthy together, with the Project card highlighted.

If the move would let more people see the experience's files, a dialog asks first. Its title is Move to and the project's name, such as Move to Leadership?, and it names the files. Click Move to continue. Otherwise the experience moves straight away.

The Move to Onboarding? dialog, listing the file that would also be shared with Onboarding.

Note: Each experience can only belong to one project at a time. A copy made with Duplicate stays in the same project as the original.

Filter the dashboard by project

The sidebar lists your projects for easy filtering:

  • All experiences: Shows all experiences across all projects

  • All access: Shows experiences in the default project

  • Your other projects: Show the experiences in each project

The sidebar shows the projects you pinned, or the first five until you pin some. To see the rest, click More projects.

To see only a project's experiences, click it in the sidebar. The members button, labeled with the number of members such as 3 members, shows who has access to the project. Click it to see each person with Can edit or Can view. An administrator can click Edit access to change who is in the project. If you can only view the project, a View only badge follows its name.

A project's page, with the members button highlighted in the project's heading.

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

Create and delete projects

  • Only administrators can create a project

  • To delete a project, in the Edit project dialog, click More and then Delete project. A project with experiences in it can be deleted: its experiences move to All access. The dialog says how many experiences move and, if some files are limited to this project, how many will become visible to everyone in the company.

    The Edit project dialog with its More menu open and Delete project highlighted.
    The Delete Safety incidents? dialog, saying its experience moves to All access and 2 files will become visible to everyone.
  • Every administrator can also manage and delete projects under Organisation in the sidebar, on the Projects page. Click Create project, or click More for and the project's name, and then choose Manage project or Delete project

    The Projects page under Organisation, with a project's menu open showing Manage project and Delete project.

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

Files and projects

Files can belong to projects too. A file that belongs to a project is visible to that project's members and to administrators only. Where a file starts depends on where you upload it:

  • Files you upload inside an experience that belongs to a project go to that project only

  • Files you add on the Media page, or inside an All access experience, go to everyone in the company

Upload files shows where your files will go: the project's name, or All access. Files uploaded earlier stay visible to everyone until someone limits them.

Moving or deleting an experience says what happens to its files:

  • When a move lets more people see an experience's files, the dialog names those files and says where they stay visible. The files stay where they were as well.

  • When you move an experience from All access into a project, Take out of All access lists its files. Files that no other experience needs in All access are selected, and they leave All access when you click Move.

  • When you delete an experience in a project, Also delete its files lists files that only that experience used. None are selected until you select them.

    The Delete this experience? dialog, with Also delete its files highlighted and its file not selected.

For how to see and change who can see a file, see Manage media content.

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 you are an administrator

  • If a message says someone else is changing a file, wait a moment and try again

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?