Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add initial user management documentation for end users #2745

Merged
merged 3 commits into from
Jun 2, 2018

Conversation

benjaminwil
Copy link
Contributor

@benjaminwil benjaminwil commented May 25, 2018

This adds initial documentation about Solidus's user management for end users. The audience for this documentation is store administrators or anyone who has to touch the solidus_backend as a business person.

@benjaminwil benjaminwil force-pushed the user_guides/users/initial branch from 3fb836b to 20c93c2 Compare May 25, 2018 16:40
Copy link
Member

@tvdeyen tvdeyen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A good first version. I left some comments

@@ -0,0 +1,78 @@
# Overview

Solidus includes a straightforward user management system. Users are your stores
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can remove "straightforward" here or replace it with "sophisticated". But leaving it out is most likely the best option.


You can search and sort users using a few types of information:

- **Email**: Users access your store and make orders using an identifying email
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Users sign into your store is more accurate as they can access the store without leaving an email


The following information is tracked against your users:

- **Addresses**: Customers have at least one address on file. This address can
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe explain that every time a user enters a new address we associate the address with the users account.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for drawing attention to this, I will tweak this sentence.

But I think that this is expected behavior and doesn't need to be explained.

If a customer enters a new address in their second order, then the new address "updates" the address on file that is exposed in the backend UI.

And at the moment, the backend UI doesn't expose the list of old or alternative addresses.

access denied page.

Talk to your developers about adding additional roles and the requirements that
you have for those roles.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👌 maybe explain why it is needed to involve a developer.

@benjaminwil benjaminwil force-pushed the user_guides/users/initial branch from 5a03773 to 5ca2ca2 Compare May 29, 2018 22:05
Copy link
Member

@kennyadsl kennyadsl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@kennyadsl kennyadsl merged commit f41063d into solidusio:master Jun 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants