Managing Project and Member Privacy
Privacy in a Social System Map is a particular kind of trust. People aren’t just
Reset your password
Enter your username or email address and we will send you a link to reset your password.
Back to loginCreate an account
Already have an account? Log inIf you have a list of members to add to your sumApp project, follow the steps below.
1. From the ‘Launch’ ‘Add members’ tab, select ‘Choose File’ to attach your CSV file.

Click “Template file” to download the recommended format and update with your member’s data. If you want to include a segment for each of your project members, you can bulk add them using this option.

Select your CSV file containing the member data from your device.
Once your file is attached and appears ready, choose ‘Open’ to close the upload window.
If you have pre-existing survey data and are on a Tier III or Tier IV plan, read How To Load Pre-Existing Data Into sumApp.
If you are running into error messages that are not easily fixed, please reach out to our Slack community. Common error types include missing first name or last name, missing email address, or duplicate email address(es) in CSV file.
Purpose of Segments
Segments are used to separate out your member list into smaller, more manageable chucks in the sumApp member view connections page. This is useful when you have large populations and don’t want to require everyone to go through the entire list. Segments are appropriate when there are subsets of the population that are more likely to know one another – for instance, if you’re mapping teachers in a school system, they’re more likely to know each other if they teach in the same school. Segments would allow the teachers to filter by school to shorten the list of names to those they are most likely to know.
To Know
- Segments are defined by the administrator, not the map users.
- If using Segments, there will be a drop-down filter on the sumApp connections page (where your members see the list of other members and indicate who they know).
- Each member’s segment shows on their member tile in the sumApp connections page.
- Each person can only belong to a single segment.
- Segments should be defined by something your map members have in common that makes it more likely they will know one another (such as school, or program, or department or in some cases fields or specialties). Commonalities that are not particularly useful are things like gender, age, broad interests. (those may be fine survey questions, but not helpful for identifying a sub-group one is most likely to know.
- Segments can be loaded via a CSV file, added manually in the member list, or manually from the add members page.
- If you use the Opt-in form, you can set that so that members can select their segment there.
- Segments are exported with the survey data and can be used in the map, but that is not their primary function.
- Segments aren’t useful in smaller groups where there aren’t existing sub-groups – if you don’t want too use Segments, you can choose not to have the segment drop down show in your member view – change it in the settings page.
What Segments Are Not
Segments are only meant to make defining connections easier in sumApp for members:
- They are not how you define filters in Kumu.
- You can use them as a filter in Kumu, but if that’s all you need it for, it’s better to create a field in the survey.
- They do not feed back into the survey in any way.
The video below gives a quick demo of how to sort map members by segment once they’re set up for your connections.

- Indicates what page you’re on, within your project.
- Indicates which project you’re currently working on.
- Shows you’re in the first tab of the project phases navigation bar – Launch.
- Shows your project status. Toggle on to enable project members to submit their survey responses.
- Shows you’re in the ‘add members’ tab of the Launch phase.
- Allows you to attach a with your members basic information. First Name, Last Name, Email, and [optional].
- Click the Template File link to download the template file to upload members by CSV.
- Manually add an individual new member using First Name, Last Name, Segment [optional].
- Add at least one email.
- Indicates you are on the manually add member section.
- Select ‘Submit’ when adding manual members or by CSV upload after attaching your CSV file.

Parts of the Workspace
- Indicates what page you’re on, within your project.
- Shows you’re in the third tab of the launch phases navigation bar – Manage members.
- Shows you’re on the list tab of manage members.
- Click to toggle to the create tab of manage members.
- Choose the carrot drop down to see menu options of within with selected.
- Displays members’ full name.
- Shows members’ primary email.
- Shows members’ secondary email, if provided.
- Shows members’ tertiary email, if provided.
- Shows members’ segment.
- Shows if invite email has been sent.
- Shows if invite link has been opened.
- Shows a checkmark if member has allowed receiving email updates.
- Shows a checkmark if member has allowed their member information to be exported.
- Shows a checkmark if the member has marked themselves as visible in the project map.
- Shows a checkmark if the member has agreed to your Terms of Agreement if required before submitting survey replies.
Why have three templates?
sumApp was designed to be what we call ‘evergreen’ – in other words, we wanted a tool that didn’t just create a snapshot in time, but could also continue to evolve as the network changes and as their mapping needs become more sophisticated. An important part of that evergreen characteristic means having the ability to add new members to the map’s databases as they join the network and to invite existing members back into sumApp to show their existing relationships to the new members.
On the one hand, doing that that can be as simple as deciding never to close a survey. But if your bulk email invitations don’t differentiate which phase you’re asking members to address, you’ll confuse and annoy people. It would be bad form to ask members to do something they’ve already done, without:
- Explaining that you’re not implying they didn’t do it.
- Making clear that it’s not a re-do – that what they’ve done is safe and intact.
- Making it clear that the reason you’re asking them back is because something has changed and those changes might be relevant for them to address.
- Making sure they know it will be a super-quick thing.
- Such as: “please go take a quick peek at the 10 brand new members at the top of the list, and if you know any, share that – then you’re done!”
So – in another SNA tool, you maybe COULD simply keep the survey open (tho, naaaw, it’d still be messy for other technical reasons, but we’ll ignore those right now . . . ),
but you’d have to revise the email over and over depending on who you’re sending to.
We thought that was dumb. So we make it easier by using three different email templates, each meant to be framed for a different context, depending on what stage your members are at in the evergreen cycle.
- The initial invitation – Frame this text for the brand-new member who has never seen sumApp & has no idea what you’re up to.
- The ‘new faces’ email – Frame this one for the initiated. Those who’ve done sumApp already, or at least have chosen to ignore previous invites (they know it’s been happening whether they’ve engaged or not). Framing in ‘new faces’ should, ideally, include all the bullet points above.
- The ‘reminder’ email – This is a follow-up framed generically for everyone. Use it when you want to address everyone at once.
The email template interface
Features of the email template interface:
1) Shows you’re in the sumApp setup phase.
2) Shows you’re on the ‘define email templates’ page.
3) Input name of sender here. This is a required field. Use a name that is as recognizable as possible for the whole population. All templates will come from this sender.
4) Input email of sender. This is a required field. Can be a different email than that belonging to the ‘from’ person’s name.
5) Deadline. Not required. Will fill into the template where you’ve inserted the {survey_deadline} tag. It has no functional effect (it won’t close your survey on that date). It’s simply there to make it easy to insert a date into your emails and change it in a single place, instead of digging into each email template to change it.
6) Field tags you can use in your email. {url} is required in each email template. No other fields are required. Read more about the curly-bracket tags.
7) The Invitation Email template WYSIWYG. More about the WYSIWYG interface.
8) The New Faces Email template WYSIWYG. More about the WYSIWYG interface.
9) The Reminder Email template WYSIWYG. More about the WYSIWYG interface.
10) Cancel – this will remove all changes you’ve made since your last save.
11) Save – Don’t forget to save when you’ve made changes anywhere on this page!!
Email template tags:
You find these fields at the top of the Email Templates page – they apply to each email type in your project:
1) Input name of sender here. This is a required field. Use a name that is as recognizable as possible for the whole population. All templates will come from this sender.
2) Input email of sender. This is a required field. Can be a different email than that belonging to the ‘from’ person’s name.
3) Deadline. Not required. Will fill into the template where you’ve inserted the {survey_deadline} tag. It has no functional effect (it won’t close your survey on that date). It’s simply there to make it easy to insert a date into your emails and change it in a single place, instead of digging into each email template to change it.
You also have tags that can be used in your email templates. They function as placeholders for inserting data from other fields within sumApp into the emails. They include:
4) {first_name} inserts the first name of the member receiving the email. Not mandatory.
5) {last_name} inserts the last name of the member receiving the email. Not mandatory.
6) {network_name} inserts the project name, which you can see at the top of the page. Not mandatory.
7) {survey_deadline} inserts the date in field #3 ‘Deadline’. Not mandatory.
8) {url} inserts the unique sumApp url belonging to the user receiving the email. This field is mandatory for all three templates.
9) {segment} inserts the segment you’re assigned to the user receiving the email, if you’ve assigned one. Not mandatory.
10 {sender_name} Inserts the name in the 3@ above ‘Sender email’. Not mandatory in the body of the email.
and again – a reminder 11) the {url} tag is mandatory for all email templates. If you’ve removed it, the save button won’t work until you replace it in all 3 templates.
The WYSIWYG
What is a WYSIWYG editor?
HTML markup tells a web browser how to display the text, images and other forms of multimedia on a webpage. A WYSIWYG is an interface designed to editing HTML without having to know or see the underlying code.
It it beyond the scope of this knowledge base to explain all the parts of this particular WYSIWYG interface, but we’ll point out a few basics.
1) Indicates which template you’re working on.
2) Defines the email’s subject line – it can include tags if desired.
3) The body of the email is edited in within the WYSIWYG editor.
A common cause of frustration using WYSIWYG editors:
You’ll often copy text from another editing tool into the email template. For instance if you’ve collaborated on the text in a google doc, or you’re pasting from Word. Each of those tools uses underlying code (such as HTML) to tell the browser or application how to render the content (headers, etc.)
Often when copying and pasting text from one editor into another, you also inadvertently copy over a bunch of hidden code as well. Sometimes that works fine & you get the formatting you want, but often it turns into a challenge. You can prevent this by copying your text into a non-formatting editor, such as NotePad before pasting it into the WYSWYG.
But if you haven’t already stripped the hidden code from your text before inserting it into a WYSIWYG, if the editor starts to behave strangely – such as not implementing changes you’re trying to make, you usually need to either examine the underlying HTML to remove junk code, or simply strip all formatting out of the text and start formatting fresh. You can either ‘view source’ or ‘remove formatting’.
4) The ‘source’ button in the WYSIWYG dashboard enables you to examine and edit the underlying HTML code. Even if you have no idea what HTML is, taking a peek will give you at least a sense of what’s going on.
5) The Tx icon will remove all hidden formatting code from the text so you can start fresh. The text to be cleaned must be selected first. You can double-check that it got removed by looking at the source code under #4.
The other buttons in the WYSWYG dashboard are either self-explanatory or not that relevant in this context.
6) If you want to start over, select ‘Reset Default’
7) The green ‘Preview’ button enables you to preview your content.
Once you’ve edited each template – don’t forget to click ‘save’ at the bottom of the page!
How sending works with each template
You send emails from the Launch > Manage Invitations page in sumApp.
Here is an overview explaining when each type is sent.
Invitation Email
- Is sent when you click the ‘Send Invitation Emails’ button or the ‘Send Invitation & New Faces Emails’ button in Launch > Manage Invitations page. It will only go out to members who have never previously been sent the first invitation.
- You can also send the Invitation Email to anyone, regardless of if they’ve been sent it before, on a case-by-case basis in the member list in Launch > Manage Members.
New Faces Email
- Is sent when you click the ‘Send Invitation & New Faces Emails’ button or the ‘Send New Faces Emails’ button in Launch > Manage Invitations page. It will only go out to members who have ALREADY been sent the first invitation at some point in the past.
- You can also send the New Faces Email to anyone, regardless of what they’ve been sent it before, on a case-by-case basis in the member list in Launch > Manage Members.
Reminder Email
- Is sent when you click the the ‘Send Reminders’ button in Launch > Manage Invitations page. It will go out to everyone in your member list, regardless of what they’ve been sent in the past.
- You can also send the Reminder Email to anyone, regardless of what they’ve been sent it before, on a case-by-case basis in the member list in Launch > Manage Members.
Custom survey filter email template – Tier IV
If you’re using the custom survey filter feature in Tier IV, you have another email template option. You can send a custom email to a sub-set of the population, based on their responses to the custom filter survey question you’re using.
You can access this extra functionality in Launch > Manage Invitations – Under the ‘Actions’ section of the page, find and click on the 5th sending button ‘Custom Filter Email’.
Why have three templates?
sumApp was designed to be what we call ‘evergreen’ – in other words, we wanted a tool that didn’t just create a snapshot in time, but could also continue to evolve as the network changes and as their mapping needs become more sophisticated. An important part of that evergreen characteristic means having the ability to add new members to the map’s databases as they join the network and to invite existing members back into sumApp to show their existing relationships to the new members.
On the one hand, doing that that can be as simple as deciding never to close a survey. But if your bulk email invitations don’t differentiate which phase you’re asking members to address, you’ll confuse and annoy people. It would be bad form to ask members to do something they’ve already done, without:
- Explaining that you’re not implying they didn’t do it.
- Making clear that it’s not a re-do – that what they’ve done is safe and intact.
- Making it clear that the reason you’re asking them back is because something has changed and those changes might be relevant for them to address.
- Making sure they know it will be a super-quick thing.
- Such as: “please go take a quick peek at the 10 brand new members at the top of the list, and if you know any, share that – then you’re done!”
So – in another SNA tool, you maybe COULD simply keep the survey open (tho, naaaw, it’d still be messy for other technical reasons, but we’ll ignore those right now . . . ),
but you’d have to revise the email over and over depending on who you’re sending to.
We thought that was dumb. So we make it easier by using three different email templates, each meant to be framed for a different context, depending on what stage your members are at in the evergreen cycle.
- The initial invitation – Frame this text for the brand-new member who has never seen sumApp & has no idea what you’re up to.
- The ‘new faces’ email – Frame this one for the initiated. Those who’ve done sumApp already, or at least have chosen to ignore previous invites (they know it’s been happening whether they’ve engaged or not). Framing in ‘new faces’ should, ideally, include all the bullet points above.
- The ‘reminder’ email – This is a follow-up framed generically for everyone. Use it when you want to address everyone at once.
The email template interface
Features of the email template interface:
1) Shows you’re in the sumApp setup phase.
2) Shows you’re on the ‘define email templates’ page.
3) Input name of sender here. This is a required field. Use a name that is as recognizable as possible for the whole population. All templates will come from this sender.
4) Input email of sender. This is a required field. Can be a different email than that belonging to the ‘from’ person’s name.
5) Deadline. Not required. Will fill into the template where you’ve inserted the {survey_deadline} tag. It has no functional effect (it won’t close your survey on that date). It’s simply there to make it easy to insert a date into your emails and change it in a single place, instead of digging into each email template to change it.
6) Field tags you can use in your email. {url} is required in each email template. No other fields are required. Read more about the curly-bracket tags.
7) The Invitation Email template WYSIWYG. More about the WYSIWYG interface.
8) The New Faces Email template WYSIWYG. More about the WYSIWYG interface.
9) The Reminder Email template WYSIWYG. More about the WYSIWYG interface.
10) Cancel – this will remove all changes you’ve made since your last save.
11) Save – Don’t forget to save when you’ve made changes anywhere on this page!!
Email template tags:
You find these fields at the top of the Email Templates page – they apply to each email type in your project:
1) Input name of sender here. This is a required field. Use a name that is as recognizable as possible for the whole population. All templates will come from this sender.
2) Input email of sender. This is a required field. Can be a different email than that belonging to the ‘from’ person’s name.
3) Deadline. Not required. Will fill into the template where you’ve inserted the {survey_deadline} tag. It has no functional effect (it won’t close your survey on that date). It’s simply there to make it easy to insert a date into your emails and change it in a single place, instead of digging into each email template to change it.
You also have tags that can be used in your email templates. They function as placeholders for inserting data from other fields within sumApp into the emails. They include:
4) {first_name} inserts the first name of the member receiving the email. Not mandatory.
5) {last_name} inserts the last name of the member receiving the email. Not mandatory.
6) {network_name} inserts the project name, which you can see at the top of the page. Not mandatory.
7) {survey_deadline} inserts the date in field #3 ‘Deadline’. Not mandatory.
8) {url} inserts the unique sumApp url belonging to the user receiving the email. This field is mandatory for all three templates.
9) {segment} inserts the segment you’re assigned to the user receiving the email, if you’ve assigned one. Not mandatory.
10 {sender_name} Inserts the name in the 3@ above ‘Sender email’. Not mandatory in the body of the email.
and again – a reminder 11) the {url} tag is mandatory for all email templates. If you’ve removed it, the save button won’t work until you replace it in all 3 templates.
The WYSIWYG
What is a WYSIWYG editor?
HTML markup tells a web browser how to display the text, images and other forms of multimedia on a webpage. A WYSIWYG is an interface designed to editing HTML without having to know or see the underlying code.
It it beyond the scope of this knowledge base to explain all the parts of this particular WYSIWYG interface, but we’ll point out a few basics.
1) Indicates which template you’re working on.
2) Defines the email’s subject line – it can include tags if desired.
3) The body of the email is edited in within the WYSIWYG editor.
A common cause of frustration using WYSIWYG editors:
You’ll often copy text from another editing tool into the email template. For instance if you’ve collaborated on the text in a google doc, or you’re pasting from Word. Each of those tools uses underlying code (such as HTML) to tell the browser or application how to render the content (headers, etc.)
Often when copying and pasting text from one editor into another, you also inadvertently copy over a bunch of hidden code as well. Sometimes that works fine & you get the formatting you want, but often it turns into a challenge. You can prevent this by copying your text into a non-formatting editor, such as NotePad before pasting it into the WYSWYG.
But if you haven’t already stripped the hidden code from your text before inserting it into a WYSIWYG, if the editor starts to behave strangely – such as not implementing changes you’re trying to make, you usually need to either examine the underlying HTML to remove junk code, or simply strip all formatting out of the text and start formatting fresh. You can either ‘view source’ or ‘remove formatting’.
4) The ‘source’ button in the WYSIWYG dashboard enables you to examine and edit the underlying HTML code. Even if you have no idea what HTML is, taking a peek will give you at least a sense of what’s going on.
5) The Tx icon will remove all hidden formatting code from the text so you can start fresh. The text to be cleaned must be selected first. You can double-check that it got removed by looking at the source code under #4.
The other buttons in the WYSWYG dashboard are either self-explanatory or not that relevant in this context.
6) If you want to start over, select ‘Reset Default’
7) The green ‘Preview’ button enables you to preview your content.
Once you’ve edited each template – don’t forget to click ‘save’ at the bottom of the page!
How sending works with each template
You send emails from the Launch > Manage Invitations page in sumApp.
Here is an overview explaining when each type is sent.
Invitation Email
- Is sent when you click the ‘Send Invitation Emails’ button or the ‘Send Invitation & New Faces Emails’ button in Launch > Manage Invitations page. It will only go out to members who have never previously been sent the first invitation.
- You can also send the Invitation Email to anyone, regardless of if they’ve been sent it before, on a case-by-case basis in the member list in Launch > Manage Members.
New Faces Email
- Is sent when you click the ‘Send Invitation & New Faces Emails’ button or the ‘Send New Faces Emails’ button in Launch > Manage Invitations page. It will only go out to members who have ALREADY been sent the first invitation at some point in the past.
- You can also send the New Faces Email to anyone, regardless of what they’ve been sent it before, on a case-by-case basis in the member list in Launch > Manage Members.
Reminder Email
- Is sent when you click the the ‘Send Reminders’ button in Launch > Manage Invitations page. It will go out to everyone in your member list, regardless of what they’ve been sent in the past.
- You can also send the Reminder Email to anyone, regardless of what they’ve been sent it before, on a case-by-case basis in the member list in Launch > Manage Members.
Custom survey filter email template – Tier IV
If you’re using the custom survey filter feature in Tier IV, you have another email template option. You can send a custom email to a sub-set of the population, based on their responses to the custom filter survey question you’re using.
You can access this extra functionality in Launch > Manage Invitations – Under the ‘Actions’ section of the page, find and click on the 5th sending button ‘Custom Filter Email’.
Why have three templates?
sumApp was designed to be what we call ‘evergreen’ – in other words, we wanted a tool that didn’t just create a snapshot in time, but could also continue to evolve as the network changes and as their mapping needs become more sophisticated. An important part of that evergreen characteristic means having the ability to add new members to the map’s databases as they join the network and to invite existing members back into sumApp to show their existing relationships to the new members.
On the one hand, doing that that can be as simple as deciding never to close a survey. But if your bulk email invitations don’t differentiate which phase you’re asking members to address, you’ll confuse and annoy people. It would be bad form to ask members to do something they’ve already done, without:
- Explaining that you’re not implying they didn’t do it.
- Making clear that it’s not a re-do – that what they’ve done is safe and intact.
- Making it clear that the reason you’re asking them back is because something has changed and those changes might be relevant for them to address.
- Making sure they know it will be a super-quick thing.
- Such as: “please go take a quick peek at the 10 brand new members at the top of the list, and if you know any, share that – then you’re done!”
So – in another SNA tool, you maybe COULD simply keep the survey open (tho, naaaw, it’d still be messy for other technical reasons, but we’ll ignore those right now . . . ),
but you’d have to revise the email over and over depending on who you’re sending to.
We thought that was dumb. So we make it easier by using three different email templates, each meant to be framed for a different context, depending on what stage your members are at in the evergreen cycle.
- The initial invitation – Frame this text for the brand-new member who has never seen sumApp & has no idea what you’re up to.
- The ‘new faces’ email – Frame this one for the initiated. Those who’ve done sumApp already, or at least have chosen to ignore previous invites (they know it’s been happening whether they’ve engaged or not). Framing in ‘new faces’ should, ideally, include all the bullet points above.
- The ‘reminder’ email – This is a follow-up framed generically for everyone. Use it when you want to address everyone at once.
The email template interface
Features of the email template interface:
1) Shows you’re in the sumApp setup phase.
2) Shows you’re on the ‘define email templates’ page.
3) Input name of sender here. This is a required field. Use a name that is as recognizable as possible for the whole population. All templates will come from this sender.
4) Input email of sender. This is a required field. Can be a different email than that belonging to the ‘from’ person’s name.
5) Deadline. Not required. Will fill into the template where you’ve inserted the {survey_deadline} tag. It has no functional effect (it won’t close your survey on that date). It’s simply there to make it easy to insert a date into your emails and change it in a single place, instead of digging into each email template to change it.
6) Field tags you can use in your email. {url} is required in each email template. No other fields are required. Read more about the curly-bracket tags.
7) The Invitation Email template WYSIWYG. More about the WYSIWYG interface.
8) The New Faces Email template WYSIWYG. More about the WYSIWYG interface.
9) The Reminder Email template WYSIWYG. More about the WYSIWYG interface.
10) Cancel – this will remove all changes you’ve made since your last save.
11) Save – Don’t forget to save when you’ve made changes anywhere on this page!!
Email template tags:
You find these fields at the top of the Email Templates page – they apply to each email type in your project:
1) Input name of sender here. This is a required field. Use a name that is as recognizable as possible for the whole population. All templates will come from this sender.
2) Input email of sender. This is a required field. Can be a different email than that belonging to the ‘from’ person’s name.
3) Deadline. Not required. Will fill into the template where you’ve inserted the {survey_deadline} tag. It has no functional effect (it won’t close your survey on that date). It’s simply there to make it easy to insert a date into your emails and change it in a single place, instead of digging into each email template to change it.
You also have tags that can be used in your email templates. They function as placeholders for inserting data from other fields within sumApp into the emails. They include:
4) {first_name} inserts the first name of the member receiving the email. Not mandatory.
5) {last_name} inserts the last name of the member receiving the email. Not mandatory.
6) {network_name} inserts the project name, which you can see at the top of the page. Not mandatory.
7) {survey_deadline} inserts the date in field #3 ‘Deadline’. Not mandatory.
8) {url} inserts the unique sumApp url belonging to the user receiving the email. This field is mandatory for all three templates.
9) {segment} inserts the segment you’re assigned to the user receiving the email, if you’ve assigned one. Not mandatory.
10 {sender_name} Inserts the name in the 3@ above ‘Sender email’. Not mandatory in the body of the email.
and again – a reminder 11) the {url} tag is mandatory for all email templates. If you’ve removed it, the save button won’t work until you replace it in all 3 templates.
The WYSIWYG
What is a WYSIWYG editor?
HTML markup tells a web browser how to display the text, images and other forms of multimedia on a webpage. A WYSIWYG is an interface designed to editing HTML without having to know or see the underlying code.
It it beyond the scope of this knowledge base to explain all the parts of this particular WYSIWYG interface, but we’ll point out a few basics.
1) Indicates which template you’re working on.
2) Defines the email’s subject line – it can include tags if desired.
3) The body of the email is edited in within the WYSIWYG editor.
A common cause of frustration using WYSIWYG editors:
You’ll often copy text from another editing tool into the email template. For instance if you’ve collaborated on the text in a google doc, or you’re pasting from Word. Each of those tools uses underlying code (such as HTML) to tell the browser or application how to render the content (headers, etc.)
Often when copying and pasting text from one editor into another, you also inadvertently copy over a bunch of hidden code as well. Sometimes that works fine & you get the formatting you want, but often it turns into a challenge. You can prevent this by copying your text into a non-formatting editor, such as NotePad before pasting it into the WYSWYG.
But if you haven’t already stripped the hidden code from your text before inserting it into a WYSIWYG, if the editor starts to behave strangely – such as not implementing changes you’re trying to make, you usually need to either examine the underlying HTML to remove junk code, or simply strip all formatting out of the text and start formatting fresh. You can either ‘view source’ or ‘remove formatting’.
4) The ‘source’ button in the WYSIWYG dashboard enables you to examine and edit the underlying HTML code. Even if you have no idea what HTML is, taking a peek will give you at least a sense of what’s going on.
5) The Tx icon will remove all hidden formatting code from the text so you can start fresh. The text to be cleaned must be selected first. You can double-check that it got removed by looking at the source code under #4.
The other buttons in the WYSWYG dashboard are either self-explanatory or not that relevant in this context.
6) If you want to start over, select ‘Reset Default’
7) The green ‘Preview’ button enables you to preview your content.
Once you’ve edited each template – don’t forget to click ‘save’ at the bottom of the page!
How sending works with each template
You send emails from the Launch > Manage Invitations page in sumApp.
Here is an overview explaining when each type is sent.
Invitation Email
- Is sent when you click the ‘Send Invitation Emails’ button or the ‘Send Invitation & New Faces Emails’ button in Launch > Manage Invitations page. It will only go out to members who have never previously been sent the first invitation.
- You can also send the Invitation Email to anyone, regardless of if they’ve been sent it before, on a case-by-case basis in the member list in Launch > Manage Members.
New Faces Email
- Is sent when you click the ‘Send Invitation & New Faces Emails’ button or the ‘Send New Faces Emails’ button in Launch > Manage Invitations page. It will only go out to members who have ALREADY been sent the first invitation at some point in the past.
- You can also send the New Faces Email to anyone, regardless of what they’ve been sent it before, on a case-by-case basis in the member list in Launch > Manage Members.
Reminder Email
- Is sent when you click the the ‘Send Reminders’ button in Launch > Manage Invitations page. It will go out to everyone in your member list, regardless of what they’ve been sent in the past.
- You can also send the Reminder Email to anyone, regardless of what they’ve been sent it before, on a case-by-case basis in the member list in Launch > Manage Members.
Custom survey filter email template – Tier IV
If you’re using the custom survey filter feature in Tier IV, you have another email template option. You can send a custom email to a sub-set of the population, based on their responses to the custom filter survey question you’re using.
You can access this extra functionality in Launch > Manage Invitations – Under the ‘Actions’ section of the page, find and click on the 5th sending button ‘Custom Filter Email’.
Why have three templates?
sumApp was designed to be what we call ‘evergreen’ – in other words, we wanted a tool that didn’t just create a snapshot in time, but could also continue to evolve as the network changes and as their mapping needs become more sophisticated. An important part of that evergreen characteristic means having the ability to add new members to the map’s databases as they join the network and to invite existing members back into sumApp to show their existing relationships to the new members.
On the one hand, doing that that can be as simple as deciding never to close a survey. But if your bulk email invitations don’t differentiate which phase you’re asking members to address, you’ll confuse and annoy people. It would be bad form to ask members to do something they’ve already done, without:
- Explaining that you’re not implying they didn’t do it.
- Making clear that it’s not a re-do – that what they’ve done is safe and intact.
- Making it clear that the reason you’re asking them back is because something has changed and those changes might be relevant for them to address.
- Making sure they know it will be a super-quick thing.
- Such as: “please go take a quick peek at the 10 brand new members at the top of the list, and if you know any, share that – then you’re done!”
So – in another SNA tool, you maybe COULD simply keep the survey open (tho, naaaw, it’d still be messy for other technical reasons, but we’ll ignore those right now . . . ),
but you’d have to revise the email over and over depending on who you’re sending to.
We thought that was dumb. So we make it easier by using three different email templates, each meant to be framed for a different context, depending on what stage your members are at in the evergreen cycle.
- The initial invitation – Frame this text for the brand-new member who has never seen sumApp & has no idea what you’re up to.
- The ‘new faces’ email – Frame this one for the initiated. Those who’ve done sumApp already, or at least have chosen to ignore previous invites (they know it’s been happening whether they’ve engaged or not). Framing in ‘new faces’ should, ideally, include all the bullet points above.
- The ‘reminder’ email – This is a follow-up framed generically for everyone. Use it when you want to address everyone at once.
The email template interface
Features of the email template interface:
1) Shows you’re in the sumApp setup phase.
2) Shows you’re on the ‘define email templates’ page.
3) Input name of sender here. This is a required field. Use a name that is as recognizable as possible for the whole population. All templates will come from this sender.
4) Input email of sender. This is a required field. Can be a different email than that belonging to the ‘from’ person’s name.
5) Deadline. Not required. Will fill into the template where you’ve inserted the {survey_deadline} tag. It has no functional effect (it won’t close your survey on that date). It’s simply there to make it easy to insert a date into your emails and change it in a single place, instead of digging into each email template to change it.
6) Field tags you can use in your email. {url} is required in each email template. No other fields are required. Read more about the curly-bracket tags.
7) The Invitation Email template WYSIWYG. More about the WYSIWYG interface.
8) The New Faces Email template WYSIWYG. More about the WYSIWYG interface.
9) The Reminder Email template WYSIWYG. More about the WYSIWYG interface.
10) Cancel – this will remove all changes you’ve made since your last save.
11) Save – Don’t forget to save when you’ve made changes anywhere on this page!!
Email template tags:
You find these fields at the top of the Email Templates page – they apply to each email type in your project:
1) Input name of sender here. This is a required field. Use a name that is as recognizable as possible for the whole population. All templates will come from this sender.
2) Input email of sender. This is a required field. Can be a different email than that belonging to the ‘from’ person’s name.
3) Deadline. Not required. Will fill into the template where you’ve inserted the {survey_deadline} tag. It has no functional effect (it won’t close your survey on that date). It’s simply there to make it easy to insert a date into your emails and change it in a single place, instead of digging into each email template to change it.
You also have tags that can be used in your email templates. They function as placeholders for inserting data from other fields within sumApp into the emails. They include:
4) {first_name} inserts the first name of the member receiving the email. Not mandatory.
5) {last_name} inserts the last name of the member receiving the email. Not mandatory.
6) {network_name} inserts the project name, which you can see at the top of the page. Not mandatory.
7) {survey_deadline} inserts the date in field #3 ‘Deadline’. Not mandatory.
8) {url} inserts the unique sumApp url belonging to the user receiving the email. This field is mandatory for all three templates.
9) {segment} inserts the segment you’re assigned to the user receiving the email, if you’ve assigned one. Not mandatory.
10 {sender_name} Inserts the name in the 3@ above ‘Sender email’. Not mandatory in the body of the email.
and again – a reminder 11) the {url} tag is mandatory for all email templates. If you’ve removed it, the save button won’t work until you replace it in all 3 templates.
The WYSIWYG
What is a WYSIWYG editor?
HTML markup tells a web browser how to display the text, images and other forms of multimedia on a webpage. A WYSIWYG is an interface designed to editing HTML without having to know or see the underlying code.
It it beyond the scope of this knowledge base to explain all the parts of this particular WYSIWYG interface, but we’ll point out a few basics.
1) Indicates which template you’re working on.
2) Defines the email’s subject line – it can include tags if desired.
3) The body of the email is edited in within the WYSIWYG editor.
A common cause of frustration using WYSIWYG editors:
You’ll often copy text from another editing tool into the email template. For instance if you’ve collaborated on the text in a google doc, or you’re pasting from Word. Each of those tools uses underlying code (such as HTML) to tell the browser or application how to render the content (headers, etc.)
Often when copying and pasting text from one editor into another, you also inadvertently copy over a bunch of hidden code as well. Sometimes that works fine & you get the formatting you want, but often it turns into a challenge. You can prevent this by copying your text into a non-formatting editor, such as NotePad before pasting it into the WYSWYG.
But if you haven’t already stripped the hidden code from your text before inserting it into a WYSIWYG, if the editor starts to behave strangely – such as not implementing changes you’re trying to make, you usually need to either examine the underlying HTML to remove junk code, or simply strip all formatting out of the text and start formatting fresh. You can either ‘view source’ or ‘remove formatting’.
4) The ‘source’ button in the WYSIWYG dashboard enables you to examine and edit the underlying HTML code. Even if you have no idea what HTML is, taking a peek will give you at least a sense of what’s going on.
5) The Tx icon will remove all hidden formatting code from the text so you can start fresh. The text to be cleaned must be selected first. You can double-check that it got removed by looking at the source code under #4.
The other buttons in the WYSWYG dashboard are either self-explanatory or not that relevant in this context.
6) If you want to start over, select ‘Reset Default’
7) The green ‘Preview’ button enables you to preview your content.
Once you’ve edited each template – don’t forget to click ‘save’ at the bottom of the page!
How sending works with each template
You send emails from the Launch > Manage Invitations page in sumApp.
Here is an overview explaining when each type is sent.
Invitation Email
- Is sent when you click the ‘Send Invitation Emails’ button or the ‘Send Invitation & New Faces Emails’ button in Launch > Manage Invitations page. It will only go out to members who have never previously been sent the first invitation.
- You can also send the Invitation Email to anyone, regardless of if they’ve been sent it before, on a case-by-case basis in the member list in Launch > Manage Members.
New Faces Email
- Is sent when you click the ‘Send Invitation & New Faces Emails’ button or the ‘Send New Faces Emails’ button in Launch > Manage Invitations page. It will only go out to members who have ALREADY been sent the first invitation at some point in the past.
- You can also send the New Faces Email to anyone, regardless of what they’ve been sent it before, on a case-by-case basis in the member list in Launch > Manage Members.
Reminder Email
- Is sent when you click the the ‘Send Reminders’ button in Launch > Manage Invitations page. It will go out to everyone in your member list, regardless of what they’ve been sent in the past.
- You can also send the Reminder Email to anyone, regardless of what they’ve been sent it before, on a case-by-case basis in the member list in Launch > Manage Members.
Custom survey filter email template – Tier IV
If you’re using the custom survey filter feature in Tier IV, you have another email template option. You can send a custom email to a sub-set of the population, based on their responses to the custom filter survey question you’re using.
You can access this extra functionality in Launch > Manage Invitations – Under the ‘Actions’ section of the page, find and click on the 5th sending button ‘Custom Filter Email’.

- See a in your project.
- Send an to your member list.
- Send an to members who haven’t been invited and send am email to current members of who is new in your project.
- Send email to everyone in your project.
- Send a to your project members.

Parts of the Workspace
- Indicates what page you’re on, within your project.
- Shows you’re in the third tab of the launch phases navigation bar – Manage members.
- Shows you’re on the list tab of manage members.
- Click to toggle to the create tab of manage members.
- Choose the carrot drop down to see menu options of within with selected.
- Displays members’ full name.
- Shows members’ primary email.
- Shows members’ secondary email, if provided.
- Shows members’ tertiary email, if provided.
- Shows members’ segment.
- Shows if invite email has been sent.
- Shows if invite link has been opened.
- Shows a checkmark if member has allowed receiving email updates.
- Shows a checkmark if member has allowed their member information to be exported.
- Shows a checkmark if the member has marked themselves as visible in the project map.
- Shows a checkmark if the member has agreed to your Terms of Agreement if required before submitting survey replies.