What can an organisation admin do in Skie?

Skie for Enterprise · Updated

Short answer

The organisation admin has the widest view inside a customer account. They set organisation-wide policy and locked settings, choose the web filter from the owner's list, manage schools, users and roles, view reports and the breach centre across everything, and can freeze the organisation or lock all devices at once.

This is the role for the person responsible for the whole deployment, such as an IT head at a trust or a company. It sits above school admins and below the Skie team.

In daily use they set the base: hardening switches, the web filter, the default policies and app lists. They can lock settings at organisation level so lower levels cannot change them. They create schools and invite their admins, and decide which pages each role can see. They also manage the organisation app store, where apps go through a draft stage and then Publish.

For oversight they use the breach centre and Insights across all levels, with sync and resolve at device, group, branch, school and organisation. They can open the audit log, run a compliance check on demand, and use nightly backups with restore preview, restore and restore a previous version.

Two powerful actions belong at this level in practice: freezing the organisation, which blocks new provisioning, and locking all devices at once. Both are covered in their own entries. Seats are granted by the Skie owner, so an organisation admin requests more rather than adding them directly.

Because the role is wide, keep the number of organisation admins small and use individual accounts, never a shared login. Disabling a person who leaves is quick and keeps the audit log meaningful.

Practical tip: give day-to-day work to school admins and branch heads, and use the organisation admin for policy, locking and review.