Adjust documenation

[jridderbusch]

Documentation Update Request

Description

General remarks

• Please update the Screenshots when the UI is finalized. The current logo is incorrect, and also the wording is not as desired.
• Make sure that the screenshot matches the users persepctive. It is confusing if you are logged in as a servicepartner admin when you have a different view of the portal than a participant while explaining e.g. the User Management from a participant admins point of view. To give an example: In https://github.com/sovity/authority-portal/blob/v2.1.2/docs/product/user-documentation/Administration%20and%20Support.md the Usermanagement is explained but the menu bar shows the item "Provided Connectors" and in your profile the servicepartner role is displayed. Please log in as a particiapant admin with no application role when you are showing features that apply to that role. A different example where this mismatch also occurs is https://github.com/sovity/authority-portal/blob/v2.1.2/docs/product/user-documentation/Connect%20to%20the%20MDS.md
• I'm missing a discription of the toggle bar used for switching the environment. Please add explainations for that (e.g. how to change the environment, which areas of the portal are affected by changing the toggle bar).
• Please use appropriate names for organizations like "Your Organziation" etc. instead of "Evil corp" and make sure your not exposing your company or companies employees. Multiple of your screenshots show your name or the names of other sovity employees. Please try to be neutral here.
• As I already mentioned in https://mobility-dataspace.online/?wpsc-section=ticket-list&ticket-id=188 I would very much prefer it if there was a clear separation between documentation that is relevant for the user and documentation that is relevant for application roles. It is not relevant for a non authority user to know how organizations are invited or rejected. Please separate this.
• I'm missing an overall description of the portal, that also describes how the portal is structured. Maybe such a description could be added to the end of "Registration in the MDS Portal".
• There is no documentation about the dashboard.

Administration and Support

• The Chapter "User Management" is not intuitivly structured for me. I would start with explaining where a user can see his role, what roles exist and roughly what they can do and then I would go into detail explaining how a participant admin can invite new users and change a users role and status.
• As already mentioned in General remarks the organization management is only relevant for authority-Roles and should therefor not be intertwined with the documentation for the customer. It should be part of a separate file.
• The same is true for the chapter "Connector Overview". This information is only relevant for authority admins, authority users and the operator.

Connect to the MDS

• You are giving a description on the on premise installation but how to request a CaaS and a short discription about the CaaS is missing. In the chapter "Connector-as-a-Service" in https://github.com/sovity/authority-portal/blob/v2.1.2/docs/product/user-documentation/Connect%20to%20the%20MDS.md you are advicing the user to go to this page https://github.com/Mobility-Data-Space/mobility-data-space/wiki/ (that btw also is about the on prem installation) while they actually could just order a CaaS through the portal. Could you please explain the CaaS-Ordering process in the portal?
• Please add a screenshot that shows the "add connector" button. You are describing this button but it does not appear in any of the screenshots on that page.

Registration in MDS Portal

• Wouldn't it make more sense to start with the organization registration and then go over the user invitation as this is the prerequisit for registering a user? From a users perspective there are two ways to get access to the portal: a) by registering his organization if the organization does not exists yet or b) by receiving an invitation from the authority.
• If the organization is already registered the user has to ask his admin to invite him -> reference to the Administration chaptwr where the invite-Process should be explained.