Introduction to the Scenario (Resource) Catalog

The Scenario (Resource) Catalog feature enables authorized users to create catalogs containing AR scenarios, which can be easily shared via automatically generated URLs or QR codes. Individual scenarios can also be shared in a similar manner. This content is accessible through the WorkLink app or web viewer (only scenarios published using Create version 2.39 or newer are supported in web viewer) and can either be public or private, depending on how the scenario or catalog is configured. A catalog serves as a repository of Work Instructions for AR content, helping organizations manage and distribute resources efficiently.

Users can share these scenarios and/or catalogs by text, email, or embedding the links within other applications. This feature offers flexibility, allowing businesses to securely share important AR content with internal teams or publicly distribute product information for marketing and troubleshooting.

Public Scenario/Catalog: Share AR Content Widely

The Public Scenario/Catalog feature allows companies to share AR content with anyone who has access to the URL or QR code, without the need for a WorkLink account. This is similar to sharing documents on Google Drive. Public scenarios/catalogs are an ideal solution for businesses wanting to provide open access to AR content for demonstrations, troubleshooting, or marketing purposes.

Benefits of Public Scenarios/Catalogs:

• Access to a Wide Audience: Anyone with the scenario/catalog link or QR code can access the AR content, making it ideal for marketing materials or product demos.
• No WorkLink Account Required: Users can open the catalog and view its content without needing a licensed account, making it easy to share content externally.

Use Cases for Public Catalogs:

1. Marketing and Sales: Share links or QR codes on websites or in marketing material to allow customers to access product demonstrations.
2. Customer Support: Provide customers with AR content to help them troubleshoot issues with your product.

FAQs About Public Scenarios/Catalogs:

• What happens if someone opens a Public Scenario/Catalog without a WorkLink account?
  The scenario/catalog opens normally, with no need to log in or provide personal information. If WorkLink is not installed, users will be prompted to download the app from the App Store.
• What functionality is available to non-WorkLink users?
  Users can interact with the AR content in the scenario/catalog as though they have a WorkLink account. However, they won’t be able to place calls, access the contacts list, or change any WorkLink settings.
• How do I share the scenario/catalog?
  You can download the QR code or copy the access link from the catalog list and share it through any media. Users can scan the QR code directly using their device’s native camera app. Additionally, individual scenarios that have been made public can be embedded in a website.

Private Scenario/Catalog: Secure Content for Internal Use

In contrast to public catalogs, Private Scenarios/Catalogs are restricted to licensed users within your organization. These scenarios/catalogs are designed to securely distribute AR content to team members, ensuring that only authorized personnel can access sensitive material. Private scenarios/catalogs work similarly to restricted Google Drive documents, where only individuals with permission can view the content.

This feature ensures that AR content is securely distributed within the company and cannot be accessed by unauthorized users.  

Managing and Sharing Catalogs

Once a catalog is created, whether public or private, it can be easily managed and shared through the CMS. Users can:

• Download the QR code generated for each catalog to share with others.
• Copy and paste the Access Link from the catalog list into emails, websites, or other forms of communication.

For public scenarios/catalogs, this allows businesses to widely distribute AR content for marketing or customer support purposes. For private scenarios/catalogs, the content can be securely shared with internal users who have the necessary permissions.