Skip to main content

Aeries Integration

Manage1to1 integrates directly with Aeries using its OneRoster API (OAuth 2.0) to synchronize buildings, students, and staff automatically.

Once enabled, Aeries becomes the source of record for roster data in Manage1to1, eliminating manual CSV imports and keeping your roster synchronized daily.

Permission Required

To configure the Aeries integration, you need the Manage Settings permission assigned to your role.


Understanding the Aeries Integration​

Think of the Aeries OneRoster integration as a direct, secure connection between Aeries and Manage1to1. Roster data flows automatically, so you no longer export and import CSV files by hand.

What the Aeries integration does:

  • Imports buildings directly from Aeries
  • Synchronizes students and staff automatically
  • Eliminates manual CSV exports and imports
  • Keeps Manage1to1 aligned with Aeries daily

Why use the Aeries OneRoster connection:

  • Direct integration - A native connection to your SIS
  • OAuth security - Secure authentication using industry standards
  • Automated - A daily sync keeps data current without manual effort
  • Reliable - OneRoster is a proven standard for roster exchange

Overview​

Aeries publishes roster data through a OneRoster API secured with OAuth 2.0. Manage1to1 connects to this API to consume roster data and keep your district aligned automatically.

How it works:

Aeries → OneRoster API → Manage1to1

When this integration is enabled:

  • Buildings are sourced from Aeries
  • Students and staff are synchronized automatically
  • Manual CSV-based imports are disabled
  • OneRoster becomes the exclusive roster source

Important Notes​

Before enabling OneRoster:

  • When OneRoster is enabled, Manage1to1 relies on Aeries for buildings and user roster data.
  • If you enable OneRoster after Manage1to1 is already in use, confirm the Aeries school building identifiers (sourcedId) align with the building identifiers already stored in Manage1to1 (commonly the SIS value used in Building Management).
  • A one-time Building Synchronization is required after connection. Students tied to buildings that do not exist in Manage1to1 are ignored.

Building alignment is critical: If building identifiers do not match between Aeries and Manage1to1, students will not import correctly. Review building SIS IDs in Manage1to1 before enabling the integration.


What You'll Need from Aeries​

When configuring Aeries as your OneRoster provider, Manage1to1 needs a small set of values from the OneRoster connection configured in Aeries. Your Aeries administrator can provide these.

Use OneRoster 1.1 with OAuth 2.0

Create the connection in Aeries as OneRoster 1.1 with OAuth 2.0, and use the Client ID and Client Secret it issues.

Base URL​

The Base URL is your district's Aeries OneRoster endpoint. It tells Manage1to1 where to send all OneRoster requests for buildings, users, and related data.

What it looks like: https://your-district.aeries.net/aeries/api/v3/ims/oneroster/v1p1

Where to find it: Copy the exact URL from the OneRoster configuration in Aeries. Include the version segment at the end.

Token URL​

The Token URL is where Manage1to1 requests OAuth access tokens. These tokens are required for every OneRoster request and are refreshed automatically during synchronization.

What it looks like: The OAuth 2.0 token endpoint shown with your Aeries OneRoster configuration, commonly your base URL followed by /token.

Client ID​

The OAuth 2.0 Client ID uniquely identifies Manage1to1 as an approved application in Aeries.

Where to find it: Generated when the OneRoster connection for Manage1to1 is created in Aeries.

Important: Copy this value exactly as provided. Do not modify or truncate it.

Client Secret​

The OAuth 2.0 Client Secret is paired with the Client ID and authenticates Manage1to1 when it requests access tokens.

Where to find it: Provided with the OAuth 2.0 OneRoster configuration in Aeries.

Security: Treat this value as sensitive. Only an administrator with appropriate access should enter it, and it should never be shared publicly. Manage1to1 stores it encrypted.


Step 1: Create the OneRoster Connection in Aeries​

Work with your Aeries administrator to create a OneRoster connection for Manage1to1 using OneRoster 1.1 with OAuth 2.0, and grant it access to the schools you want to sync. When it is created, record the values Manage1to1 needs.

What to record:

  • Base URL
  • Token URL
  • Client ID
  • Client Secret

Tip: Copy these values to a secure document for reference. You will enter them into Manage1to1 in the next step.


Step 2: Enable Aeries as the OneRoster Provider in Manage1to1​

After the connection exists in Aeries, connect Manage1to1 to it.

Steps:

  1. In Manage1to1, navigate to Settings → Rostering & SIS and find the User Rostering section.
  2. Select Configure Provider.
  3. Set the Rostering Provider to Aeries.
  4. Enter the values from your Aeries OneRoster configuration:
    • Base URL - OneRoster API endpoint
    • Token URL - OAuth token endpoint
    • Client ID - Application identifier
    • Client Secret - Authentication secret
  5. Use Test Configuration to confirm connectivity.

If the test fails:

  • Verify every value was copied correctly (no extra spaces, no truncation).
  • Confirm the OneRoster connection is still active in Aeries.
  • Check that school access was granted correctly.
  • Contact Manage1to1 Support if issues persist.

Once the configuration test passes, Manage1to1 is ready for OneRoster synchronization.


Step 3: Initial Synchronization​

After the provider is enabled, run the initial synchronization to import buildings and users. Run the Building Synchronization first (it is required), confirm your buildings imported, then run the student and staff synchronization. From then on, Manage1to1 keeps your roster aligned with Aeries on a daily schedule.