ROKRescue Operator Knowledge

How it works

Agencies, members and what's separate

How ROK keeps each agency's content, people and recognition apart — and what changes when someone belongs to more than one.

ROK runs many agencies on one system. Everything you create — content, tags, media, groups, badges, settings, branding — belongs to your agency and is invisible to every other one.

One login, many agenciesOne loginone profileRescue Team — activeMembershipAuthor + OperatorIts contentguides, tags, mediaIts recognitionbadges, ladder, pointsCoastal SES — not activeMembershipOperator onlyIts contentinvisible right nowIts recognitionseparate pointsEverything an agency owns is scoped to it. Switching the active agency switches the whole picture.Same person.Different powersin each agency.Nothing crosses the boundary — not content, not points, not permissions. The database enforces it per request.
One login, many agencies. Only one is active at a time.

One login, many agencies

A person has one account. If they volunteer with two agencies, they don't get two logins — they get one login with two memberships.

Memberships are independent. Someone can be an author in one agency and a plain operator in another; nothing carries across. Their points, badges and level are counted separately too, because they earned them in different places doing different things.

Only one agency is active

At any moment a session has exactly one active agency, and everything you see belongs to it. Switching agencies is deliberate — from the switcher in the header — and reloads the whole picture.

The active agency belongs to the sign-in, not the account: each browser and each phone keeps its own. Switching on a laptop moves nothing on your phone; it only sets where your next sign-in starts. The tabs of one browser share one sign-in, so a switch in one tab reaches the others — they say so and stop saving until you choose.

The separation isn't in the app

This is the part worth trusting. Agencies aren't kept apart by the console remembering to filter its lists — they're kept apart by the database, which decides on every single request which rows the current session is allowed to see at all.

So a bug in a screen is not what keeps agencies apart: the database decides which rows a session can read, whatever the screen asks for. See how ROK keeps agencies' data separate.

What's shared on purpose

Two things are deliberately visible to everyone:

  • The ROK Library — content authored centrally that any agency can browse and import. An import takes a copy; from then on it's yours, and editing it changes nothing for anyone else.
  • The ROK badge and track catalog — recognition designs your agency can switch on as-is or duplicate and customise.

In both cases the shared thing is a source, not a link. Nothing you do to your copy travels back, and nothing changes under you.

What platform staff can see

ROK platform administrators can enter an agency for support. It isn't a quiet back door:

  • Each visit needs a stated reason, and its start and end — with that reason — are written to your agency's audit log, where your administrators can read them.
  • A visit is view only unless they chose to make edits, and even then it can never publish, delete content, reach your operators' phones, alter who has access or touch billing.
  • It ends after four hours at most, and a banner shows on their screen for the whole visit.

A ROK administrator you have invited into your agency is an ordinary member there, with only the access you gave them.

See also

Last reviewed