Answers.Body: <p>I would recommend using the CiviVolunteer extension: <a href="https://civicrm.org/extensions/civivolunteer" rel="nofollow noreferrer">https://civicrm.org/extensions/civivolunteer</a>. We have one customer that uses this extension to manage the volunteerd planning for a big event.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-05-24T10:30:26.437Z
Answers.Text: I just had a look at the documentation. Seems like a possible way, but would this mean I need to define a project for each day of the festival (10) and in each project add an opportunity for each workplace (50)? Or a project for each workplace and an opportunities in these projects for each day so the responible can assign volunteers for his/her workplace only?
Answers.UserDisplayName: Christophe Keppens
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-05-24T14:23:04.583Z
Answers.Text: Within CiviVolunteer you can use one project for the 10 event and and your role definition (opurtunities) should match what you meed. Out of the box within CiviVolunteer you can also let your volunteers signup for opporutinities. So that managers only have to check and fill empty places
Answers.UserDisplayName: Jaap Jansma - CiviCooP
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-05-24T10:02:02.563Z
Answers.LastActivityDate: 2018-05-24T10:02:02.563Z
Answers.UserDisplayName: ErikH - CiviCooP
Answers.Body: <p>Another approach (esp as you are on Drupal) would be to consider using permissioned relationships as your method of connecting entities together.</p>
  
  <p>Eg John is Manager for Backstage (an Org type contact). Jenny and Joe are volunteers via a relationship to Backstage.</p>
  
  <p>By using Fuzion's <a href="https://www.fuzion.co.nz/relationship-permissions-acls" rel="nofollow noreferrer">extension</a> you can therefore give John permission to see Jenny and Joe.</p>
  
  <p>If jenny also volunteers for Toilets, then Teddy the Toilet manager will also have access to her record.</p>
  
  <p>All of this can easily be cooked up using webforms and views so most users don't even need to go 'in' to civicrm itself.</p>
  
  <p>Get in touch if this approach sounds useful if you need more of a walk through. Good luck</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-05-24T12:09:06.403Z
Answers.Text: Hi Pete, this extension could indeed simplify the permissions. 
  So I would need to create a sub-organization for each workplace and define a relation between volunteers and this organization?
Answers.UserDisplayName: Christophe Keppens
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-05-24T20:19:52.550Z
Answers.Text: Correct. Treat your 'workplace' as a Contact which allows you to  have multi-level permissioned relationships.
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-05-24T10:32:23.897Z
Answers.LastActivityDate: 2018-05-24T10:32:23.897Z
Answers.UserDisplayName: petednz - fuzion
Body: <p>I'm taking care of the management of volunteers (about 800 people) for a 10-days music festival.
  I've been using drupal+civicrm for this for about 5 years now. There were some complaints that the way it works is not user friendly (but had to be implemented quickly). We've been looking to replace cicicrm by a commercial product but found out this product can't beat civicrm ;-)</p>
  
  <p>So now I'm looking how I can improve the civicrm setup so everybody is happy! I hope to get some tips ... </p>
  
  <p>I'll try to describe the way we are organised now and how I've set this up in civicrm.</p>
  
  <p>At the festival there are about 50 different workplaces: bars, stage, backstage, toilets, foodstands, ... Each workplace has one or more responsibles. Volunteers can work on multiple workplaces. The workplace responsible must be able to manage the data of people working for him / her only. (So not of the other people)
  Currently this is setup using groups and giving access rights on groups. Disadvantage of this is that when a responsible adds a new volunteer but forgets to assign a group (or assigns the wrong group) he cannot acces the data anymore.</p>
  
  <p>One of the most important parts is creating a planning of who will work in which place on a certain day and creating reports / lists. I've done this now using custom fields for the contacts and creating many reports using drupal views but this is a lot of manual work each year.
  I was wondering if using civievents would be more appropriate?</p>
  
  <p>Ideally each volunteer would also be able to manage his/her own data (such as address, indicate when he/she's able to work, ...) </p>
  
  <p>Any suggestions on the optimal way to implement this?</p>
  
Tags: <civievent><contacts><groups><civivolunteer>
Title: Use case: management of planning / volunteers for a music festival
ThreadText: # Use case: management of planning / volunteers for a music festival
  
  (Asked by: username_0 on 2018-05-24)
  
  I'm taking care of the management of volunteers (about 800 people) for a 10-days music festival.
  I've been using drupal+civicrm for this for about 5 years now. There were some complaints that the way it works is not user friendly (but had to be implemented quickly). We've been looking to replace cicicrm by a commercial product but found out this product can't beat civicrm ;-)
  
  So now I'm looking how I can improve the civicrm setup so everybody is happy! I hope to get some tips ...
  
  I'll try to describe the way we are organised now and how I've set this up in civicrm.
  
  At the festival there are about 50 different workplaces: bars, stage, backstage, toilets, foodstands, ... Each workplace has one or more responsibles. Volunteers can work on multiple workplaces. The workplace responsible must be able to manage the data of people working for him / her only. (So not of the other people)
  Currently this is setup using groups and giving access rights on groups. Disadvantage of this is that when a responsible adds a new volunteer but forgets to assign a group (or assigns the wrong group) he cannot acces the data anymore.
  
  One of the most important parts is creating a planning of who will work in which place on a certain day and creating reports / lists. I've done this now using custom fields for the contacts and creating many reports using drupal views but this is a lot of manual work each year.
  I was wondering if using civievents would be more appropriate?
  
  Ideally each volunteer would also be able to manage his/her own data (such as address, indicate when he/she's able to work, ...)
  
  Any suggestions on the optimal way to implement this?
  
  **Tags:** civievent, contacts, groups, civivolunteer
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2018-05-24. Score: 1
  
  I would recommend using the CiviVolunteer extension: <https://civicrm.org/extensions/civivolunteer>. We have one customer that uses this extension to manage the volunteerd planning for a big event.
  
  > **Comments:**
  > **username_0**: I just had a look at the documentation. Seems like a possible way, but would this mean I need to define a project for each day of the festival (10) and in each project add an opportunity for each workplace (50)? Or a project for each workplace and an opportunities in these projects for each day so the responible can assign volunteers for his/her workplace only?  
  > **username_2**: Within CiviVolunteer you can use one project for the 10 event and and your role definition (opurtunities) should match what you meed. Out of the box within CiviVolunteer you can also let your volunteers signup for opporutinities. So that managers only have to check and fill empty places  
  
  ---
  
  ### Answer by username_3 on 2018-05-24. Score: 0
  
  Another approach (esp as you are on Drupal) would be to consider using permissioned relationships as your method of connecting entities together.
  
  Eg John is Manager for Backstage (an Org type contact). Jenny and Joe are volunteers via a relationship to Backstage.
  
  By using username_3's [extension](https://www.username_3.co.nz/relationship-permissions-acls) you can therefore give John permission to see Jenny and Joe.
  
  If jenny also volunteers for Toilets, then Teddy the Toilet manager will also have access to her record.
  
  All of this can easily be cooked up using webforms and views so most users don't even need to go 'in' to civicrm itself.
  
  Get in touch if this approach sounds useful if you need more of a walk through. Good luck
  
  > **Comments:**
  > **username_0**: Hi Pete, this extension could indeed simplify the permissions.  So I would need to create a sub-organization for each workplace and define a relation between volunteers and this organization?  
  > **username_3**: Correct. Treat your 'workplace' as a Contact which allows you to  have multi-level permissioned relationships.  
  
  ---
  
  