When creating attribute categories, you can make those categories “attached to” an entity or record in the system. This post explains the difference between each of the “Attached To” options.
This attribute is shown on the individual details screen in the internal application, and other detail screens that are related to an individual (registration detail screen with an individual on it). It can also be seen on the website. It includes additional information about an individual, such as a job title or t-shirt size, that remains the same across multiple registrations and contexts. (Note that a t-shirt size would be best as a yearly attribute, since the size likely changes from year to year.)
This is attached to an individual and is shown in most places where an individual is. The main difference is on the registration website, where these attributes are shown on the “Attendee Selection” step. The purpose of this is to have “individual” type attributes (belongs to an individual, same across all contexts for that individual) but that is asked about the individual during registration (when the individual is actually an attendee).
Is attached to a family and is shown on the family details screen and when editing the family details on the website. These attributes are the same for everyone in the family, in whatever context they are in. An example could be a camp that splits their campers into multiple teams, with all children from the same family always being on the same team. By making it a family attribute, you set it once for the entire family.
This one is the same as family, but intended for groups instead.
This is set for every registration and is part of that registration. This means, if the individual on the registration were to change, the attributes still remain the same on that registration; they belong to it, not the individual. This can be asked during the registration process online as the “Additional Questions” step. A good example would be asking if the child is going to be arriving early for this camp session. The idea is that this information varies from registration to registration.
This is a hybrid of the “Attendee” and “Registration” attributes. These attributes are selected to be part of the registration process and shown with the “Additional Questions” workflow step. The information will be stored and populate anytime the attribute is asked of the camper during a calendar year. One of the main uses is for campers signing up for multiple events per year when the same questions will be asked for each event. Instead of a parent having to answer the question on every registration, their previous answer will populate and show to them.
This is set for an itinerary and helps provide additional information about it. It is often used with “guest groups” and other non-event groups, where details about the group contract (agreed to prices, dates they signed, etc) can be entered and kept track of as custom fields (a.k.a. attributes).
This attribute will be shown and set on the “Resource Allocation” details screen, and can be reported on with custom reports. This is information related to how a resource is being used for an event. Most often used to note which staff members will be in that cabin for an event.
It is attached to the individual whose medical information this is, and is asked in the medical form online; also available in the internal app when editing medical information.
If an individual is admitted in the Health Center, an “Incident” is created. Incidents can also be added in the internal app by going to Individual Detail > Medical > Incident, then right click and “Add”. This opens a new incident form (or you could open an existing incident) and there is a tab there for the attributes. This lets you keep track of custom information that you want to apply to each medical incident for an individual.
These questions will be filled out by a reference for a potential staff member
These attributes are shown and filled out as in sections on the application form. Their values are also shown on the staff application report(s)
*Individual, Family, Group attributes if marked as show on web will show up on the website when the user goes in to edit their details for their members and family/group.
Add the ability to track specific Attributes per Event. Examples include speaker or band that will be performing.