The Teams layer needs some configuration to avoid error and delay. Lets check what these are.
Steps needed are;
1. An Event has the Hirer for that event set on the Workflow page.
3. Set the Hires allocation for any Event using the Master Hirer Account.
This enables allocation Per Event.
You need to use the single Hirer account here - We suggest naming like this"Hirer - Portal"
This links the asset for the event to the Hirer for the event and enables per-event sharing. There is no need to use multiple accounts. One account is set to share all assets with the Hirer.
Here is an example of sharing Sydney FC portal accounts to Sydney FC's own grid view.
if set up like the above Sydney FC will receive only the assets allocated to them per event. They are then able to share assets with their customer base in the same way you do.
It also enables assets to be shared as barcodes where they are the hirer but as tickets where they are not the Hirer but still share tickets where they
The naming {team name} = "portal" is only a suggestion so you use the correct linked account.. often there are many team accounts.
The critical setting is that the account here is linked as the connected Team account. This indicates that the Team should only receive barcodes and Not-built tickets. This Portal account is then linked to the master hirer account.
There is no impact on barcoding when allocating to teams or 'Hirers'. You will notice that ticketing fo is disabled when a hirer owns those assets.
Where the yellow ticket build is disabled - leave this step to the hirer. (as set on workflow)
Is the ROOM shared as a full asset or as a seat? This is dependent on how the room is distributed.
For example - if the owner of the asset is not selling the asset it's likely the room is shared as a FULL ASSET. If the Room is "for sale" - each seat is likely "on-Sale" and therefore needs to be set by Seat, so that individual seats can be "owned"
if this is confusing please let us help via our support channels.
