In a multi-studio setup, an aggregator member can sometimes not be created or checked in at a second studio, often with the message "Aggregator member already exists". This is usually not a configuration error. It comes from how aggregator member profiles are shared across studios. This article explains the behaviour and what you can do.
Contents
- How aggregator profiles work across studios
- What you see
- Why it happens
- What you can do
- Special case: archived former member
- When to contact Support
How aggregator profiles work across studios
An aggregator member profile exists once per tenant. Whether another studio in the same tenant can see and use that profile depends on the cross-studio visibility of your setup. Chains differ here: some want a member to be usable across all studios, others deliberately limit access to a single studio.
What you see
When a studio tries to create or check in an aggregator member that already exists elsewhere in the tenant, you may see "Aggregator member already exists", the member is not found, or the member is not visible in the other studio.
Why it happens
Because the profile exists only once per tenant, and because visibility between studios can be limited, a second studio may neither see the existing profile nor create it again. In setups with economically independent studios, the profile effectively stays with the studio that first registered the member.
What you can do
- Decide the intended access model for your chain. Should aggregator members be usable across all your studios, or should access stay per studio? The right setup depends on that answer.
- If access should be shared, the studios need cross-studio visibility for the member. If members should stay separate, the current behaviour is expected.
- If the behaviour does not match how your chain is meant to work, contact Support so we can align the setup with your access model. This is a structural topic, not something a single studio can reconfigure on its own.
Special case: archived former member
If the member was a paying member before and is now archived, the archive can block re-creation. Reactivating the member or lifting the archive resolves this case, independently of any cross-studio question.
When to contact Support
If the access model needs to change or the behaviour is unclear, include:
- Tenant name
- The studios involved
- Aggregator member number
- What you expected to happen versus what happened