Organise experiences and control team access using projects in Makeshapes
Projects are a powerful way to organise your experiences and control team access within your Makeshapes organisation. With projects, you can group related experiences together and assign specific team members with appropriate permissions.
Understanding Projects
Every Makeshapes organisation starts with an "All access" project that contains all experiences by default. You can create additional custom projects to better organise your content and manage team access.
Key benefits of Projects:
Organisation: 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: Easily find experiences by filtering by project
Creating a new project
Navigate to Organisation from the main menu
Click on the Projects tab
Click the "Add new project" button
Fill in the project details: Name: Enter a descriptive name for your project Icon: Choose from the available icon options Color: Select a color to help identify your project Invite users: Choose team members you want to have access. Admins already have access.
Click "Create" to save your new project
Managing project settings
Editing a project
Go to Organisation → Projects
Find your project in the list
Click the menu button (⋯) next to the project name
Select "Manage project"
Update the name, icon, or color as needed
Click "Save" to apply changes
Adding team members to projects
In the "Manage project" modal, use the search field to find team members
Select a user from the dropdown
Choose their role: Editor: Can view and edit experiences in the project Viewer: Can view experiences but cannot make changes
Click "Save" to apply the changes
Removing team members
In the "Manage project" modal, find the team member
Click the (-) button next to their name
Click "Save" to confirm the removal
Tip: You can also manage a team member's access in the Team Member tab.
Adding experiences to projects
For new experiences:
When creating a new experience, you'll see a Project dropdown
Select the appropriate project from the list
The experience will be created in that project
For existing experiences:
Use the project dropdown in the three-dot settings button on the card in the dashboard.
Or, Open the experience you want to move
Go to the Settings tab
Use the Project dropdown to select a new project
The experience will be moved immediately
Note: Each experience can only belong to one project at a time.
Using project filters on the dashboard
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
Custom Projects: Shows experiences specific to each project
Filtering by project:
Click on any project name in the sidebar
The dashboard will display only experiences from that project
You'll see role indicators (like "View only") if you have limited access
Understanding project roles and permissions
Organisation-Level 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-level roles:
Editor: Full editing access to experiences in the project
Viewer: Read-only access with "View only" indicators displayed
Important project rules
Default "All access" project:
Cannot be deleted
Always exists in every organisation
New experiences default to this project if no other is selected
Appears for Editors only. If a team member is "Analytics" role and not "Editor" role, "All access" will not appear
Project creation and deletion:
Only administrators can create a project
Projects with experiences cannot be deleted. Move all experiences to other projects first. Empty projects can be deleted freely
Access control:
Analytics users can only have Viewer role on projects
Administrators automatically have Editor access to all projects
Users must have Editor organisation role to be assigned as Editor on projects
Tips for effective project management
Use Descriptive Names: Choose clear, descriptive names for your projects
Organise by Purpose: Group experiences by topic, client, or campaign
Set Appropriate Permissions: Only give Editor access to team members who need to make changes
Use Icons and Colors: Visual identifiers help team members quickly find the right project
Regular Review: 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?
Verify they have Editor role in the Organisation
Verify they have Editor permission 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