Answers.Body: <p>That table is defined in templates/CRM/Event/Form/Selector.tpl and changing that would require some level of coding (your profile suggests you have this skill). Changing the Selector.tpl template directly would solve your problem but is discouraged because it causes headaches when upgrading to new versions. Creating an extension is the preferred way to make these kinds of changes, but that is much more involved. (See <a href="https://civicrm.stackexchange.com/questions/22424/how-to-customize-events-dashboard">this question</a> for more information.)</p>
  
  <p>A non-coding, quick alternative is create an Event Report with the columns that you want to view, and under that report's Access tab check "Available for Dashboard". That will allow users to add the report to their main Civi Dashboard (rather than the Events Dashboard). That won't get exactly what you want, but may help you solve the usability/workflow issue that I imagine is behind your question.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-10-29T16:58:32.960Z
Answers.Text: Thank you. I'll use the report route for the moment. I am worried about the implications you've mentioned (if I change the *.tpl file) about updates etc.
Answers.UserDisplayName: ArisK
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-10-29T17:07:55.183Z
Answers.Text: You'd just need to manually update the template file every time you run a civi upgrade. Might not be a big deal to you, but it's one more thing to juggle/document.
Answers.UserDisplayName: Phil Morice Brubaker
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-10-29T16:43:56.317Z
Answers.LastActivityDate: 2019-10-29T16:43:56.317Z
Answers.UserDisplayName: Phil Morice Brubaker
Body: <p>Hi to all (and thank you in advance),</p>
  
  <p>I'm looking to add / remove a number of columns under the "Recent Registrations" view, in CiviEvent (image attached).</p>
  
  <p>Any suggestions are welcome.</p>
  
  <p>(running CiviCRM 5.13.4)</p>
  
  <p>Kind regards
  A.
  <a href="https://i.sstatic.net/57RlU.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/57RlU.png" alt="enter image description here"></a></p>
  
Tags: <civievent><custom-fields>
Title: "Recent Registration" view under CiviEvent - Customise columns
ThreadText: # "Recent Registration" view under CiviEvent - Customise columns
  
  (Asked by: username_0 on 2019-10-28)
  
  Hi to all (and thank you in advance),
  
  I'm looking to add / remove a number of columns under the "Recent Registrations" view, in CiviEvent (image attached).
  
  Any suggestions are welcome.
  
  (running CiviCRM 5.13.4)
  
  Kind regards
  A.
  [![enter image description here](https://i.sstatic.net/57RlU.png)](https://i.sstatic.net/57RlU.png)
  
  **Tags:** civievent, custom-fields
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2019-10-29. Score: 1
  
  That table is defined in templates/CRM/Event/Form/Selector.tpl and changing that would require some level of coding (your profile suggests you have this skill). Changing the Selector.tpl template directly would solve your problem but is discouraged because it causes headaches when upgrading to new versions. Creating an extension is the preferred way to make these kinds of changes, but that is much more involved. (See [this question](https://civicrm.stackexchange.com/questions/22424/how-to-customize-events-dashboard) for more information.)
  
  A non-coding, quick alternative is create an Event Report with the columns that you want to view, and under that report's Access tab check "Available for Dashboard". That will allow users to add the report to their main Civi Dashboard (rather than the Events Dashboard). That won't get exactly what you want, but may help you solve the usability/workflow issue that I imagine is behind your question.
  
  > **Comments:**
  > **username_0**: Thank you. I'll use the report route for the moment. I am worried about the implications you've mentioned (if I change the *.tpl file) about updates etc.  
  > **username_1**: You'd just need to manually update the template file every time you run a civi upgrade. Might not be a big deal to you, but it's one more thing to juggle/document.  
  
  ---
  
  