User Journeys

This section contains role-based documentation for common user workflows in Image Factory.

Quick Start

Read QUICK_START.md first to identify the role-specific guide that matches your workflow.

Snapshot

Tenant dashboard:

Role Navigation Map

flowchart TD
    A[Choose Your Role] --> B[Owner]
    A --> C[Admin]
    A --> D[Member]
    A --> E[Viewer]
    B --> F[Strategy, Team, Billing]
    C --> G[Projects, Members, Configuration]
    D --> H[Builds, Logs, Artifacts]
    E --> I[Monitoring, Reporting, Audit]

Workflow Coverage

flowchart LR
    A[User Journeys] --> B[Build Creation]
    A --> C[Project Administration]
    A --> D[Team Management]
    A --> E[Monitoring And Audit]
    A --> F[Quarantine And Messaging]

Overview

Each role in Image Factory has a unique set of capabilities, workflows, and responsibilities. These documents provide detailed user journeys showing exactly what each role can do, how they work, and what their typical day looks like.

Available Roles & Documents

How to Use These Documents

For New Users

1. Start with QUICK_START.md to identify your role (5 min)
2. Read your role's journey document (15-20 min) - pick from table above
3. Follow the "Getting Started" section in your journey
4. Reference the quick actions as needed during work

For Team Leaders

1. Share this folder with new team members
2. Direct them to QUICK_START.md first
3. Share role-specific docs by assignment
4. Use success criteria to verify onboarding
5. Reference specific workflows in training

For Trainers And Team Leads

1. Use QUICK_START.md as the first handoff document
2. Share the role-specific guide that matches the person’s day-to-day work
3. Reference specific journeys during onboarding or shadowing sessions
4. Use workflow sections as a practical checklist for early adoption

Common Workflow Areas

• Build creation and execution
• Project and member management
• Notifications and operational follow-up
• Quarantine intake and review
• Reporting, audit, and oversight

What To Expect In Each Guide

Most role guides include:

• a role overview and capability summary
• getting-started steps
• common daily or weekly workflows
• detailed task walkthroughs
• pointers to related reference material

Typical User Journeys

Journey 1: Building & Execution

Who: Members, Admins, Owners
Focus: Creating and monitoring builds

Steps:

1. Create build manifest
2. Start build
3. Monitor execution
4. Download artifacts
5. Deploy/use results

Success: Build completes and artifacts are usable

Journey 2: Team Management

Who: Admins, Owners
Focus: Managing team members and access

Steps:

1. Invite team members
2. Assign roles
3. Configure permissions
4. Monitor activity
5. Make adjustments

Success: Team has right access, roles match responsibilities

Journey 3: Project Configuration

Who: Admins, Owners
Focus: Setting up projects

Steps:

1. Create project
2. Configure build methods
3. Set up integrations
4. Configure notifications
5. Create templates

Success: Project is operational and team can build

Journey 4: Monitoring & Oversight

Who: Viewers, Admins, Owners
Focus: Tracking performance and quality

Steps:

1. View analytics
2. Analyze trends
3. Identify issues
4. Generate reports
5. Make improvements

Success: Issues identified, trends understood, improvements planned

Journey 5: Troubleshooting

Who: All roles (especially Members)
Focus: Fixing failed builds

Steps:

1. Identify failure
2. Review logs
3. Find root cause
4. Fix issue
5. Verify resolution

Success: Build succeeds, root cause fixed, team informed

Permission Matrix

By Role

                Owner    Admin    Member   Viewer
────────────────────────────────────────────────────
View Projects   ████     ████     ████     ████
Create Project  ████     ░░░░     ░░░░     ░░░░
Delete Project  ████     ░░░░     ░░░░     ░░░░
View Builds     ████     ████     ████     ████
Start Build     ████     ████     ████     ░░░░
Cancel Build    ████     ████     ░░░░     ░░░░
Download Logs   ████     ████     ████     ████
View Artifacts  ████     ████     ████     ████
Download Artifact ████   ████     ████     ████
Manage Team     ████     ████     ░░░░     ░░░░
Edit Settings   ████     ████     ░░░░     ░░░░
View Analytics  ████     ████     ░░░░     ████
View Billing    ████     ░░░░     ░░░░     ░░░░

Access Levels

████ = Full Access / Can do
░░░░ = No Access / Cannot do

Quick Reference by Task

I Need to...

...start a build → Member/Admin/Owner
→ See MEMBER_JOURNEY.md - Journey 1

...manage team members → Admin/Owner
→ See OWNER_JOURNEY.md - Journey 2

...configure a project → Admin/Owner
→ See ADMIN_JOURNEY.md - Journey 3

...view analytics → Viewer/Admin/Owner
→ See VIEWER_JOURNEY.md - Journey 3

...troubleshoot a failure → All roles
→ See MEMBER_JOURNEY.md - Journey 4

...manage project integrations → Admin/Owner
→ See ADMIN_JOURNEY.md - Journey 3

...audit activity → Viewer (especially) / Owner
→ See VIEWER_JOURNEY.md - Journey 5

...generate a report → Viewer/Admin
→ See VIEWER_JOURNEY.md - Journey 3

Role Hierarchy And Dependencies

flowchart TD
    A[Tenant Owner] --> B[Project Admin]
    B --> C[Project Member]
    B --> D[Project Viewer]
    A --> E[Tenant Oversight]
    B --> F[Project Coordination]
    C --> G[Build Execution]
    D --> H[Monitoring And Reporting]

Typical Adoption Path

Most teams can onboard effectively by following this order:

1. identify the user’s role with QUICK_START.md
2. read the matching role guide
3. complete one common workflow such as build creation, project administration, or audit review
4. return to the guide as a working reference for less common tasks

Related Documentation

For more information, see:

• DOCUMENTATION_INDEX.md - All documentation
• RBAC Documentation - Role definitions
• BUILD_MANAGEMENT_GUIDE.md - Build system details

Using These Guides

Use the role guides in three common situations:

• onboarding a new user into the correct role and first workflow
• clarifying permissions or expected responsibilities across roles
• finding the right workflow reference when a task is unfamiliar

When a question is feature-specific, start from the role guide and then follow the linked reference documentation.

This section is intended as a practical map to the role and workflow guides included in the published documentation set.