S
STRIDE

Stride Glossary

A comprehensive reference of terms, concepts, and technical terminology used in Stride. This glossary covers both framework concepts and platform implementation details.

Framework Concepts

Release

A high-level delivery milestone that represents a meaningful product version or feature set. Releases provide the strategic view of what's being delivered and when.

Examples:
  • Q1 2025 Launch
  • Mobile App v2.0
  • Enterprise Features Package
Related Terms:
OutcomeMilestoneVersion

Outcome

What the user can achieve using the system. Outcomes are driven by user and business needs, and represent tangible value delivered. Functional Designers take Outcomes and create User Actions.

Examples:
  • Users can book appointments directly
  • Dashboard loads 10x faster
  • Mobile checkout is seamless
Related Terms:
User ActionReleaseUser Value

User Action

The actual things the user does in the system to achieve an Outcome. User Actions bridge the gap between business needs (Outcomes) and technical implementation (Tasks). Created by Functional Designers, they describe specific user interactions like form submissions, navigation flows, or data operations.

Examples:
  • Select available time slot
  • Enter appointment details
  • Confirm booking
  • Cancel or reschedule booking
Related Terms:
OutcomeTaskFunctional Designer

Task

Implementation work that Developers create to build User Actions into the system. Tasks are actionable, granular work items that can be assigned and completed by individual team members. When all Tasks under a User Action are complete, the User Action is complete.

Examples:
  • Design booking flow mockups
  • Build appointment API endpoints
  • Test booking flow end-to-end
Related Terms:
User ActionDeveloperWork Item

Work Item

A unified term in Stride's data model that encompasses releases, outcomes, user actions, and tasks. All four levels are stored with hierarchical relationships.

Examples:
  • Any release, outcome, user action, or task in the system
Related Terms:
ReleaseOutcomeUser ActionTask

Functional Designer

The role responsible for taking Outcomes and creating User Actions. Functional Designers bridge the gap between business requirements and technical implementation by defining exactly what users will do in the system.

Examples:
  • UX Designer creating interaction flows
  • Business Analyst defining user workflows
  • Product Designer specifying UI behaviour
Related Terms:
User ActionOutcomeDeveloper

Parent-Child Relationship

The hierarchical link between work items. Tasks belong to User Actions, User Actions belong to Outcomes, and Outcomes belong to Releases.

Examples:
  • Task → User Action → Outcome → Release
Related Terms:
HierarchyWork Structure

Status Category

A high-level grouping of work item status that indicates where work is in the lifecycle. Common categories include: Not Started, In Progress, Completed, and Blocked.

Examples:
  • In Progress
  • Completed
  • Blocked
Related Terms:
Status CodeWorkflow

Work Structure & Status

Status Code

A specific, granular status within a status category. Teams can define custom status codes to match their workflow.

Examples:
  • Backlog
  • Ready for Dev
  • In Review
  • Done
Related Terms:
Status CategoryWorkflow States

Blocked

A state indicating that work cannot progress due to a dependency, technical issue, or other impediment. Blocked items require explicit resolution before continuing.

Examples:
  • Waiting for API access
  • Blocked by another task
  • Requires design approval
Related Terms:
ImpedimentDependency

Assignment

The act of designating a specific team member as responsible for completing a work item. In Stride, tasks are typically assigned while outcomes may have multiple contributors.

Examples:
  • Assigned to: Sarah Chen
  • Owned by: Engineering Team
Related Terms:
OwnerResponsible Party

Organization

The top-level multi-tenant container in Stride. Each organization has its own users, products, releases, and work items. Organizations enable agencies and consultancies to manage multiple clients.

Examples:
  • Acme Corp
  • Client: TechStartup Inc
  • Internal Projects
Related Terms:
TenantAccountWorkspace

Product

A distinct application, service, or offering within an organization. Products contain their own set of releases, outcomes, and tasks.

Examples:
  • Mobile Banking App
  • Customer Portal
  • Admin Dashboard
Related Terms:
ProjectApplication

Membership

The relationship between a user and an organization, including their assigned role. Memberships define what users can access and do within an organization.

Examples:
  • John Doe - Admin role
  • Sarah Chen - Developer role
Related Terms:
UserRolePermission

Role

A named set of permissions that defines what actions a user can perform. Roles enable fine-grained access control within organizations.

Examples:
  • Admin
  • Product Manager
  • Developer
  • Viewer
Related Terms:
PermissionAccess Control

Permission

A specific capability or action that can be granted to a role. Permissions control what users can view, create, edit, or delete.

Examples:
  • Can create releases
  • Can edit outcomes
  • Can delete tasks
Related Terms:
RoleAccess Right

Outcome Type

A categorization of outcomes that helps teams understand the nature of the work being delivered.

Examples:
  • Feature
  • Enhancement
  • Performance
  • Technical
