> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/data-library/asset-register/how-it-works.md).

# How it Works

The Asset Register compiles all assets—both auto-discovered and manually added—into a single dashboard, allowing teams to manage asset-based compliance efficiently.

Here’s how it works:

***

### Step 1: Assets are auto-discovered from integrations

Once you connect your cloud providers (e.g. AWS, Azure), code repositories (e.g. GitHub, GitLab), or HRMS tools (e.g. Rippling), Sprinto automatically discovers your organisation’s digital infrastructure and people.

The following tabs get populated based on integration data:

* **Infrastructure**: EC2s, buckets, containers, and other resources
* **Staff Devices**: Employee laptops and machines
* **Code Repos**: Project repositories hosted on Git platforms
* **People**: Staff directory synced from HRMS or IDP

Each asset comes tagged with metadata like classification (Production/In Scope), owner, and added date.

***

### Step 2: Add assets that are not auto-discovered

Some assets—such as backup generators, CCTV systems, or legacy servers—can’t be automatically pulled via integrations.

You can add them manually from the **Custom assets** tab using either of these options:

* **Individually**: Fill out a simple form with fields like asset ID, name, owner, classification, and group.
* **Bulk upload**: Download the CSV template, fill it with asset details, and upload to import multiple records at once.

***

### Step 3: Classify assets and assign ownership

Whether discovered or added manually, each asset can be:

* **Classified** as *In Scope* or *Out of Scope*
* **Grouped** into categories for reporting
* **Assigned** to an owner for accountability

These actions ensure that only relevant assets are monitored, and the right people are responsible for evidence submissions.

***

### Step 4: Use assets across compliance modules

Once assets are in place, Sprinto links them to compliance modules like:

* **Monitoring checks**
* **Workflow evidence**
* **Risk assessments**

This makes it easy to meet auditor requirements, assign reviews, and respond to incidents with asset-level traceability.


---

# 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://docs.sprinto.com/data-library/asset-register/how-it-works.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.