Restrictions on Access to Event Information
Some way for an event maintainer to indicate to whom an event is open, pertains mostly to, or is visible to.
Use cases:
- Scott Grocott, Selwyn Bar Manager, only wants to advertise bar events to members of Selwyn.
- Newnham JCR are holding a combined bop for Newnham, Selwyn and Robinson students.
- Deloitte are holding a career event at Newnham - it's open to all students, but is particularly relevant to Newnham students.
- The Careers Service only wants to advertise career events to members of the University, and wants to indicate specific restrictions for attendance to certain events.
- A member of the public [non-university] wishes to know what they can attend in our listings.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Medium
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Discussion
- Series goal:
- Accepted for 3.0
- Implementation:
-
Not started
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
I suspect that decisions here will interact with other decisions about user interaction workflow with Pidge - for example whether we let users view data before registering.
