These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Live Event Streaming
- Features
- Organizations and venues
Organizations and venues
Define the operating team and event locations.
OverviewVenue Directory×
Live Event Streaming · Organizations and venues
New
Venue Directory
Venues
| Name | Code | Contact name | Address | Eligibility note | Organization | |
|---|---|---|---|---|---|---|
| Venue 575 | CDE-545 | Contact 810 | U-12 | EN-233 | ORG-1075 | |
| Venue 209 | CDE-379 | Contact 212 | Z-12 | EN-439 | ORG-9777 | |
| Venue 242 | CDE-432 | Contact 360 | Y-17 | EN-575 | ORG-1890 | |
| Venue 850 | CDE-172 | Contact 405 | U-3 | EN-461 | ORG-2106 | |
| Venue 478 | CDE-738 | Contact 754 | X-10 | EN-601 | ORG-1946 |
6 of 6 records
Venue 575Venues · VNS-10582
CodeCDE-545
Contact nameContact 810
AddressU-12
Eligibility noteEN-233
OrganizationORG-1075
What you can do
Set the operating scope
Organizations identify the entity that owns event work. Each has a name, code, active state, time zone and currency. Those details set context for a program before admissions begin. Team Members connect a platform User to an Organization and keep a role name, active state and time zone. The Event owner refers to one of these members, making responsibility visible on the working record.
Venues belong to an Organization and include a contact, address and eligibility note. A venue can represent a physical or virtual location or resource provider. The Event’s Counterparty reference selects the venue for that program. The venue directory lets a manager check whether a location is active and whether its note fits the planned event before it is sent for review.
How the work is organized
- Organization. The operating entity supplies time zone and currency context.
- People. team members link staff identity and membership to the entity.
- Place. Venues provide a named counterparty and contact for the event.
What to agree during setup
Decide which Organization owns each program when the business operates more than one entity. Keep codes distinct and agree who may retire a venue or membership. Confirm that an event’s owner belongs to the correct organization. Use the venue eligibility note to record a useful selection criterion; it does not replace an Event Reviewer’s decision on a specific program.
Check the handoff on an actual case
A manager is preparing an event in a venue used by several programs. Admin checks that the venue is active, its organization matches the event and its contact can handle the schedule. The Event Manager selects that venue and assigns a current Team Member as owner. The Event Reviewer can then see the organization, responsible person and venue in one record. If the venue becomes unavailable, the manager changes the event’s counterparty and sends the changed revision through review. Earlier admissions and decisions remain linked to the same Event rather than being moved into a new record without explanation.
Before using a venue for another event, confirm its active state and contact details. An older event may still reference a venue that has since become inactive; that history should remain understandable. Similarly, a Team Member who leaves the organization should not become the owner of a new event. Admin can maintain the master records while the Event Manager remains accountable for the selected event.
What your team sees
- Venue Directory — Active event locations and their organization, contact and eligibility note.
- My Team Membership — The signed-in user’s organization and membership details.
Follow the work through
See event preparation and implementation.
What it keeps track of
Data model- Organizations
- Operating organizations that own events, venues and team members.
- Team members
- Staff membership linking a platform user to an organization and role.
- Users
- Users
- Venues
- Physical or virtual venues and resource providers used by events.
- Events
- Programs, events and sessions with capacity, lifecycle and revision.
Who uses it
Permissions- Admin
- , Event Manager, Event Reviewer.
Set up Live Event Streaming your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.