Skip to content
D
Documentation

App — Learning Path

guide
6 min readUpdated

Learning Paths › App

This learning path is for App administrators, content teams, support staff, and operations reviewers who need to organize customer-facing materials, manage operational work, configure the workspace, and monitor activity. By completing it, learners will be able to navigate core records and queues, maintain documents and screenshot coverage, configure organization-level capabilities, and use analytics and issue views to prioritize follow-up work.

Learning objectives

  • By the end of this path you can locate and review operational records and work queues in Desk.
  • By the end of this path you can organize documents and find content using document views and search.
  • By the end of this path you can review screenshot coverage and initiate recapture for records that need attention.
  • By the end of this path you can invite teammates, begin integration connections, and access enterprise capture tooling.
  • By the end of this path you can review activity, exports, and issues across relevant time ranges.

Prerequisites

  • Access to the App workspace.
  • Access to Documents, Desk, Analytics, and Issues for daily operational work.
  • Access to Organization, Settings, and Enterprise for workspace configuration and enterprise capabilities.
  • A teammate email address when practicing invitations.
  • Familiarity with the purpose of your team’s documents, support conversations, screenshots, and integrations.

Module 1: Establish the workspace for collaborative work

Goal: Set up the people, connections, and workspace areas your team needs before beginning ongoing operations.

Lesson 1.1: Invite a teammate to the organization

When a new teammate needs access, invite them from Organization. Enter their address in teammate@company.com, then select Send invite to send the organization invitation.

Practice task: In Organization, enter a teammate email address and select Send invite.

Lesson 1.2: Begin an integration connection

When your team needs to connect a source through a Git provider or webhook, open Settings. Go to Git Providers or Webhooks, choose the connection you want to start, and select Connect.

Practice task: In Settings, open either Git Providers or Webhooks and select Connect for the integration you want to begin.

Lesson 1.3: Access the Captured Flows recorder

When you need to capture a workflow for documentation or review, open Enterprise, select Captured Flows, and choose Get recorder to access the recorder.

Practice task: From Enterprise, open Captured Flows and select Get recorder.

Lesson 1.4: Explore branding areas for a branded workspace

When you need to identify where branding changes are managed, open Branding. Review the available areas: Atloria Web, Site Info, Media, Colors, Top Menu, Typography, White-label, and Domain.

Practice task: In Branding, open one branding area relevant to your team, such as Colors or Domain.

Module 2: Maintain content and capture coverage

Goal: Keep documentation organized and ensure screenshot records are current enough to support reliable content.

Lesson 2.1: Create a document category for organized content

When related documents need a shared organizational home, open Documents and select Add Category. Use the category creation flow to add the category before placing related content under it.

Practice task: In Documents, select Add Category and create a category for a content group you manage.

Lesson 2.2: Find the right document for review

When you need a specific document, first choose the most useful view in Documents: All, Draft, Published, Archived, or Recently Updated. If the view does not narrow the list sufficiently, use Search... to locate the document directly.

Practice task: In Documents, use Recently Updated or Search... to locate a document to review.

Lesson 2.3: Review screenshot coverage by capture condition

When checking whether documentation has usable visual evidence, open Enterprise, then Screenshots. Review records through All0, Fresh0, Carried0, Stale0, and Missing0 to understand their capture condition.

Practice task: In Screenshots, compare the Fresh0 view with either Stale0 or Missing0.

Lesson 2.4: Recapture a screenshot that needs attention

When a screenshot is no longer current or is absent, go to Screenshots. Open Stale0 or Missing0, identify the screenshot record that requires action, and select Recapture.

Practice task: In Screenshots, open Stale0 or Missing0 and select Recapture for a needed screenshot.

Module 3: Work support and operational records

Goal: Find individual records quickly and use status queues to prioritize support follow-up.

Lesson 3.1: Find and review a Desk record

When you need to investigate a specific support record, open Desk and use the search field to find it. Select the relevant record row to review it; when finished, use the browser Back control to return to the prior Desk context.

Practice task: In Desk, use the search field, open a record row, and return using the browser Back control.

Lesson 3.2: Prioritize Desk work by response status

When deciding what to handle next, use the status queues in Desk. Start with Needs first response 0 for conversations awaiting an initial reply, then review Needs next response 0, Investigating 0, Waiting for customer 0, and Paused for later 0. Use Done today 0, Triage 0, and Your threads 0 to review completed, untriaged, and personally assigned work.

Practice task: In Desk, open Needs first response 0, then compare it with Your threads 0.

Lesson 3.3: Handle an email follow-up from Support Agent

When a Support Agent email needs attention, open Support Agent. Use Resend email when the email must be sent again, or select Dismiss when no action is needed. Use Menu when you need the available additional options.

Practice task: In Support Agent, review an email follow-up and choose either Resend email or Dismiss.

When an email-related item appears during configuration work, use the available action on Settings: select Resend email to send it again or Dismiss to clear the item. Apply the same decision when handling an integration email message in Integrations.

Practice task: Review an email-related item in either Settings or Integrations and select the appropriate action: Resend email or Dismiss.

Module 4: Monitor activity and identify follow-up work

Goal: Use time-based reporting, exports, and issue views to review performance and focus attention where it is needed.

Lesson 4.1: Review Analytics activity for the right time horizon

When reviewing recent or historical activity, open Analytics. Choose 7d, 30d, 90d, or 1y based on the period you need to assess. Use Dashboard for a broad activity view, Audit Trail for activity history, and Needs Attention to focus on items requiring review.

Practice task: In Analytics, select 30d and then open Needs Attention.

Lesson 4.2: Open Analytics exports

When you need to work with available reporting exports, open Analytics and select Export Center. Review the export area before choosing the reporting artifact relevant to your follow-up work.

Practice task: In Analytics, open Export Center.

Lesson 4.3: Review issues over an appropriate period

When investigating trends or recent problem reports, open Issues. Select 7d for a recent review, 30d for a monthly view, or 90d for a broader trend review.

Practice task: In Issues, review issues for 7d, then switch to 90d and compare the scope.

Final assessment

  1. A support lead wants to contact conversations that have not yet received an initial reply before reviewing their own assigned threads. Which Desk views should they use, and in what order?

  2. A content reviewer finds that a screenshot is outdated. Which screen and capture-condition view should they use, and what action should they take?

  3. An administrator needs to connect a new webhook-based service. Where should they begin, and which control starts the connection?

  4. A manager wants to inspect activity from the past month and concentrate on items that require review. Which Analytics controls should they select?

  5. A team member needs a document that was recently changed but does not know its title. Which document view should they try first, and what should they use if they still cannot locate it?

Answers

  1. Open Desk, review Needs first response 0 first, then review Your threads 0.
    Why: The first queue identifies conversations awaiting an initial response, while the second focuses on the user’s own threads.

  2. Open Screenshots, select Stale0, and choose Recapture.
    Why: Stale0 identifies outdated captures, and Recapture starts the needed refresh.

  3. Open Settings, go to Webhooks, and select Connect.
    Why: Webhook connections are started from the Settings integration area using Connect.

  4. In Analytics, select 30d and then Needs Attention.
    Why: 30d sets the monthly period, and Needs Attention narrows the review to follow-up items.

  5. In Documents, select Recently Updated; if needed, use Search....
    Why: The recent-update view is the best first filter, while search helps locate a document when its exact location is unknown.

Was this page helpful?