Home / From record to access

From record to access

A smoother handoff starts with a clear process.

Start with a single process, such as provisioning new students. Connect the right systems, validate the rules and expand when your team is ready.

Sample workflow · Active Directory + SIS

From local agent
to student onboarded.

An illustrative onboarding flow. Your institution chooses the trigger, mappings, systems and required steps.

  1. 01CAMPUS · SETUP

    Connect the local agent

    Install the agent on a Windows or Linux server and configure its Active Directory and SIS connections. The agent opens an encrypted outbound connection to OnboardConnect.

    Step details

    Your team grants the permissions and command access needed for this workflow.

  2. 02SLATE · TRIGGER

    A student becomes eligible

    A configured Slate query supplies the student record. Your eligibility rules decide which records move forward.

    Step details

    Example: include newly enrolled students with the required identity fields.

  3. 03ONBOARDCONNECT · WORKFLOW

    Validate and map the record

    Filter the incoming data, map student fields and choose the account and campus-system actions to run.

    Step details

    Example: map a student identifier, name, account name and target groups.

  4. 04CAMPUS · PROVISION

    Create the account

    OnboardConnect dispatches the configured task over the agent’s established connection. The agent creates the Active Directory account and applies the selected groups.

    Step details

    The agent returns the result to the workflow. Cloud-directory actions use their configured cloud connections.

  5. 05SIS · WRITEBACK

    Update the student record

    A configured SIS writeback step sends mapped account details to the student system through the agent. Additional Slate writeback steps can follow.

    Step details

    The values and operations depend on your SIS connection, field mappings and permissions; username writeback is available for Ellucian Ethos (Banner and Colleague).

  6. 06STUDENT · READY

    Student onboarded

    After the required steps succeed, send the configured welcome message with next steps for accessing campus services.

    Step details

    IT can review the run history and confirm the handoff across connected systems.

The agent establishes the outbound connection first; the Slate record triggers the onboarding workflow. No inbound connections from the internet are required.

01 / From record to access

01. Connect your data and systems.

Choose the Slate query, or another source such as a CSV upload or webhook, that represents the students you want to process. Configure your target directories and any campus-system connections.

  • Agree on the source records, identifiers and fields with your Slate administrator.
  • Authorize Microsoft Entra ID or Google Workspace connections as needed.
  • Install the agent on a Windows or Linux server for on-premises Active Directory, SIS, SQL Server or file operations.
  • Confirm outbound connectivity and the permissions required by each connection.

02 / From record to access

02. Put your rules into a workflow.

Use the visual builder to order actions, map fields and branch on outcomes. Make exceptions part of the design from the beginning.

  • Filter to the records that should enter this process.
  • Transform values and map them to the fields each action expects.
  • Add provisioning, writeback, file and notification steps.
  • Define the success and failure paths your team needs.

03 / From record to access

03. Validate before you expand.

Run a controlled set of representative records and review the outcome in each connected system.

  • Confirm account naming, matching and group placement.
  • Review step results, error paths and any writeback values.
  • Test recovery routing and messaging if you enable self-service.
  • Agree on a rollout schedule and ownership of exceptions.

04 / From record to access

04. Run, review and refine.

Enable your workflow and use execution history to understand what happened. Add further lifecycle processes as your needs grow.

  • Review successful and failed steps in run history.
  • Adjust mappings and rules as your source data changes.
  • Create separate workflows for updates, access changes and departures.
  • Measure performance against your own intake volume and system schedules.

Your next step

Let's map your first workflow.

Bring your systems, questions and requirements. We'll work through the handoffs together.

Use the evaluation guide ↗

Request a 90-day trial ↗