New customer organization
Create the account and issue its owner invitation. Two people are required: you request it here, an independent approver decides it, and only then can it be committed.
Note: Two people are required to complete this
You request the change here; an independent staff approver decides it on the Approvals screen; only then can it be committed. The server refuses a commit with no approval, and refuses an approval whose approver is the requester - so you cannot finish this on your own, and there is no approve control on this screen.
Creating a customer organization is one of the three staff operations that administer a customer account from outside it. It needs staff.customers.organizations.create at platform scope - a grant limited to named organizations cannot create new ones, because there is no organization yet to scope the decision to.
Note: What creating this does, and what it does not do
- The organization is created with no members at all. You do not become its owner, and no staff identity does - the server refuses to give the staff actor a membership of a customer organization, which is what keeps staff authority and customer membership from becoming one privilege set.
- Its owner is the person you name below. They get an invitation, and the organization has no active owner and is unusable by the customer until they accept it.
- If no LandmanIQ identity exists for that address, none is created now. The invitation is the route by which one comes to exist, and the invitee must complete signup first.
- Nothing is purchased. No package, seat or subscription is attached by this operation.