Settings and admin

Yes. Everything saves as you go.

Some steps tick by themselves when the work is done on their own page. Do the work there.

A step needed before going live is still open. The page names it.

No. Skipping only lets you carry on. Come back to it.

Admins. Managers and DSLs see only the steps that are theirs.

No record changes. Only the word used to describe it changes, everywhere it is shown.

Yes. Press Reset to our default on the card. The standard word comes back at once.

Either a box needs fixing, which the line under the boxes explains, or you are a manager and changes are not allowed yet.

Everyone in your organisation, and anyone who receives your emails and reports, including schools and families.

It is the possessive form, as in the thing that belongs to one person. The sample sentence shows how each form is used.

Field labels are separate. Edit them on Record fields. They are listed on this page.

Admins only. Anyone else sees that this page is for administrators.

It does not contrast enough with white, so text on it would be hard to read. Pick a darker one.

They moved here. The old addresses send you to this page.

One logo is used everywhere. Upload it once under branding and emails follow.

Seats are set from your subscription. Use the portal on the billing page or ask the platform team.

No. It only changes what is shown. Your web address is set by the platform team.

No. Nothing is deleted. Switch it back on and everything is there again.

It still holds open items. The row says what and links to it. Deal with them, then try again.

Everyone who opens the page. Each row shows who set it and when, and the history is kept.

At the end of the set-up guide, or under Organisation policies on the switches page.

A switch used to try something with a few people first. Leave flags alone unless the platform team asks you.

They can see which are on. Changing them is for admins, and for a DSL on the statutory registers.

You can retire it. Answers already entered are kept, and Restore brings the field back.

The record has no meaning without it, so it cannot be hidden. Rename it if the wording is wrong.

Only the roles you choose under Who can see it. Pick the narrowest group that needs it.

No. The data stays. The field simply stops showing on the form.

Mark it required for onboarding on the built-in list, or on a custom field when you add it.

A rename on the words page does not change field labels. Edit them here.

No. Categories are retired, never deleted. Records filed under one keep it.

No. It is a starting point only. A record's urgency is set when it is raised.

No. Records keep the version they were asked.

People who manage safeguarding categories. Others are shown who to ask.

It is not live until you publish it.

Yes. Choose a category, then name people for one area on top of the organisation-wide row.

Check text messages are switched on under modules, and that the contact has a mobile number.

Only the first name is offered, to keep texts light on detail.

Yes. Later texts use the new wording. Ones already sent are unchanged.

Press Archive. You can still see it afterwards.

Admins in their own view. Viewing as someone else is read-only.

It is the long code in the web address of their record page.

JSON is the records only. ZIP adds their documents.

No, apart from limited recovery inside the retention window. Treat it as final.

Erasing is sensitive, so it needs a sign-in from the last five minutes.

It may, inside notes. Read it and remove what you must before sending.

No. It pauses work on the record and keeps everything.

Yes, but nothing can be added or changed.

Yes. They are excluded from combined reporting while restricted.

Until the reason has gone. Look at it again regularly.

Say who asked, what they asked for and the date. Someone reading it months later should understand why the record was paused.

Yes. Every restriction and lift goes into the audit log.

No. It needs a DSL and a data protection lead, then an admin to carry it out.

It is the long code in the web address of the concern.

Admins, data protection leads and DSLs.

Yes. Every step is written to the audit log.

Do not approve it. Ask the others not to approve either.

For thirty days after it was removed.

No. This page restores removed write-ups only.

Only admins, after a fresh sign-in and typing PURGE.

It runs across every organisation, so only the platform team can start it.

Until they turn twenty-five.

Seven days. After that it and the copied files are deleted.

Press Download again. A new link lasts fifteen minutes.

No. Nothing here deletes or seals data.

Admins. Data protection leads and DSLs can open the export page too.

Yes, with Cancel this case. Exports already made are kept.

You can only export records you can access. The page counts those left out.

Yes, with the time and a reference.

Use the organisation export for that.

You may have hit the limit of five a minute. Wait a moment and try again.

Admins.

This page records the details. Keep the signed document in your usual storage.

Admins and data protection leads.

Leave the expiry blank. It stays in force until you mark it expired.

Its expiry is within thirty days.

No. It is a record. Sharing is switched on where it happens.

Only if you tick Show names. Otherwise it sees codes or labels.

Never. The most they see is type and dates.

The agreement runs for twelve months and can be renewed.

Yes. Untick what it sees, or use Pause access on a login.

Press Preview what they see →.

The log holds sensitive detail, so it needs a sign-in from the last five minutes.

No. It begins when records were tagged to your organisation, shown at the top.

No. The log is read-only.

Each use of an AI feature, the model, the user, the result, and what was removed first.

Managers, admins and data protection leads.

Work with no route goes to nobody. Add an organisation backstop.

The most specific: a child, then a mentor, then an area, then the organisation.

Self-sign-off rules are set per stage on stage settings.

On their own profile, which says where their write-ups go.

Yes, on History. Ended routes stay listed.

No. It applies to admins and DSLs. Anyone else can set it up early.

Not through this route. They ask and an administrator approves.

At most an hour, and it cannot be extended.

They contact support, who check it is them and reset it.

Not yet.

Any that supports SAML, including Entra, Okta and Google Workspace.

Yes unless you tighten it. Test before relying on it.

Change it on the team page. The default is only a fallback.

Admins only.

No. Disabling it just returns people to passwords.

No. It is shown once. Revoke it and make a new one.

They limit what a key can read, such as people, sessions or reports.

Yes, with longer gaps, up to ten times.

Admins. Some are normally used with the platform team.

In the API quickstart guide.

It sends the email to the team inbox, with the real recipient in the subject.

Yes. Sign-in links and invitations always go to the real person.

The platform team holds it. The row says so.

No. They only show how the emails look.

Admins.

Two write-ups overlap. It may be a genuine copy or a shared session. You decide.

It links to the record. Fix it there.

Only the latest sign-in is kept, so a long sign-in may not show.

The monitor every twenty seconds.

Admins.

It is now on the organisation details page.

On the reports page, in a panel.

In the emails settings, on the half-term report rows.

To Onboarding, under the welcome pack.

Yes. It redirects to the new page.