Disconnect Subaccount From Snapshot Update
J
James Campbell
I would like the ability to disconnect a subaccount from the snapshot it was created with.
When pushing an update, it would essentially remove a given account from being automatically listed when pushing that update.
Sometimes it makes sense to leave an account with an old version of a snapshot. Sometimes I may want to keep an old version as an archive and not risk having it update.
Log In
S
Sales & Marketing
Merged in a post:
Ability to unlink accounts
B
Boyet Ancheta
Ability to easily link and unlink accounts to snapshots
M
Michael Riordan
whats up with this? lookss like an old request
J
Jon Aloff
Is this being worked on GHL? This is important as to not accidently override a sub account that has adjusted some process, which started in an original template snapshot
A
Aaron Rowley
We push out updates all the time & want to be able to disconnect accounts from that push.
Occasionally we also do full overhauls for individual clients off-niche that we don't want to be a part of the master system
S
Spencer Frame
Yes please, I have employee's who if they accidentally check a sub-account that no longer should be synced, would completely screw up the entire account.
J
Jodee Peevor
I would like a snapshot to also be for one asset or the assets i make it for - eg a course or a workflow so when i need to push an update i just click it :) if i want a snapshot for loads of stuff i make it that way or its just for one thing
C
Clifford Paulick
workaround:
1) create a fresh subaccount-A from snapshot-A
2) now this subaccount-A will be forever tied to that snapshot-A
3) make a new snapshot-B from subaccount-A
4) make a new subaccount-B from snapshot-B
5) delete subaccount-A
6) now snapshot-A won't have a link to subaccount-B
This, however, is only for brand new account creation, as snapshots don't allow full subaccount cloning where contacts, conversations, business settings, etc would be copied from subaccount-A to subaccount-B.