Critical DevelopmentsFrom First Principles Works

Shared service · Account

Shared sign-in, licences and appropriate access

Shared sign-in, school membership, licences and appropriate access for the tools your school chooses.

Areas 4Features 10Fictional school records

Account connects the six apps through school access, licences and shared settings.

Explore Account

School examples and feature detail.

Area 1 of 4

Account

Reach the tools your school has chosen

Use the shared school sign-in and Account home to reach licensed products, with each tool's own rights and responsibilities kept clear.

Account provides the shared school service for your chosen Critical Developments tools. Each product keeps its own licence and record permissions.

A configured school sign-in

Reach the school's available tools through its configured sign-in route. Microsoft and Google connections are activated during onboarding; local accounts are invitation-only. Opening Account does not assign access to every product or pupil record.

Request, review and activate

Request a product licence and attach the relevant order or contract evidence for separate review. A request, estimate or purchase order is not activation. Check the licence's confirmed status before relying on product access.

The full suite includes all six product apps, including Ready and WorkPane, plus shared Account. Confirm your school's chosen products, setup and availability.

Use the school's configured sign-in route. Current Account sign-in; options depend on school configuration.
Account · Reach the tools your school has chosenFictional school recordsOpen full screenshot

Choose a numbered marker to look closer.

  1. Start with your work email

  2. Use a configured school account

See 2 features in this areaFeature guide · page 78

Account

Match access to responsibilities

Keep school membership and product duties distinct, so staff can reach the work they are responsible for without blanket pupil access.

Account provides the shared school service for your chosen Critical Developments tools. Each product keeps its own licence and record permissions.

People and school membership

Invite staff, review their Account access level and manage school membership status. Ask the colleague to confirm that the invitation arrived, then check that their membership is in the intended state.

Product duties stay specific

Use designated product permission workspaces to assign responsibilities. An Account level does not confer every app capability or pupil record. Product Leads, professional designations and source scope remain distinct; administration does not create blanket pupil access.

Recent account changes

Review bounded recent account and access activity without opening pupil records. It helps explain school-account changes, while product records keep their own histories and permissions.

Account activity is not a complete pupil-work audit or a compliance certificate. Use each product's record and access controls for its own work.

Product duties stay specific. HP Source access profiles illustrate product-specific duties. Illustrative school data.
Account · Match access to responsibilitiesFictional school recordsOpen full screenshot

Choose a numbered marker to look closer.

  1. Different duties, different profiles

  2. Administration is separate from pupil access

See 3 features in this areaFeature guide · page 79

Account

Keep shared school information consistent

Maintain the school information adopted by the products and arrange approved directory connections with a clear scope.

School setup required

Wonde MIS integration needs school approval and checked setup. Product connections and calendar sources are agreed separately; each product keeps its licence and record permissions.

Shared identity and school day

Manage configured school presentation and school-day/calendar fields through designated Account settings. Only adopted shared fields carry into the products that use them. Check the school's setup rather than assuming a complete timetable or automatically inferred schedule.

Wonde MIS integration and staff links

Connect supported MIS data through Wonde and keep verified staff linked to current directory records. School and supplier approval, an agreed minimum scope and checked setup are required. Email addresses or domains do not create inferred matches.

Confirm supported MIS systems, data and permissions for your school. Synchronisation stays within the agreed scope; these settings do not provide automatic timetable write-back.

Show the configured school day in context. WorkPane calendar illustrates configured school-day information. Illustrative school data.
Account · Keep shared school information consistentFictional school recordsOpen full screenshot

Choose a numbered marker to look closer.

  1. Use the configured week and timezone

See 2 features in this areaFeature guide · page 80

Account

Protect sign-in and recover checked access

Use the school's configured verification policy, request help when a method is lost and review signed-in sessions deliberately.

Account provides the shared school service for your chosen Critical Developments tools. Each product keeps its own licence and record permissions.

Renew sensitive verification

Set the school verification policy and require renewed verification for sensitive Account changes. The available methods depend on the configured provider and current school policy.

A checked recovery request

Record a request when a member loses an enrolled verification method. The request does not bypass the checks or guarantee a reset. Microsoft or Google password recovery remains with the school or provider.

Review signed-in sessions

Inspect current Account sessions and deliberately end another session through the security controls. The result shown applies to the selected Account session. Check any other product or provider access separately.

School/provider account recovery and other signed-in services retain their own controls. Follow the displayed outcome before assuming that access has changed.

See 3 features in this areaFeature guide · page 81

Find the detail

Account feature library

Browse by school job, feature or the people using it.

Areas 4

Features 10

Reach the tools your school has chosen

Follow this walkthrough

Account provides the shared school service for your chosen Critical Developments tools. Each product keeps its own licence and record permissions.

Match access to responsibilities

Follow this walkthrough

Account provides the shared school service for your chosen Critical Developments tools. Each product keeps its own licence and record permissions.

Product-scoped permissions

Use designated product permission workspaces and assignments to match access to responsibilities.

For Designated administrators, Product leads

Account activity view

Review bounded recent account/access events without exposing pupil records.

For School administrators

Keep shared school information consistent

Follow this walkthrough
School setup required

Wonde MIS integration needs school approval and checked setup. Product connections and calendar sources are agreed separately; each product keeps its licence and record permissions.

Approved MIS connection and staff links

Request the school-approved Wonde connection and retain checked links between verified staff identities and current directory records.

For School administrators, Integration leads

Protect sign-in and recover checked access

Follow this walkthrough

Account provides the shared school service for your chosen Critical Developments tools. Each product keeps its own licence and record permissions.

Make it work for your school

See the fit. Then talk it through.

Explore another app, check the complete annual price, or arrange a conversation about your school’s needs and Wonde MIS integration.

See pricing and next stepsExplore the six appsExplore the suite

Account screen

Fictional school records · Escape closes this view