The right access for every staff member

In a paper institute, anyone can open any register. In software you need to decide who can see fees, who can edit students and who can change settings. Instione makes that simple without compromising on safety.

Roles as templates

Roles such as administrator, accountant, front-desk and instructor come ready to use. Think of each one as a starting template: an accountant works with fees, front-desk staff register students and enrol them, and an instructor sees the students in their own batches. Assign a role to a person and they get the matching access.

Adjust for real people

Real staff rarely fit a template perfectly. You can adjust an individual’s access, giving one front-desk person the ability to record payments while leaving the rest of the team without it. You can also see why someone has the access they have.

The server decides

Screens hide what a person should not use, but that is only a convenience. Every request is checked again on the server against that person’s permissions and branch. Changing someone’s access takes effect without a software update, and no one can give themselves more access than they hold.

Accounts you control

Staff do not sign themselves up. An administrator creates the account and provides a temporary password, and the person must choose their own on first login. Each person can view and update their own profile.

Combined with branches

Access can be limited to particular branches; see multi-branch. Who can act is tied to the records in student and staff management, which keeps ownership clear.

Why it matters

Limiting access protects your students’ personal details and your fee records, and it reduces honest mistakes such as a trainee editing the wrong batch.

What is not here yet

Custom role builders, field-level permissions and two-factor login are not available today.