Skip to main content

Skyward Integration

Manage1to1 integrates directly with Skyward (Qmlativ) using its OneRoster API (OAuth 2.0) to synchronize buildings, students, and staff automatically. Once enabled, Skyward becomes the source of record for roster data in Manage1to1, eliminating manual CSV imports and keeping your roster synchronized daily.

Permission Required

To configure this integration you need the Manage Settings permission.

How it works​

Skyward publishes roster data through a OneRoster API secured with OAuth 2.0; Manage1to1 reads from it on a daily schedule.

Skyward → OneRoster API → Manage1to1

When enabled, buildings are sourced from Skyward, students and staff sync automatically, and manual CSV imports are disabled.

What you'll need from Skyward​

Create a OneRoster 1.1 with OAuth 2.0 connection in Skyward and record these four values:

ValueWhat it is
Base URLYour Skyward OneRoster REST base, ending in the version segment (for example .../ims/oneroster/v1p1).
Token URLThe OAuth 2.0 token endpoint (commonly your base URL with /token).
Client IDThe OAuth 2.0 Client ID generated for the OneRoster connection.
Client SecretThe OAuth 2.0 Client Secret. Stored encrypted.

Connect it in Manage1to1​

  1. Go to Settings → Rostering & SIS and find User Rostering.
  2. Select Configure Provider and set the provider to Skyward.
  3. Enter the Base URL, Token URL, Client ID, and Client Secret.
  4. Use Test Configuration to confirm connectivity.

If the test fails, check that each value was copied exactly (no extra spaces), the connection is still active in Skyward, and the right schools were granted access.

First synchronization​

Run the Building Synchronization first (required), confirm your buildings imported, then run the student and staff sync. Building identifiers (sourcedId) must line up with the building SIS IDs already in Manage1to1, or students tied to unknown buildings are skipped. After that, Manage1to1 keeps your roster aligned with Skyward daily.