Flint Integration: EdLink Sharing Rules

This article will broadly summarize how to adjust the data coming into Flint from your SIS/LMS via the EdLink Sharing Rules.

Written by Jacob Edington
November 13, 2025

EdLink Background Information

Navigating to Sharing Rules

Log into EdLink

Click on the Integration within your dashboard.

Click on "Sharing Rules" in the top-left corner

Click "Create a Rule"

Note: Sharing rules will share all people and classes that pass a rule.

Logic Categories

Sharing by Class:

• Use this rule when Flint will be used by specific teachers for their individual courses or classrooms. This gives you granular control, allowing teachers to opt-in only the classes relevant to their use of our product.
• This is the most common rule type and is designed to share entire instructional groups.
• Pulls in all classes and students that are in a school.
• When a class is shared, all teachers and students who are enrolled in that class, along with their enrollment records for that class, are automatically shared.

Sharing by School:

• Use this rule when your entire school building will be using Flint, and you want Flint to have access to all students, teachers, and classes within that specific school. This is the broadest level of sharing.
• Shares data based on school designations
• What is shared: The entire school that matches the rule's criteria.
• When a school is shared, all Classes and all People (and their Enrollment records) associated with that school are automatically included.
• Important Consideration: When using "Share by School" rules, it's important to understand that the accuracy of school designations can vary depending on the original data system (LMS/SIS) connected to Edlink.

Sharing by Person:

• Use this rule when you need to share data for only specific students or staff members, perhaps for privacy reasons or specialized programs. This offers the highest level of control over individual data.
• This rule type focuses on individual users and will share the specific person that matches the rule's criteria (e.g., by email, grade level).

Understanding And vs Or Logic

• Within a single rule: The system uses "and" logic. This means that all conditions within a rule must be met for the rule to apply.
• Between multiple rules: The system uses "or" logic. This means that if a user meets the conditions of any one rule, they will be included in the sharing rule.

Sharing Rules Process

There are four steps to sharing rules.

1. Set the Rule: Create a new sharing rule and select "Class" as the rule type. Enter the teacher emails or other identifiers (e.g., role) to generate a list of classes and students.

   • BE SURE TO CHECK THE BOX TO ENABLE DISTRICT RULES - otherwise the rule will not be applied.

2. Check the Materialization: Changes will not show instantaneously in Edlink. A process called materialization needs to run before the rules are applied and the updated data set is available in Edlink.

3. Verify Roles: Once the Materialization is complete, verify that the roles have been assigned correctly. You can do this by clicking on People on the left side to verify that there is something populating under the roles column.

4. Review and Refine: Review the rule and refine it as needed to ensure that it is working as intended. You can use the preview feature to test the rule and make adjustments before saving the changes.

Tips for Sharing Rules

Logic Based on Teacher & Staff Email

The easiest way to pull in your teachers and students is by setting a rule at the Class level and adding all of your teacher's and staff emails.

Roles not Populating

If you check the roles under people and there are not roles assigned, please follow the steps below.

1. Go to Custom Transformations.
2. Create a new transformation and select "Infer Roles" as the transformation type.
3. Configure the transformation to infer roles based on user enrollments.
4. Save and activate the transformation.
5. Verify the roles.

Duplicate Classes Showing

If you have a scenario where you have duplicate classes pulling in, this could mean your SIS/LMS is Fall and Spring classes as two different classes. You can set a rule that allows the data to pull in information in segmented timeframes.