> For the complete documentation index, see [llms.txt](https://docs.violetlabs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.violetlabs.com/features/requirements/systems.md). # Systems Violet **Systems** allow you to define the architecture of your product. This architecture can be used to organize and allocate permissions to Violet objects (like [requirements](/features/requirements/structure.md) or schedules) based on the systems they belong to. For example, Systems elements can be used to establish user permissions and to filter, sort and visualize Violet Requirements. For example, a Spacecraft System may be composed of the following systems: * Space Vehicle * Payload * Bus * Structure * Power * Thermal * ADCNS * GNC * C\&DH Systems are defined in the [Programs](/features/programs.md) configuration pane. User groups or individual users assigned to systems will be able to edit requirements associated with the system; these users are designated requirement owners. Click the **+Add** button to create a new system, then drag and drop it into the appropriate order and hierarchy level to align with your architecture. Add owners and optionally assign a color code for the system.
### Using systems to define user access When a user is added to a system, Violet will grant them write-access to requirements in that system as well as all lower-level systems contained within it. You can opt to remove lower level "inherited" access if you wish (for example, granting an engineer write permissions to a system, but not to all nested subsystems). You will also have the option to list any user within a program as an approver to a requirement. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.violetlabs.com/features/requirements/systems.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.