A login for your child

On this page

Children can log in to obacht too, if you want them to. With their own login a child sees what you see about them (today's time, history, apps, devices, limits and the media agreement) and can propose changes to their limits and the agreement. You accept or decline. Nothing changes without a parent, so the negotiation happens in obacht instead of at the dinner table.

Setting it up

Open the child, then Settings → Login for the child, and choose a username and a password (at least 10 characters). The child logs in with them in the obacht app, on their own phone or a family computer. A new password, or a new username, logs the child out everywhere. Remove login takes the login away again; proposals waiting for an answer stay.

When your obacht uses a login provider (see Setting up obacht), there is no password in obacht: create an account for the child at the provider with the same username, and leave it out of the parent group. The child then logs in through the provider like you do. A provider that speaks SCIM can do both steps itself; see Accounts from your login provider.

Proposals

Logged in, the child opens Limits or Agreement, changes what they would like (more time for games, a later bedtime on Fridays, a sentence for the parents such as "No phones at dinner, parents too"), writes a few words why, and taps Propose to my parents.

Parents see "Lena proposes changes" on the start page and get a notification if notifications are on. On the child's page they see each change as before and after, write an answer if they like, and Accept or Decline.
Accepting applies what the child changed. Anything a parent changed meanwhile elsewhere (an app approved, another limit) stays as it is.
The child sees that their proposal is waiting, can take it back, and sees the answer once a parent has decided.
One at a time. A new proposal replaces the one still waiting.
Not too often. A child can send 5 proposals a day. Extra time and pauses can't be proposed: extra time is asked for on the child's device.

Everything else is read-only for the child: they can't change rules, answer requests, pair devices, change settings, add children or parents, or create API tokens.

Asking for extra time

Asking for more time from the child's device works at most once every 10 minutes and 6 times a day per child, counted across all their devices. The device tells the child to wait a bit before asking again.

For integrations

Everything here is in the API: PUT, GET and DELETE /api/v1/children/{id}/login, POST and GET /api/v1/children/{id}/proposals, POST /api/v1/proposals/{id}/accept and /decline, and DELETE /api/v1/proposals/{id} to take one back. A child's login gets a session token like a parent's; GET /api/v1/permissions says whose it is (child_id) and what it may do. With permissions per parent, a decision point can take things away from a child's login, but never allow more than viewing and proposing.

This page is part of obacht's documentation, licensed under CC BY 4.0. Source on GitHub · CC BY 4.0 · Version: main (2ab2740)