# User Roles and Responsibilities

## Management Team (**MT**)

* Community and OSP membership management
* Regular review, endorsement & publication of roadmap for OSP development
* Certification of software platform, models and other Systems Pharmacology content qualifications and trainings
* Release of certified platform versions
* Organization of contributions to scientific and regulatory community and publication of whitepapers

## Sounding Board (**SB**)

* Review of scientific and technical content
* Identification of scientific and regulatory trends
* Scientific and technical consultancy for the management team

## Core Developers (**DEV**)

* Development and testing of OSP software platform and tools
* Review of proposed software changes
* Integration of proposed software changes into the platform

## OSP Community Members (**OSP Members**)

* Development of Systems Pharmacology content, in particular
  * data and models
  * software requirements
  * methods
  * best practices and qualification frameworks
  * training material
* Development and testing of OSP software platform and tools
* Qualification of Systems Pharmacology applications
* Validation of OSP software platform
* Experience exchange and active contributions to OSP forum

## Users

* Use of OSP content and software platform and reporting of observations, needs and issues
* Experience exchange and active contributions to OSP forum (e.g. Q\&A)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://dev.open-systems-pharmacology.org/software-engineering-transparency-and-security/overview/user-roles-and-responsibilities.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.