Skip to main content

Bring a colleague on board

Who this is for: Operational manager and System admin.

What you will achieve: a new colleague who can sign in, sees the screens their job needs, and is told about the alerts they are responsible for.

Before you start: you need Operational manager or System admin. An Operational manager can give Operational manager, Supervisor and Operator. Only System admin can build or assign custom roles. See What each role can do.

1. Decide what they need to do, before you create anything​

Answer these three questions first. Each one decides a later step.

QuestionWhat it decides
Which screens do they need?Their role (step 2)
Will they handle alerts, or only look?Whether they need to acknowledge and close
Do they need telling away from their desk?Their routing (step 4)

Give people the least that lets them do the job. Rights are easy to add later and awkward to take away once someone has been using them.

2. Choose or build the role​

The Ministry roles are Operational manager, Supervisor and Operator. System admin is the Kairos platform administrator. Machine roles are hidden. Who uses IFMS describes what each does all day, and What each role can do has the full table of screens and actions.

If one of them fits, use it. Building a role per person produces a list nobody can reason about a year later.

If none fits - somebody who should read everything and change nothing, say - build one, following Roles and permissions. Building a role, and giving a custom role to someone, both need a System admin.

A role that can see a screen cannot always use it

Seeing a screen and acting on it are separate rights. A read-only role pointed at Events will see the queue and find the acknowledge and close buttons missing. Check the role against What each role can do before you hand it out, not after the first complaint.

3. Create the user​

  1. In the sidebar, under Administration, select Users.
  2. Check whether the colleague already has an account: set Status to All and search for their email address. If an inactive account comes up, Reactivate it instead of adding a new one — Add user refuses an address that belongs to a deactivated account.
  3. Otherwise, add the user and assign the role, following Users. The roles list shows only the roles you are allowed to give.

Their sign-in is handled by the Ministry's central sign-in service, not by IFMS - see Sign in for what they will see the first time.

4. Make sure the alerts reach them​

This is the step that gets forgotten.

Everyone who can see alerts gets them in the portal and in their Inbox automatically. Email and SMS do not work that way. If this colleague must be told when they are not looking at the screen, add a rule under Alert Routing matching the severity or kind of alert to their role.

Routing rules point at roles, not at people. Adding somebody to a role that already has a rule is enough; it also means removing them from the role quietly stops their messages. A role that is switched off is not offered as a target.

5. Check it worked, with them​

Ask the new colleague to sign in, then check three things together:

  1. The menu. They should see the items their role allows. If the menu looks too short, wait a moment and reload - the menu fills in as their permissions load. If it is still short, the role is wrong.
  2. A screen they need. Have them open the one they will use most. "Access denied" means the role is missing that right.
  3. A message. If you set up routing, wait for a real alert of that severity and confirm it reached them.

When somebody leaves or changes job​

  • Changing job: change their role. Their routing follows automatically, because rules point at roles.
  • Leaving: deactivate the user on Users. They are signed out at once and cannot sign back in. You cannot deactivate yourself, or the last active System admin.