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

1

Navigate to Account-level Artifacts

1. Navigate to the Account scope.
2. Open Artifacts (or equivalent navigation label).

2

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.

3

Organize and publish

1. Place the Artifact in a stable folder structure when available.
2. Validate access aligns to Account governance.

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.