Can you have a non-personal team without the personal team?

I'm a bit late to the party and the "Enable Personal Accounts" toggle has already been added to the config (thanks Chris Oliver ). That being said I was a bit surprised that it still created an account named after the user on sign up... I expected user sign up and account creation to be completely separate at that point.

I've just gone back to the admin page and it clearly says "Disabling personal accounts will automatically create a regular account for each user instead." but I mustn't have read (or absorbed) that.

I get that it's tricky to know exactly what people are after when they uncheck that box but maybe it would be helpful to include some links to documentation on some common scenarios? Or split it into 3 options...? Something like:

• Enable Personal Accounts (default)
• Create a regular account at user sign up
• Don't create any account at user sign up

• Enable Personal Accounts (default)
• Create a regular account at user sign up
• Don't create any account at user sign up Associate user with an existing account at sign up

EDIT: I just re-read your reply Chris Oliver and my long answer basically just repeated what you suggested. Sorry!
TLDR:

1. Is there a simple way to have the new_user_registration_path create a User and an AccountRequest (based on current_account being set) rather than a User and an Account?
2. Bonus points, is there a simple way to also ask for an Account Name on sign up if current_account is not set?

How do they choose the existing account?

How do approvals work?

What extra information do you need to collect?

None in the base case... the only change is what Patrick Misch mentioned: "Allow for setting a Team/Company name on sign up"... but only if you're creating an account from the main app page.

Reading through the thread I think this would help Richard (the OP), Patrick, David, Ryan and myself (and presumably others who haven't asked).

If this doesn't make sense in the app template, I'd love some help figuring it out (perhaps a guide?).

I'm still trying to figure out:

• if I need an alternate new_user_registration_path for when a new Account is being created
• or maybe something needs to happen in Devise... do I override, or add behaviour to #create in app/controllers/users/registrations_controller.rb?
• or maybe I need to change what happens in #create_default_account in app/models/concerns/user_accounts.rb based on whether current_account is set?
• or maybe I'm barking up the wrong tree

1. Is there a simple way to have the new_user_registration_path create a User and an AccountRequest (based on current_account being set) rather than a User and an Account?

2. Bonus points, is there a simple way to also ask for an Account Name on sign up if current_account is not set?

Have a look at using current_account Borja Soler .

I found that when you visit the registration page using a subdomain, domain or with /:account_id/ in the path then current_account will be set which lets you distinguish between someone registering as a user in an an existing account or someone registering for a brand new account.

In my app/views/devise/registrations/new.html.erb file I then controlled the display of the account name field using the following:

...

    <% if !!current_account %>
      <%= f.hidden_field :link_account_id, readonly: true, value: current_account.id %>
    <% else %>
      <div class="form-group">
        <%= f.label :account_name, "Account name" %>
        <%= f.text_field :account_name, autofocus: !current_account, placeholder: "Acme Inc.", class: "form-control" %>
      </div>
    <% end %>

    <div class="form-group">
      <%= f.label :name, "Full name" %>
      <%= f.text_field :name, autofocus: !!current_account, autocomplete: "name", placeholder: "Steve Jobs", class: "form-control" %>
    </div>

...