Module 2: Allocating Projects
In this module:
- Inviting users to projects.
- Accepting invitations.
- Editing, upgrading, and removing users from projects.
- Deleting and modifying projects.
And a bit of help:
Module 2 video
Prefer to read along?
Click CC to enable captions in YouTube or read the full transcript below.
Module 2 practice quiz
FYI: All of the questions on the final exam are taken from the practice quizzes!
- Click here to take the practice quiz for Module 2
- Click here to review the quiz answers
Show Notes № 2
- Admin Extras: Creating starter projects for Standard users
- Admin Extras: Finding and customizing starter projects as a Standard user
- Core Certification Module 2: All About Creating Surveys
- Survey Types section of the Help Center
Quiz answers
Read the transcript
If you wish to follow along with the script, or just prefer reading, a complete transcript of the video can be seen below.
Welcome to Module 2 of the Delighted Admin Certification: Allocating Projects.
Now that you’ve identified your users, let’s give them some projects to work on! Projects are created independently from users. This means if you delete a project, you will not accidentally delete any users joined to the project (and vice versa—deleting a user won’t delete the projects they’ve created).
Users are invited, by Admins, to join specific projects. This begs the question, “Which comes first, the project or the user?” The answer is . . . (drumroll please):
The Project! To put it succinctly, you can’t invite someone to a survey that doesn’t exist.
Well, that’s not entirely true. You can make someone an Admin user and they can create their own projects at will. However, this freedom is not afforded to Limited and Standard users who are totally dependent on you (or your fellow Admins) for their survey projects.
For Standard and Limited users, you’re faced with two options. You can: assign Limited and Standard users to already existing projects, or create “starter” projects from scratch for Standard users to begin working with (Limited users don’t get to play).
To invite a user to an existing project:
- Choose Users from the Account menu
- Enter their email address
- Select their Role from the drop-down menu (either Limited, Standard, or Admin)
- Open the Select projects dropdown menu to assign projects (This step only applies to Standard and Limited users, since Admins have access to all projects in your account)
- Click “Send invite” to, well, send your invite!
Say you want a Standard user to build their own project, rather than doing all the work for them. What we need to do in this case is to create a “starter” project for them, consisting of just the shell of a project.
To create a Starter project, simply create a new project, select the survey type, then jump back to the Account menu to assign that project to a user. To learn more about this process, check out Admin Extras (linked in the Show Notes).
Remember that, as an Admin, you’ll always be able to see every project, make any necessary changes, and even reassign a project if a user leaves your company or drops the ball. (The show must go on!)
When you invite a new user, the invite will be sent via email. The new user will click “Join” in the invitation email, and then click “Join” to complete the process once logged in!
There will be times when old projects will have served their purpose, and times when you want to tweak existing surveys. When you’re working on updating a survey, you can create a new project or modify an existing project.
Delighted’s advice is to create a new project when you wish to: change the survey type—NPS, CSAT, CES, etc., survey a new touchpoint in the customer journey, or separate new data entirely from any previous feedback.
Otherwise, modifying an existing project has its merits. Modify an existing project when you are happy with the existing survey type and, either: you are asking the same basic question to a new demographic, or you are running a relational NPS, CSAT or similar survey and it’s time to send again.
In the first case, you can use properties to identify which demographic you’re surveying and filter your older data by date to isolate each audience's responses.
For the second case, there is little reason to have one project called NPS Q3 2022 and another named NPS Q1 2023. Use a single NPS project for both and tap into Properties and Date filters to distinguish one survey outreach from the next—which is very clever.
Delete old, sad, tired, or defunct projects and create new ones in their wake. Careful! Anyone with Admin access can delete some of your most valuable projects!
If you are deleting a project, it’s smart to download its data to a CSV or Excel file first.
To delete old projects: Open the Projects menu and click the Gear icon next to the project you wish to delete, choose Delete this project from the Edit Project window, and then after reviewing some severe warnings about the Perils of deleting a project, click Delete this project (without a care in the world).
Deleting a project is fairly drastic. When you click Delete this project you will be faced with a very serious looking screen detailing everything that will be removed if you continue. To succinctly summarize the list—“All is lost!”
Ah, but is it? If you click Delete this project and instantly regret it, Delighted will give you one last chance to Undo the damage! (Thank you, Delighted.)
However, if you close this notification by clicking the X there's no going back. (Sorry.)
If you do hit Undo and restore the project, it will reappear in the Projects menus for all of the users that were formerly assigned to it—like nothing ever happened.
You'll also receive a comforting email telling you that all is well.
It’s time to test your skills! I’ll give you a scenario, and you decide if it calls for modification of an existing project, or creation of a new one.
Here’s the first scenario: Eta, who runs Hem & Stitch’s HR team, just got wind that Hem & Stitch has a Delighted license. They want to set up an eNPS project to measure employee satisfaction with the company. This will be the first time that Hem & Stitch has ever measured eNPS. What should Eta do?
Eta should create a new project, since this survey will use a new survey type!
Now let’s take a look at Beta’s situation. In the last module, we learned that Beta is a Support Manager for Hem & Stitch. Beta wants to make a survey just like the existing CSAT one, but with all new Additional Questions for the new quarter. Should Beta start a new project, or modify the existing CSAT?
Since Beta is just adjusting the Additional Questions, modifying the project is the way to go! No previous data will be lost, and this way Beta can compare old responses to this quarter’s feedback.
Great work! That’s it for Module 2. We’ll see you soon for the next module!