Design the Settings per Project

Owned by Matt Kepple
Last updated: Jan 30, 2024
4 min read

This is the part of your onboarding process using Blueprints where you choose which settings to add to your projects.

image-20240130-140057.png

How to fill in the Settings per Project Blueprints Tab

image-20240130-140650.png

We recommend that you fill in the Projects per Project Template Blueprints tab first

Column of the spreadsheet

What it means and what to put in there

Column of the spreadsheet

What it means and what to put in there

Project

Name of the project.

How do I organise our work into projects?

If you do the same work but in several locations, have a separate project for each location.

  • You can always group all those projects together in an album later whenever you need to report on that workstream as a whole.

Each project has its own contacts, surveys, forms and settings. So have a project for each type of activity or service you provide.

Project Category

Name of the project category (these are called Project Forms or Project Templates)

Enable Waiting List

Mark Yes if you want to have a Waiting List on this project

Enable Alumni

Mark Yes if you want to have an Alumni List on this project. This is useful if you have cohorts of your project and want to record which people used to be involved in that project but are not involved with that project anymore.

Note: someone can be on the Alumni of one project but in a different State (e.g. on the Waiting List) of another project

Enable Declined

Mark Yes if you want to have an Declined List on this project.

  • This is useful if you do an Initial Assessment before formally accepting someone onto your project and want to be able to record that after the Initial Assessment they were not deemed to be an appropriate match for the project

Enable Events

Mark Yes if you want to create events within this project.

Which users should be allowed to create events

By default a Project Manager can create events within a project they are part of and an Organisation Admin can create events within any project.

  • But if you want other coworkers, e.g. Project Reporters or Project Analysts to be able to create events as well, add their email addresses here

Enable Cases

Mark Yes if you want to create cases within this project.

  • Cases allow your coworkers to collaborate on a specific area of work that affects a single contact.

Set conditions for cases to be closed

Mark Yes if you only want coworkers to be able to close a case once they have completed a particular survey (e.g. completed your designated ‘Case Completion Form’)

Hide the Manual Headcount fields when there are Contacts

Mark Yes if you don’t want your coworkers to see the option to include Manual Headcount (apart from when they specifically choose that option)

Default story privacy

Decide whether you want the survey responses, case notes and attendance records that are saved within this project to be visible to people who work on this project, specific individuals or your coworkers across the organisation?

Prevent project reporters from changing a story's privacy level

Mark Yes if you want to prevent Project Reporters from changing a story’s privacy from the default setting you chose above.

Quick Updates: Display tickbox formats for a single contact

This setting will be applied to Progress Boards that you invite your contacts to.

Automate following between Participating Contacts

Enable by default: Share stories with other Participating Contacts

Enable task & story timesheets

Mark Yes if you want coworkers to record the time spent on every task saved within this project and story (includes case notes, observations, survey responses etc) that they save within this project

Enable Financial Values

This feature is in beta. https://makerble.atlassian.net/wiki/spaces/MCPD/pages/837713929