Organization

Before you start

Open the Client Admin area while signed in with Client Admin access. Confirm that you are working in the intended organization before changing membership or the organization tree.

• Organization units and regions are separate trees with separate assignment and reporting uses.
• Use recognizable names and avoid putting sensitive information in names, codes, or user notes.
• If a source is unavailable, stop before making a membership decision; a blank list is not confirmation that nothing exists.
• Organizations can nest sub-organizations several levels deep. Expand a row in the organization tree to see its sub-organizations, or use Expand all to open the whole tree at once.
• Retired organizations are hidden from the tree by default; use the Inactive filter to bring them back into view.
• When adding or moving a sub-organization, choose its place in the tree level by level: start with the top-level organization, then choose the specific organization it nests under.

Use the setup checklist

A new Admin lands on a persistent setup checklist that tracks four steps: Organization hierarchy, Regions and sub-orgs, Review roles, and First-wave managers. It is a guide, not a gate: the rest of the Admin portal stays available throughout setup, and you can return to the checklist at any time to see what is left.

• Organization hierarchy and Regions and sub-orgs are complete once at least one org unit or region is configured.
• Review roles is complete once you have acknowledged the role and capability review on the Roles page.
• First-wave managers is complete once at least one active manager is assigned to an org unit or region.

Read the organization tree

Choose Orgs or Regions to switch dimensions. Organization units can nest several levels deep; regions remain a separate hierarchy used for regional assignment and reporting.

• The Active filter is on by default, so inactive or retired rows stay out of the working view.
• Expand a row to see its children, or use Expand all and Collapse all when you need to inspect the whole tree.
• Use the Inactive filter when you need to review a retired row; hiding it does not delete it.

1. Open Organization and choose Orgs or Regions.
2. Use Expand all, Collapse all, or a row's expand control to inspect the hierarchy.
3. Turn on Inactive when you need to review rows that are not active.

Create or update a unit or region

Use Add New Organization or Add New Region for a new row. Edit an existing row when its name, code, active state, parent, or optional home-region description needs to change. A user’s own region assignment is what drives reporting; a unit’s optional home-region field is descriptive.

• Archive hides a unit or region from new assignment and can be reversed with Active. Before permanent deletion, Stride checks current assignments. Archive to preserve assignments and history.

1. Choose the dimension, then select Add New Organization, Add New Region, or an existing row.
2. Enter a clear name and optional code. For an organization unit, choose whether it is a parent org or select its parent level by level.
3. Choose Active when the row should remain available for assignment; leave it off to hide the row from new assignment.
4. Select Create org or Save changes and wait for the tree to reload with the saved row visible.

Review role groups

Use the Roles page to review and rename the role groups that drive challenge and quest targeting. The built-in system roles come from the survey's role question; add a custom role group for a role the survey does not cover.

• The write-in queue collects a member's own typed-in answer whenever they choose Other on the survey's role question; triage each one into the correct role group.

Invite and manage users

Use Users to review the organization roster, invite a participant, add a user directly, assign a Manager, and assign an organization unit or region. Follow your organization's joiner and leaver process when access changes.

• Invitation statuses are pending, sent, accepted, and revoked. Stride also shows Expired as a computed label on a pending or sent invitation once its link has timed out.
• A deactivated account does not receive new access until your organization's process restores it.
• Use a work address when your organization requires one, and do not put sensitive details in a user note.
• A name is cleaned of invisible and directional-control characters before it is saved. If a name is rejected as empty, it likely contained only such characters; re-enter it with visible letters.

1. Open Users and use Search name or email or the role, team, pending, unit, and unassigned filters to find the intended person.
2. Choose Send Invite Link for a new invitation, or Add User when you are entering an account directly.
3. Check the recipient and choose the appropriate access, Manager, organization unit, and region values before saving.
4. Confirm the invitation or roster readback before telling the person that access is ready.
5. For many people at once, choose Bulk Import and upload a CSV of up to 1,000 rows. Importing only stages a pending invitation for each valid row; no email is sent yet. Review the staged rows, then choose Invite all just-imported users to actually send the invite emails.

Privacy and recovery

Membership changes affect what a person can access and which manager-scoped surfaces include them. Verify the intended person and organization before sending an invitation, changing access, or assigning a reporting relationship.

• A person's data can be exported on request through their Client Admin, and a deactivated account is permanently erased after a period of inactivity your organization configures, or never, if your organization has not set one.

1. If the Users or Organization source reports an error, choose Refresh sources or Retry for the affected source.
2. If a region source is unavailable, continue only with unit work that does not require region metadata and retry the region source before assigning a region.
3. If no rows appear, confirm the active and search filters before treating the view as empty.

Set the reporting privacy floor

The reporting privacy floor is the smallest group Stride will report on. A unit, region, or segment below the floor shows Insufficient data in executive and Admin roll-ups, so small groups cannot be identified.

• The default is 5.
• Lowering the floor below 5 weakens the privacy protection, so check with your organization's privacy and employee-representation reviewers first.
• The Reporting privacy step in the Admin setup guide points here.

1. Open Organization and find Reporting privacy floor at the top of the page.
2. Enter a whole number from 1 to 100 under Minimum respondents.
3. Choose Save.