> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/artifacts/at-account-level.md).

# At Account Level

### Overview

Account-level Artifacts store reusable references shared across the Account.

They support standards that should remain consistent across Organizations and Projects.

### Key Concepts

* **Account scope**: content visible based on Account-level access
* **Reusable reference**: policy, template, or standard used across Projects
* **Linking**: references from requirements, tasks, and tests back to the source

### How It’s Used

Use Account Artifacts for content that should not vary by Project.

Such as governance templates, naming conventions, and standard operating procedures.

### Benefits

* Consistent standards across Projects
* Faster onboarding through one source of truth
* Reduced duplication across Project libraries

### Setup Steps

{% stepper %}
{% step %}

### Navigate to Account-level Artifacts

1. Navigate to the Account scope.
2. Open **Artifacts** (or equivalent navigation label).
   {% endstep %}

{% step %}

### Create the Artifact

1. Select **Create artifact** (or **New artifact**).
2. Choose a source type, such as file upload or link.
3. Enter a clear title aligned to governance intent.
   {% endstep %}

{% step %}

### Organize and publish

1. Place the Artifact in a stable folder structure when available.
2. Validate access aligns to Account governance.
   {% endstep %}
   {% endstepper %}

### Best Practices

* Treat Account Artifacts as standards. Avoid frequent renaming.
* Use version labels in titles when standards change.
* Archive outdated versions instead of deleting when auditability matters.

### Summary

Account-level Artifacts provide a shared reference layer for consistent delivery across Projects.


---

# 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://help.transform.ai/artifacts/at-account-level.md?ask=<question>&goal=<user_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.