Answers.Body: <p>You can create a custom "Participant Status" at <strong>civicrm/admin/participant_status</strong> (via the menu at <strong>Administer > CiviEvent > Participant Statuses</strong>).</p>
  
  <p><img src="https://i.sstatic.net/HWoqh.jpg" alt="Add Participant Status"></p>
  
  <p>I don't think there is a default way to expose the participant status on a core event registration form (they are typically for admins in the backend only), so you may consider using a separate workflow with a tag or group for those that are not attending, as noted by @Nicholai below. You might even be able to use Rules to automatically change their status to the new one you created based on the tag/group they are in.</p>
  
  <p>However, if you are using Drupal with Webform-CiviCRM for the registration, it would be a nice clean solution to expose this new participant status on the form (allowing "Registered" or "Not Attending" as choices), and then use Webform's Conditional functionality to show or hide event registration fields as appropriate. This way they can indicate they are not attending without having to see/fill out any custom registration fields on the form.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-22T03:55:25.720Z
Answers.Text: Wonderful! Thanks for your quick response!
Answers.UserDisplayName: Tomulent
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-22T16:33:48.130Z
Answers.Text: I've rethunk the second part of my answer and am going to revise slightly...
Answers.UserDisplayName: Laryn
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-22T03:36:32.067Z
Answers.LastActivityDate: 2015-04-22T16:41:39.323Z
Answers.LastEditDate: 2015-04-22T16:41:39.323Z
Answers.UserDisplayName: Laryn
Answers.Body: <p>Consider keeping the invitation and the registration as different concepts in your workflow, as invitees aren't really event participants if they don't attend. When you email invitees, link them to a Profile page containing options for two groups (I will attend / I will not attend). They can check the desired group, and you can track and contact them more easily. </p>
  
  <p>You could maybe even play with the CiviMail checksum links to have your options be direct links within the email, which would add the contact to the appropriate group in one click (depending on whether you use the double opt-in feature of groups).</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-22T16:33:21.480Z
Answers.Text: Yes, I had a momentary blank on this one, conflating 'participant role' with 'participant status'... Will update my answer.
Answers.UserDisplayName: Laryn
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-22T11:31:29.997Z
Answers.LastActivityDate: 2015-04-22T11:31:29.997Z
Answers.UserDisplayName: Nicholai
Answers.Body: <p>This seems an inventive workaround but would imply the user who doesn't want to attend the event still has to fill in all required fields of the registration form (most of those very specifically and only relevant for people who will attend).</p>
  
  <p>The main use case for declining an 'invitation' would be in case someone is invited with a link to the registration form and a checksum token.
  A simple button/link to inform the event host with either a maybe, a no or a registration (a yes) would definitely mature the event registration of CiviCRM! A special profile with fields for people who choose maybe/no would preferably then be selectable from the even settings page.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-11-22T11:06:32.883Z
Answers.Text: I'm working on a project currently where the client holds many events, each with specific groups of invitees. It's really important for them to be able to allow invitees to submit their apologies as unable to attend a given meeting/event. The lack of this functionality in CiviEvent feels like a real gap. Responding to an invitation with a 'No' would also stop further marketing emails for the given event from being sent.
Answers.UserDisplayName: Graham
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-22T06:25:15.497Z
Answers.LastActivityDate: 2015-04-22T06:25:15.497Z
Answers.UserDisplayName: Richard van Oosterhout
Body: <p>I've been getting complaints from my invitees that there's no way to indicate that they won't be attending. Is there someway to activate or build this option?</p>
  
Tags: <civievent>
Title: Create a "Not Attending" Option for CiviEvent
ThreadText: # Create a "Not Attending" Option for CiviEvent
  
  (Asked by: username_0 on 2015-04-22)
  
  I've been getting complaints from my invitees that there's no way to indicate that they won't be attending. Is there someway to activate or build this option?
  
  **Tags:** civievent
  
  
  ---
  
  ## 3 answers
  
  ### Answer by username_1 on 2015-04-22. Score: 2 | Accepted answer
  
  You can create a custom "Participant Status" at **civicrm/admin/participant\_status** (via the menu at **Administer > CiviEvent > Participant Statuses**).
  
  ![Add Participant Status](https://i.sstatic.net/HWoqh.jpg)
  
  I don't think there is a default way to expose the participant status on a core event registration form (they are typically for admins in the backend only), so you may consider using a separate workflow with a tag or group for those that are not attending, as noted by @username_2 below. You might even be able to use Rules to automatically change their status to the new one you created based on the tag/group they are in.
  
  However, if you are using Drupal with Webform-CiviCRM for the registration, it would be a nice clean solution to expose this new participant status on the form (allowing "Registered" or "Not Attending" as choices), and then use Webform's Conditional functionality to show or hide event registration fields as appropriate. This way they can indicate they are not attending without having to see/fill out any custom registration fields on the form.
  
  > **Comments:**
  > **username_0**: Wonderful! Thanks for your quick response!  
  > **username_1**: I've rethunk the second part of my answer and am going to revise slightly...  
  
  ---
  
  ### Answer by username_2 on 2015-04-22. Score: 2
  
  Consider keeping the invitation and the registration as different concepts in your workflow, as invitees aren't really event participants if they don't attend. When you email invitees, link them to a Profile page containing options for two groups (I will attend / I will not attend). They can check the desired group, and you can track and contact them more easily.
  
  You could maybe even play with the CiviMail checksum links to have your options be direct links within the email, which would add the contact to the appropriate group in one click (depending on whether you use the double opt-in feature of groups).
  
  > **Comments:**
  > **username_1**: Yes, I had a momentary blank on this one, conflating 'participant role' with 'participant status'... Will update my answer.  
  
  ---
  
  ### Answer by username_3 on 2015-04-22. Score: 2
  
  This seems an inventive workaround but would imply the user who doesn't want to attend the event still has to fill in all required fields of the registration form (most of those very specifically and only relevant for people who will attend).
  
  The main use case for declining an 'invitation' would be in case someone is invited with a link to the registration form and a checksum token.
  A simple button/link to inform the event host with either a maybe, a no or a registration (a yes) would definitely mature the event registration of CiviCRM! A special profile with fields for people who choose maybe/no would preferably then be selectable from the even settings page.
  
  > **Comments:**
  > **username_4**: I'm working on a project currently where the client holds many events, each with specific groups of invitees. It's really important for them to be able to allow invitees to submit their apologies as unable to attend a given meeting/event. The lack of this functionality in CiviEvent feels like a real gap. Responding to an invitation with a 'No' would also stop further marketing emails for the given event from being sent.  
  
  ---
  
  