Related Terms:
OutcomeCategory

Platform & Organization

Comment

A discussion entry on a work item. Comments enable team collaboration, questions, updates, and decisions to be captured alongside the work.

Examples:
  • Status update
  • Question from reviewer
  • Implementation note
Related Terms:
DiscussionNoteUpdate

Estimate

A prediction of effort required to complete a task, typically measured in hours, story points, or t-shirt sizes. Estimates help with planning and capacity management.

Examples:
  • 3 hours
  • 5 story points
  • Medium
Related Terms:
EffortSizingStory Points

Metadata

Additional information attached to work items beyond the core fields. Metadata can include custom fields, tags, dates, and other tracking information.

Examples:
  • Priority: High
  • Sprint: Sprint 23
  • Due Date: 2025-03-15
Related Terms:
Custom FieldsProperties

Session Context

The current user, organization, and product scope in the Stride application. Session context determines what data is shown and what actions are available.

Examples:
  • User: john@example.com, Org: Acme Corp, Product: Mobile App
Related Terms:
User ContextScope

API Context

The organizational and product identifiers automatically attached to API requests. API context ensures data isolation in multi-tenant scenarios.

Examples:
  • orgId: abc-123, productId: xyz-789
Related Terms:
Session ContextMulti-Tenant

Entity

A database table representation in Stride's API. Each entity (like releases, outcomes, tasks) has defined CRUD operations and permissions.

Examples:
  • organizations
  • users
  • work-items
  • releases
Related Terms:
TableResource

CRUD Operations

The four basic operations for persistent storage: Create, Read, Update, and Delete. Stride's API provides RESTful CRUD endpoints for each entity.

Examples:
  • POST /releases (Create)
  • GET /outcomes (Read)
  • PATCH /tasks/123 (Update)
  • DELETE /work-items/456 (Delete)
Related Terms:
RESTAPI Operations

Filterable Fields

Attributes of an entity that can be used in query parameters to filter results. Filterable fields enable efficient data retrieval.

Examples:
  • ?status=completed
  • ?assigneeId=user-123
  • ?releaseId=release-456
Related Terms:
Query ParametersSearch

API & Data Concepts

Roadmap

A strategic view of planned releases over time. Roadmaps show the big picture of where the product is heading.

Examples:
  • Q1-Q4 2025 Release Plan
  • Feature Roadmap for Next Year
Related Terms:
ReleaseStrategic Planning

Changelog

A historical log of changes, updates, and releases. Changelogs provide transparency about what's been delivered.

Examples:
  • v2.1.0 Release Notes
  • February 2025 Updates
Related Terms:
Release NotesHistory

Multi-Tenant Architecture

A software architecture where a single instance serves multiple organizations (tenants) with complete data isolation. Each organization's data is logically separated.

Examples:
  • Agency managing 10 client organizations
  • SaaS platform with thousands of companies
Related Terms:
OrganizationData Isolation

Microsoft Entra ID

Formerly Azure Active Directory (Azure AD), Microsoft's cloud-based identity and access management service. Stride uses Entra ID for authentication and user profiles.

Examples:
  • Single sign-on
  • Company directory integration
Related Terms:
Azure ADAuthenticationSSO

Technical Implementation

Microsoft Graph

Microsoft's unified API for accessing data across Microsoft 365 services. Stride uses Graph to retrieve user profiles and photos.

Examples:
  • User profile data
  • Profile photos
  • Organization directory
Related Terms:
Microsoft Entra IDAPI

Monorepo

A repository structure where multiple related projects are stored together. Stride uses a monorepo containing api, site, native, and web folders.

Examples:
  • Single repo with API, web app, mobile app, and marketing site
Related Terms:
RepositoryCode Organization

Azure Functions

Microsoft's serverless compute platform. Stride's API is built on Azure Functions v4, providing scalable backend infrastructure.

Examples:
  • HTTP triggered functions
  • Serverless API endpoints
Related Terms:
ServerlessAPIBackend

Azurite

A local emulator for Azure Storage services. Used during development to simulate blob, queue, and table storage without cloud resources.

Examples:
  • Local development environment
  • Testing storage operations
Related Terms:
Azure StorageDevelopment Tools

Expo

A framework and platform for React Native applications. Stride's mobile app uses Expo 53 for cross-platform iOS and Android development.

Examples:
  • Native mobile development
  • EAS Build
  • Over-the-air updates
Related Terms:
React NativeMobile Development

EAS (Expo Application Services)

Cloud services for building, deploying, and updating Expo applications. Includes EAS Build for creating native binaries and EAS Update for over-the-air updates.

Examples:
  • Production iOS build
  • Over-the-air update deployment
Related Terms:
ExpoCI/CDBuild Pipeline

Learn More About Stride

Explore the framework concepts and how they work together.