AlumnIQ Admin Documentation
  • README
  • Common Features
    • Identity
    • Xid
    • Google Analytics Tracking
  • Content Management
    • Editing Pages
  • Profiles and Directory
    • Public Resources
      • Account Creation
      • Updating a Profile
      • Using the Directory
    • Administrative Resources
      • Profile Customization
      • Maintenance
      • Capturing Changes
      • Directory Permissions and Inclusion
  • Events Module
    • Event Setup
      • Event Skinning
    • Activity Setup
    • Fees
    • Webinars
    • Products
    • Fair Market Value (FMV)
    • Location Management
    • Access Control
    • Remote Check In [V5]
    • Wingman
    • Customer Service
    • Printing Name Tags
    • Express Registration
    • Reporting
    • Including Warehouse Data
    • Post-Event Survey
    • Post-Event Tasks
      • Matching
  • Image Library
    • Recent Uploads
    • Edit Image
    • Search Images
    • Uploads
  • Email and Lists
    • List Management
    • Delivery Workflow
    • Unsubscribes
    • Exclusions
    • Automated Messages
    • Bounce Handling
    • Spam Complaints
    • Resubscribes
  • Membership
    • Customer Service
  • Volunteer
    • Data Feeds
  • Online Giving
    • Giving Form
    • Global Configuration
    • Donor Cover
    • Setup Paths & Pitches
    • Sending targeted emails
    • Ask Arrays
    • Customer Service & Reporting
    • Tax Receipts
    • Suspended Pledges
    • Payment Processing
    • Give Now
    • Refunds
  • Crowdfunding
    • Introduction
    • Media Recommendations
    • Scheduled Page Updates
    • Challenges
  • Salesforce
    • Installation
    • Integration
    • Security
  • Security
    • Salesforce
    • Shared User Accounts
    • API Keys
    • S3 Keys
  • Data Sync
    • API Basics
    • Sending us your data
    • Getting data out of AlumnIQ (API)
    • API: Financial Data
    • Object Model/ER Diagrams
    • Salesforce
  • Integration Recipes
    • Everyday Events
    • Warehouse Loads
    • Salesforce
  • Compliance
  • Customer Guides
    • Auburn Specific Instructions
    • WWU Specific Instructions
  • Signature Events Service
    • Onboarding and Setup Timeline
    • Integration
    • Payments and Gateways
    • Warehouse Structure and Projection
    • Graphic Specs
    • Giving
    • Where to update what
    • Planning to Attend
    • Bio Update
    • General Configuration
    • Who's Coming List(s)
    • Package Controls
    • Access Controls
    • Strings
    • Health+Safety/Vaccination Attestation
    • Table/Seat Assignment
    • Getting events from contributors across campus
    • Virtual Events and Webinars
    • Staff Assistant
    • Common Scenarios
    • General Registration Management
    • Text and Email Messaging
    • The Pass
    • Watches
    • Housing
    • Post-Event Survey
    • Name Tags and Printing
    • Options for Check In
    • Batch Printing
    • Offloading Clicker Data
    • Event Attendance with Gatekeeper
    • iqKey for fast Gatekeeper access
    • Email Senders
    • Newsletter Archive
Powered by GitBook
On this page
  • The Process
  • Setup
  • The Hierarchy / The Dictionary
  • General Configuration
  • You're impatient - here's your quick proof of concept.
  • Now for the more fun stuff
  • Public Side
  • Access Control
  • Who can be a colleague?
  • Impersonation
  1. Signature Events Service

Staff Assistant

Last updated 8 February 2020

You can't run a big event without staff to help you. Traditionally, this is done with a spreadsheet passed down through generations and a whole lot of email.

AlumnIQ has a better way.

The Process

  1. You set up the 'events' you need help with. These may be events that already exist in the registration system, but also generally include stuff like 'staff for the registration area' and 'greeters at the satellite parking lot'.

  2. Then you set a switch to enable selection

  3. Then you send an all-staff email to invite your colleagues in.

  4. They select the shifts they're willing to work. This, as you know, may take some...encouragement.

  5. After you've had enough of that, you'll set that switch to disable selection.

  6. Then you'll assign staff members to shifts. See, what they've been doing is indicating interest - but you have the final say-so over who works what/when.

  7. Then you'll set a switch to enable viewing.

  8. Your beloved colleagues will then return to the system to see where you expect them to be.

  9. {time passes}

  10. 20 minutes before each shift, we'll send a text reminder to the affected staff reminding them to show up.

At pretty much any point along the way you can pull reports to see how covered you are for each shift, who's volunteered, and adjust the config as needed.

Setup

The Hierarchy / The Dictionary

A Master Event has one or more Events An Event has one or more Jobs A Job has one or more Shifts

What your Colleagues are signing up for are Shifts -- which tells us the job and event they'll be working.

You'll be setting up events, jobs, and shifts. This allows you to maximize clarity and flexibility for scheduling as needed.

The system will also automatically block your colleagues from selecting concurrent shifts. Double booking is in nobody's best interest.

General Configuration

  • is open to selection - colleagues can opt in to and out of shifts

  • is open to view - colleagues can see the shifts you've confirmed them to work

  • hard cap - if you say you need 2 people for a shift, should we allow only 2 people (hard cap) or allow oversubscription 18 people (so you can pick and choose)

You're impatient - here's your quick proof of concept.

  1. Create an event.

  2. Create a job.

  3. Create a shift.

  4. Hop on over to the public side (/staff) in another tab.

  5. Request a login using your email address.

  6. Click the link in the email.

  7. Observe the one shift you have to select from. Add it to your stash.

Now for the more fun stuff

On the admin side, you'll have a top level view of how well you're filling your slots all the time:

Public Side

And once selected, they have options to print or export their selections to their Outlook or Google calendar. The little group icon? A way for them to see who else is working that shift, since community is important even when working.

Access Control

Colleagues can access the selection side of the system via a fairly simple magic link-based process.

  1. Colleague visits the login screen (/staff)

  2. Colleague inputs their email address

  3. Colleague recieves email (if they're a valid user)

  4. Colleague clicks magic link in email

The magic link is good for 7 days.

Who can be a colleague?

AlumnIQ can be configured to auto-create profiles based on a domain whitelist. For example, any individual requesting access from an @valpo.edu email address would be permitted to log in but @gmail.com would not. This is much, much easier than having you provision everybody before you let them in (though that reamins an option).

You can always create profiles for individuals outside the whitelist if you need them. Use the Colleague Add/Edit link in the admin to create them.

If you'd like to alter your whitelist, pop the request in a ticket.

Impersonation

Who doesn't want to become someone else every now and then? You can impersonate any of your colleagues as/when needed to revise their selections or simply 'see what they see' to address a question.

PreviousVirtual Events and WebinarsNextCommon Scenarios

Last updated 4 years ago

Your colleagues will enjoy a friendly, approachable interface for shift selection. The site they go to to sign up is

https://{YOUR_ALUMNIQ_SUBDOMAIN}.events.alumniq.com/staff
staff overview of event config
staff overview of signups
staff selection UX
staff selection UX