Platform administrator ​

The platform-admin role manages the platform across organizations and campuses. Use it for platform duties and delegated access management. Check the working campus before changing an operational record.

Before you start ​

Activate the account and review profile security. The reviewed template receives all permissions created by the permission seeder. Global scope includes access all schools, access all organizations, and manage platform. Record ownership, state, and feature restrictions still apply to workflows. A role name alone does not replace assigned global permissions.

Create a platform administrator account ​

The installer creates the first platform administrator with chosen credentials. An authorized deployment operator uses the interactive skuul:create-super-admin command for an additional platform administrator. In the local Sail environment:

vendor/bin/sail artisan skuul:create-super-admin

vendor/bin/sail artisan skuul:create-super-admin

The command asks for identity and password details and creates a new account. It is a data-changing operation, rather than a read-only permission check. Use command instructions and the approved operator process before running it. Do not assign a global platform role through the ordinary campus role editor. Organization scope is managed separately through the organization membership workflow.

Prepare organizations and campus access ​

1. Open Organization → Organizations.
2. Follow organization creation for the intended organization.
3. Create its campuses with the correct organization owner.
4. Add organization administrators and review their permitted operations.
5. Arrange campus memberships and roles for the campus staff.
6. Ask each administrator to verify access with their own account.

Use the organization administrator guide for the authority being delegated. Organization scope and operational campus membership are separate. Test both when giving a person duties at more than one campus. For custom duties, follow delegated staff instructions.

Review configuration and access ​

A domain claim identifies a context; it does not grant a person's record access. Account suspension affects sign-in across campuses. End one campus membership when the person should leave only that campus.

Coordinate release and recovery work ​

Read operations with the deployment operator. Review backups, uploaded files, the original application key, queues, scheduler, and monitoring. Use deployment instructions for the release checklist. Use updating instructions for a proposed update.

Platform access does not establish that an upgrade is ready or that an automatic archive restores deleted data. Keep the operator's recovery evidence with the release decision.

Check delegated access ​

Test a permitted task and a denied task with the actual delegated account. Check another-campus access, a revoked membership, and the relevant feature state. A successful platform-admin session does not demonstrate a delegated user's access. Use the worked exercise for teacher, reviewer, accountant duties, and family cooperation.

Follow service recovery when deployment components fail.