@chris thanks for explaining the technical limitations to automated account creation. However, I don’t think that is a prerequisite to making it easy for people to sign up.
I think there are a couple options to allowing individuals to sign up, pay, and use Meet.coop infrastructure:
Option 1
What @chris proposes, to distribute the manual account creation and maintenance to member orgs. People arriving to Meet.coop are greeted with a form like what @decentral1se referenced in https://forum.meet.coop/t/governance-model/128/12?u=benhylau they make a subscription on OC or Stripe, and wait for an email with account details within some time frame we commit to.
Option 2
We host an “official” Meet.coop instance, and allow people to subscribe via an “official” OC hosted at open-coop, and wait for an email with account details within some time frame we commit to.
I think both these are possible. I can see how some of us may favour 1 for scalability, and 2 for usability. This is where we need a way to make decisions together.
@osb do you think both the above options, with proper marketing copy on the website, can address your concerns here?
@chris on the technical side, I want to clarify the steps to account creation. My understanding is:
-
All the Greenlight containers share the same BBB backend server
-
Sysadmin manually verify payment
-
Sysadmin manually login into the correct Greenlight container
-
If it’s a admin account run
rake admin:create[name,email,password,role]
If it’s a user account runrake user:create[name,email,password,role,provider] -
Sysadmin send email to new customer with access information
Does that sound correct? Is the user account the same thing as when I sign up using https://demo.meet.coop/b/signup?
I understand that the commands for listing accounts, updating accounts and removing accounts are missing, but how do you see those relevant in signup/onboard flow?
Do you think 1-4 can be automated via a Stripe (not familiar with OC API) webhook triggered execution of these steps?