Asset Visibility in AMPLYFI

In this article:

1. Overview
2. Permission Scopes
3. Report Template Visibility
4. Custom Source Bundle Visibility
5. Common Workflows & Tips
6. FAQs

1. Overview

This guide explains how project permissions affect the visibility and usage of Report Templates and Custom Source Bundles in AMPLYFI. Understanding these rules ensures your team has access to the right templates and data sources while maintaining data security.

2. Permission Scopes

AMPLYFI supports two primary scopes for assets:

3. Report Template Visibility

3.1 Org‑wide Templates

• Use case: Standard guides you want every project to use.

  Features:

  • Can only pull data from AMP⁠LYFI and preconfigured Global bundles.

  • Outputs can be saved to any Project.

    To create:

  1. In the New Template modal, choose Org‑wide.
  2. Fill in the name, description, date range, and variables.
  3. Add sections using AMP or Global sources.
  4. Save.

3.2 Project‑scoped Templates

• Use case: Templates requiring private or project‑specific data.

  Features:

  • Can pull data from the selected project’s private assets, plus AMP⁠LYFI and Global bundles.
  • Only visible to project members and admins.

  • Irreversible: Once saved as Project‑scoped, you cannot convert back to Org‑wide. To share more broadly, duplicate the template and choose Org‑wide.

    To create/edit:

  1. In the New Template or Edit Template modal, select Project‑scoped.
  2. Choose the target project.
  3. Add or adjust sections, pulling from private project assets as needed.
  4. Save.

4. Custom Source Bundle Visibility

4.1 Org‑wide Bundles

• Use case: Shared source collections every team can leverage.

  Features:

  • Can be used in any project, template, view or generative research.

To create:

1. Navigate to Custom Sources in Settings and click Create Source Group.
2. Select Org‑wide.
3. Search & add domains
4. Save.

4.2 Project‑scoped Bundles

• Use case: Source collections that can be only used by templates and views with the same Project-scope.

  Features:

  • Only visible to project members and admins.

  • Irreversible scope: Once marked Project‑scoped, you cannot revert to Org‑wide. To share more broadly, duplicate the bundle in a new scope.

    To create/edit:

  1. Navigate to Custom Sources in Settings and click Create Source Group, select Project‑scoped.
  2. Pick the project.
  3. Search & add domains
  4. Save.

5. Common Workflows & Tips

• Duplicating for broader access: If you need an Org‑wide copy of a Project‑scoped asset, use the Duplicate button rather than attempting to change scope.
• Using project data: If you want to use Project specific data, create Project-scope source bundles and templates.
• Gen Res usage: You can use any project's data that you're a member of as a source in generative research

6. Frequently Asked Questions

Q: Can I convert a project‑scoped template back to org‑wide?

A: Yes — you can make a project-scoped template or bundle org-wide. However, this change is irreversible. Once an asset is made org-wide, it cannot be made private again.

Q: Why can’t org‑wide templates see my private project assets?

A: Org-wide assets can only reference public AMPLYFI or Global bundles. To use private assets (like Views or custom bundles), the asset must be part of the same private project or have a project-scoped context.

Q: How do I share a custom bundle with another project?

A: You can either:

• Duplicate the bundle into the target project
• Or convert it to org-wide (note: this makes it visible to the entire organisation and cannot be undone)

For further help, contact our support team at support@amplyfi.com.