Skip to content

Custom User Settings

District admins only. Editing school access or additional teacher access on another user is restricted to district admin accounts. School users, teacher users, and plain district users cannot make these changes. If you don't see the edit form on a user, your account doesn't have permission.

Custom settings are exceptions to the default user scoping. The two common cases:

  • A school user who needs access to more than one school.
  • A teacher user who needs access to more than one teacher's classroom and students.

These are configurable directly from the user's edit page in TKG Analytics by a district admin. You no longer need a support ticket for either one.

Multi-School Assignment (School Users)

Use this for staff serving roles that span more than one campus (assistant principals, specialists, coordinators). Their scope expands to all teachers and students across the assigned schools.

How to set it up

  1. Open the user menu and pick School Users.
  2. Click the school user whose access you want to broaden.
  3. In their edit form, find the School access multi-select.
  4. Add the additional schools. You can also remove schools to narrow access.
  5. Click Update Account user.

The change applies immediately. The next nightly SIS sync will not override these multi-school assignments (see CSV Interaction below).

Multi-Teacher Assignment (Teacher Users)

Use this when a teacher takes on additional responsibilities like lead or mentor teacher, supporting students across multiple classrooms. Their scope expands to include the additional teachers' students.

How to set it up

  1. Open the user menu and pick Teacher Users.
  2. Click the teacher whose access you want to broaden.
  3. In their edit form, find the Additional teacher access multi-select. (The Teacher Record field above it is the teacher's own record and is managed by your SIS.)
  4. Add the additional teachers. You can also remove teachers to narrow access.
  5. Click Update Account user.

CSV Interaction

CSV imports will not overwrite the custom access you set here.

Anything you decide by hand takes that user off nightly management. Anything the import already leaves alone keeps them on it.

What you change in the app Still managed by the nightly import?
Role change, including upgrading a Teacher No. Their role and schools are yours from then on.
School access change No.
Reactivating a user No. They are not deactivated again for being absent from the CSV.
Uploader or Maintenance add-on Yes. Those grants survive every import anyway.
Additional teacher access Yes. The import never touches those grants.
Any edit to someone who stays a Teacher Yes, unless they were already taken off it. Their scope comes from teachers.csv.
Name and email Yes. Updated by the import for everyone it lists.

Two notes on teachers. You cannot change a teacher's school access on its own: while Teacher is the selected role the school picker is hidden, and only Additional teacher access is editable. To give a teacher school or district scope, upgrade them and assign the schools in the same change. Upgrading does not touch their Teacher record, so their scores are still attributed to them normally.

Changing a role or school access, or reactivating a user, also turns off automatic deprovisioning for that user. Nightly imports remove access for anyone missing from the CSV, but only while that user is still managed by the import. Once you change their role or their schools, or reactivate them, dropping them from the CSV no longer removes their access. Use Deactivate on their edit page instead. This is the same behavior as the rollover wizard's user review steps.

When to still contact support

Self-serve covers extra school and teacher access on existing users. To make someone a District Admin, promote an existing user from their edit page (Make District Admin), up to the district maximum of 5. Open a Helpdesk Ticket if you need help reversing a misconfigured assignment you can't sort out from the user edit page.

Tips for Success

  • Verify whether a user truly needs multi-school or multi-teacher access before granting it. Default scoping is usually correct.
  • Audit your multi-assigned users periodically. The Version History panel on the user edit page shows who added or removed each school or teacher and when.
  • The CSV stays the source of truth for everything except the custom scope. Keep it clean.

Need Help?