> For the complete documentation index, see [llms.txt](https://opsmanual.studentrobotics.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://opsmanual.studentrobotics.org/master/internal-structure/infrastructure-team.md).

# Infrastructure team

## Purpose

The Infrastructure Team is responsible for providing and maintaining the computing infrastructure required for the other teams to operate.

This includes, but is not limited to:

* Setting up and maintaining servers to support SR operations including the deployment of the public facing web site
* Setting up and maintaining the organisation's domains (studentrobotics.org and srobo.org)
* Maintaining the security of the infrastructure and related services
* Setting up and maintaining the structure of GitHub organisations and permissions
* Setting up and maintaining G-Suite accounts for SR volunteers, teams and committees
* Providing support and guidance with regards to best-practices to other teams or volunteers on infrastructure and services where possible
* Maintaining a list of core services (i.e. services central to Student Robotics operation)
* Maintaining a list of team services (i.e. services maintained especially for and in collaboration with another team)
* Ensuring continuous/enduring access to SR services

The infrastructure team is **not** responsible for content beyond ensuring it does not break other functionality

[The way that the team is structured and operates](/master/internal-structure/team-operations.md) is consistent with all of the other SR teams.


---

# 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 dynamically by asking a question.

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

```
GET https://opsmanual.studentrobotics.org/master/internal-structure/infrastructure-team.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
