Skip to content
New Kurasa + aiDE · Targeting 31 October 2026. See what’s coming
← Administration

Manage aiDE credits and staff budgets

Review staff credit shares, usage and feature permissions before changing budgets.

Checked on 28 October 2026

On this page

Overview

aiDE allocation sets staff shares and the school pool. Review usage alongside the school’s preparation routine and support needs; a credit count is not a teaching-quality measure.

Get to know the screen

Practice example: all names, records and amounts are fictional. Options vary with your school’s curriculum, currency and access.

Desktop example · Manage aiDE credits and staff budgets

Manage aiDE credits and staff budgets — Desktop example View full-size image
Phone example

Phone example · Manage aiDE credits and staff budgets

Manage aiDE credits and staff budgets — Phone example View full-size image

Interface labels are shown in English. Follow the translated steps below to find each control. Follow the sequence, review the recorded information and choose the next step.

Who can use this feature

Use your own authorised school account. Settings usually require owner, co-owner, administrator or school-leadership access; finance and staff-credit actions have their own permissions. Confirm the specific action with the school lead.

Before you start

Confirm the workspace, academic year, school curriculum and your responsibility for this change. Have the approved school records available and review existing settings before entering replacements.

Confirm school, credit period, staff roles and responsibility for the budget. Check current balances and any approval rules before changing an allocation.

Understand user types and permissions

Sign in and choose your school workspace

Review roles and access

Required and optional fields

FieldRequirementFormat or examplePrerequisite
Credits per person in each editable role bucketRequired when applicableFor an allocation change, enter non-negative whole credits and check the staff counts and pool impact before Save allocation. Budgets and actual usage are different records.The displayed offer, billing period and saved invoice or credit account.
Feature permissions and top-up requestRequired when applicableFeature toggles need an explicit Save changes. A top-up request needs a positive credit amount; add a reason where requested. Buying credits and approving a request are separate actions.Existing school users, supported roles and current allocations.

Picklist prerequisites

ChoiceOptions come fromEarlier selectionIf missing
Offers, invoices and credit allocationsThe selected market, billing period, saved account and authorised staff.Check the offer context and wait for the account to load.Clear filters and distinguish an empty list from a loading or access error.
Users and rolesCurrent school membership and the supported role catalogue.Complete joining first; check the intended staff member before selecting a role.Check pending invitations, current school and role permissions.

Desktop walkthrough

Choose the allocation view

Screen walkthrough · 0:12Download GIF ↓
  1. Open AI and credits and read the overview for the intended school and term. Distinguish plan allocation, purchased credits and actual usage.
  2. Open Allocation and choose the available role/person view. Check editable role buckets and how many people are included.
  3. Enter non-negative whole-credit shares, review their pool effect and Save allocation. Reopen to confirm the saved split.
  4. In Limits and rules, review feature permissions by role and use the explicit Save changes action. Check the intended staff member’s access afterwards.
  5. Review top-up requests individually with their stated purpose. Treat request approval and buying credits as separate actions; verify history and the account after either approved action.

Mobile walkthrough

Choose the allocation view

Screen walkthrough · 0:12Download GIF ↓

On a phone, open the school menu and the feature named in the steps. Open one record or panel at a time. Scroll inside drawers and close the keyboard to reach the lower fields and final action.

Choose prerequisite fields first and check any defaults after changing school, year, class or curriculum. For wide grids and large imports, use landscape or a larger screen; the written instructions remain available.

After an authorised save, wait for confirmation and reopen the record. If a request may have completed, inspect the saved state before trying again.

Save and verify

The saved split, staff permissions and credit history match the approved arrangement. Review the next preparation action when a person’s allocation needs support.

Troubleshooting

An option or feature is missing

Check school, year, role, curriculum and enabled modules. Clear search filters and wait for loading. Resolve the preceding setup item first; ask the administrator to check access if the choice remains unavailable.

A staff member has credits but cannot use a feature

Check role, feature permission, school context and the relevant credit wallet. Increasing a share alone does not grant a disabled feature.

A change did not save

Read the named validation error and correct that field. Check whether any part of the request succeeded before retrying. Keep the original source record available until the saved version has been checked.

Partners