You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently when users access the sign up page they can only register as Collaborators. To improve store owner engagement we want to change this page to present two routes to the users: Collaborator and Store Owner;
We could do this by just enabling the role dropdown to be used by the users, but to I'm wondering if it might be nicer to have an initial step where we present the two possibilities to users and what each of them allows them to do, see the sketch with my idea.
This adds an extra step, but it allows users to know what they are registering to do. And makes the register forms a little more simple as we don't need to check the value of the role chosen and change things based on that.
For the store owners form we need to allow the users to pick the stores they want to manage, as we already have, or in a nicer element, but we need to ensure that this connection is not active until we validate it. So we need to add a state to the user_stores table.
With this said, I'm now wondering if we really want to be validating all the store owners that might appear by us opening this up... thoughts?
List of (potential) tasks
Update register page to allow the two paths;
Move the current collaborator sign up to a separate route;
Create a new store owner sign up page with the possibility of selecting stores to manage;
Ensure that stores assigned to newly created store owners are not immediately available for them to report on, these need to be approved;
Email presence needs to be mandatory for Store Owners
The text was updated successfully, but these errors were encountered:
Currently when users access the sign up page they can only register as Collaborators. To improve store owner engagement we want to change this page to present two routes to the users: Collaborator and Store Owner;
We could do this by just enabling the role dropdown to be used by the users, but to I'm wondering if it might be nicer to have an initial step where we present the two possibilities to users and what each of them allows them to do, see the sketch with my idea.
This adds an extra step, but it allows users to know what they are registering to do. And makes the register forms a little more simple as we don't need to check the value of the role chosen and change things based on that.
For the store owners form we need to allow the users to pick the stores they want to manage, as we already have, or in a nicer element, but we need to ensure that this connection is not active until we validate it. So we need to add a state to the
user_stores
table.With this said, I'm now wondering if we really want to be validating all the store owners that might appear by us opening this up... thoughts?
List of (potential) tasks
The text was updated successfully, but these errors were encountered: