> ## Documentation Index
> Fetch the complete documentation index at: https://docs.internal.nscale.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Getting Access

> Prerequisites for operating or using Fleet Manager.

This page covers the access operators and general users of Fleet Manager need.
If you're setting up a local development environment, see the
[Developer Guide](../developer-guide/overview) instead.

## What You Typically Need

* **GitHub** for codebase access
* **Fleet Manager UI / API** for submitting and observing workflows
* **[1Password](./glossary#1password)** access to the relevant Fleet Manager vaults for any site you operate
* **Grafana** for logs, metrics, and dashboards
* **[Temporal](./glossary#temporal) UI** for workflow execution history
* **[Teleport](./glossary#teleport)** Used to access company infrastructure such as SSH, Kubernetes etc.
* **[NetBox](./glossary#netbox)** for inventory and [device](./glossary#node) state

Deployment engineers additionally need OpenStack, [ArgoCD](./glossary#argo-cd), and site-specific secrets.

## GitHub

* Our organisation is [nscaledev](https://github.com/nscaledev), raise a [Servicely ticket](https://nscale.servicely.ai/) to gain access.
* Ask a Fleet Manager member to be added to our fleet-manager team in GitHub

## 1Password Vaults

Fleet Manager uses deployment- and environment-scoped vaults:

* Hub vaults follow `Fleet Manager hub {environment}`
* Satellite vaults follow `Fleet Manager {deployment} {environment}`
* Satellite operator-managed secrets live in `Fleet Manager {deployment}-operators {environment}`

1Password should be used to securely store and share secrets designed to be used by humans.

* Use [this link](https://nscale.1password.com/teamjoin/invitation/OHZMLLJUHJGHZNTJ4M624YXWTQ) and your nscale.com account to sign up.
* Raise a Servicely Internal IT ticket at [nscale.servicely.ai](http://nscale.servicely.ai/) to confirm your account.
  * To gain access to vault and groups you must go directly to the owner/managers of those groups. It is not handled by Infra Support or Internal IT

## HashiCorp Vault

Deployment and runtime workflows need authenticated access to nscale's HashiCorp [Vault](./glossary#vault) at
[`https://vault.nscale.com`](https://vault.nscale.com), with `fleet-manager` KV permissions (this
is separate from 1Password above).

* Authenticate with `vault login -method=oidc` — the CLI defaults to `https://vault.nscale.com`.
* If you can't log in or lack the `fleet-manager` KV path, request it via
  [Requesting Access](#requesting-access). Cluster-level Vault resources (such as creating the
  `fleet-manager` KV-v2 mount for a new deployment) are owned by the platform/Vault team.

## NetBox

NetBox is the source of truth for inventory and device state.

* Make sure you have [Teleport](#teleport) access — NetBox is reached through Teleport [https://netbox.nscale.teleport.sh/](https://netbox.nscale.teleport.sh/).

## Requesting Access

Raise a request in the `#fleet-manager-chat` Slack channel. If you're not sure exactly
which access you need, start there rather than requesting broad access up front.

### Teleport

You can log in with your Google account via [https://nscale.teleport.sh](https://nscale.teleport.sh), but you won't be able to do that until your name is provisioned as described below.

To request access to resources, you’ll need to put in a PR to the `gcloud-iac` repo, approved by your manager and the owners of the resources


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.