bb87db8342
This PR includes documentation that preps for v2 docs (but doesn't introduce new docs). _Note: The number of file changes in the PR is due to find-and-replace within the `references` which is unavoidable. Let me know if I should move it to another PR._ ## Changes - Change Medusa version in base OAS used for v2. - Fix to docblock generator related to not catching all path parameters. - Added typedoc plugin that generates ER Diagrams, which will be used specifically for data model references in commerce modules. - Changed OAS tool to output references in `www/apps/api-reference/specs-v2` directory when the `--v2` option is used. - Added a version switcher to the API reference to switch between V1 and V2. This switcher is enabled by an environment variable, so it won't be visible/usable at the moment. - Upgraded docusaurus to v3.0.1 - Added new Vale rules to ensure correct spelling of Medusa Admin and module names. - Added new components to the `docs-ui` package that will be used in future documentation changes.
647 B
647 B
sidebar_position, description
| sidebar_position | description |
|---|---|
| 1 | Medusa Admin can be accessed more than one user. Merchants can have users added into their team to use the Medusa Admin. |
Users Overview
In this document, you’ll get an overview of features related to users and teams.
Overview
Only users who are part of the store’s team can access the Medusa Admin. You can have more than one user in a team. Each user must have an email and password to log in.
As an admin, you can manage the users’ roles and information. You can also invite or remove users.