Why not just share with them a link and let them clone it into their account?
I did this way with a client and it's perfectly fine. I was not sure if I should redo the connexion between the different variables, but it's working like a charm. No need to redo something. Just clone it and it's work.
@Oleg Isonen I didn't know this was an option. Thank you. Regardless, doesn't this tell you something about the workflow? I looked at sharing but assumed it was just a way for someone to look into my project. Where is the 'clone' button?
Similarly, and this is a separate request/suggestion but loosely connected, I'd like my client to own the project but I should still be able to work on it. Once again, the fact that we are forced to sign in with personal accounts means password sharing is out of the question so some sort of account permissions access is important for commercial workflows
and in my case we are self-hosting, so there's definitely some thought needed/disconnect in a professional/client workflow and Web Studio. I've mentioned to you before a button to control the CLI / Upload to Vercel would be very cool as a client will want to publish their changes should they make a change. I wouldn't expect them to whack open the Terminal.
I of course welcome work arounds as you're developing the tool but think this is an area where the options aren't immediatly clear to me so maybe worth considering in time
I know these are all separate issues but they are all connected to wanting a seamless client workflow stemming from the ability to 'transfer' a project. Transferring/cloning is fine from a complete website standpoint but for an ongoing relationship, it's not suitable. The UX for 'cloning' as suggested, well that's all hidden to me as the transferer so maybe a clear 'transfer project' button solves all this. I'd assume under the hood it'd use the same technology as sharing/cloning but to me it's way more explicit in what you want to do.
Hope all this helps
One last thing, I think the very quickest easiest interim solution is just to be able to create an account without using personal google/github accounts. I'm almost tempted to create a dummy google account purely for Web Studio.
@Samuel Gregory where would you expect the "transfer" button?
Is this for not having to handoff? basically using a dummy account then handing over password to that account? It's an interesting thought, as we will have other login options too.
Though this is more like account handoff vs project handoff
On the homescreen under the three dots
Yeah, just a way that we can both edit the site
You can do that now too, after handoff they would need to share a link from their account
Did you expect after handoff that project remains in your projects list as well?
How about ability to invite somone to a project and give them owner permission. This way it stays in your both accounts. If the other owner wants to kick you out out from access to the project - they will have to actively do it.
This isn't a "transfer" but an account-based sharing. So it would still be part of the Share UI.
this is a very convenient solution for client handoff !
@Oleg Isonen Sharing UI is perfect. Both have access to the project is ideal. I would like to transfer ownership so they become admin but admins in general should also be able to add users(s) as a guest(s) or editor(s) to the project so they can continue to work on the site
I'm curious about this thread. I see the GitHub issue and assume it might be a while because it's a priority 2 and high complexity.
I just tried creating an admin share link to test how this currently works. Since that link isn't account or password protected at the moment, is there a recommended way of sharing the url?
You just temp share it, once not needed delete
Sharing it securely is same thing as any message
