Pulling Collaborators from the Org Library and Pushing Changes Back

Your organization's Collaborator Database, the org library, holds the venues, vendors and partners you work with again and again. Instead of retyping a known vendor onto every event, pull it from the library. Whatever you learn about it on the event, such as a new contact or a corrected phone number, can be pushed back so the next event starts from current information.

Adding from the library needs event admin and Collaborator Database Read in the organization. Pull from org and Push to org are offered to organization members with Settings on the collaborator; pulling needs Collaborator Database Read, and pushing needs Collaborator Database Edit.

Pull Collaborators onto an Event

Each pulled collaborator brings its crew, who arrive as contacts with no access. People already on the event under another collaborator stay where they are. Invite them when they need to log in. If one company cannot be added, the others still are.

Types and values come down only where the event already has a linked copy of the library's types and properties. So copy the types you need first, from Event Settings > Collaborators with Add from org library (see collaborator types and properties). A library value whose property has no copy on the event is skipped, and you can assign more types afterwards from the collaborator's details panel.

Refresh from the Library

When the library record has changed, open the event collaborator and select Pull from org. The library wins: the name, linked property values and linked crew contact details on the event are overwritten, and library types are assigned where the event already has a linked copy of the type. Event-only properties, crew and types are not touched.

Push Changes to the Library

On the event collaborator, select Push to org. The library record's name and linked property values are overwritten with the event version, and linked types it lacks are added; no types are removed. The collaborator's crew are saved to the organization crew database with their contact details only. To carry a person's types and values too, push them from their crew record. Colleagues on other events read that record, so check the changes first.

For a collaborator created on the event, the button reads Save to org library and adds it to the library as a new record, linked from then on.

Before a pull or push runs, a confirmation lists the name and property values that will be overwritten, with old and new values, summarizes the crew changes, and names the event-only fields that will not sync.

flowchart LR
    L["Org library record"] -->|"From org library"| E["Event collaborator"]
    L -->|"Pull from org (library wins)"| E
    E -->|"Push to org / Save to org library"| L

What Travels and What Does Not

Only types and properties linked to the organization travel. Event-only ones stay on the event. A collaborator's advances, tasks and files stay on the event as well.

Collaborator types and property values do not travel inside event templates: a template carries a collaborator's name and department only.