Role based authorization
Starmind uses a role based authorization approach. A user can have multiple roles which grant access to different parts of the application/API. The roles are applied additively (that means each role defines unique rights, combining roles allows to grant the combined right to a user). Roles can be grouped into User-, Admin- and Technical- roles.
User Roles (Unprivileged)
|This is the default role for all users and does not need to be applied specifically. A user is able to create new questions, forward and solve questions and write comments. In addition, a user is able to access other user profiles and top topics within the network.
|This role allows a user to access features that are still in "Preview" state.
Admin Roles (Privileged)
|This role can manage the communication features of a network. He can create, read, delete and update announcement.
|This role can manage all the content of a network. He can create, read, delete and update questions, comments and solutions. The name of the original question poser is never disclosed to the Content Manager.
|Network Statistics Admin
|This role can download statistics data from the network.
|This role allows to read and update the network settings.
|This role allows to add, edit and deactivate users in the network. This role is usually assigned to the Helpdesk of the customer to support the users in first level support.
|User Statistics Admin
|This role can download user score statistics from the network.
Technical Roles (Privileged)
|Act On Behalf
|The on behalf user has the same rights as a regular user, but he can additionally make all actions in the name of another user. This allows him e.g. to write a solution in the name of another user.
|The api user may authenticate with the API.
|The read-only user can only read questions (including deleted questions).