Page not found

The page you are looking for does not exist or has moved.

Page not found

The page you are looking for does not exist or has moved.

Page not found

The page you are looking for does not exist or has moved.

Operators

Our own staff, as Members of the Platform.

Something went wrong on our side. Try again in a moment.

Filter by:

Invitations:

Showing 1–4 of 4Showing 1–5 of 5Showing 1–3 of 3Showing 1–1 of 1Loading Operators… Show per page · Page of 1

Operators
Operator	Email	Roles	Status
Fajar Nugroho You	fajar.nugroho@platform.test	Operator admin, Operator	Active
Fajar Nugroho You	fajar.nugroho@platform.test	Operator admin, Operator	Active
Lina Marlina	lina.marlina@platform.test	Operator admin	Active
Putri Rahayu	putri.rahayu@platform.test	Operator	Active
Rudi Hartanto	rudi.hartanto@platform.test	Operator	Invited until 19 Oct 2026, 14:30 WIB
Maya Putri	maya.putri@platform.test	Operator	Invited until 19 Oct 2026, 15:10 WIB
Lina Marlina	lina.marlina@platform.test	Operator admin	Active

Showing 1–4 of 4Showing 1–5 of 5Showing 1–3 of 3Showing 1–1 of 1Loading Operators… Page of 1

No Operator matches “budi”

Check the spelling, or search by email. Someone whose Membership ended isn't listed.

Invitation sent to Maya PutriThey have until 19 Oct 2026, 15:10 WIB to accept.

Lina Marlina is removedThey were signed out everywhere. The account stays, and can be invited again.

Putri Rahayu is removedThey were signed out everywhere. The account stays, and can be invited again.

Rudi Hartanto's invitation is revokedThe link in their email no longer works.

Shown only with membership.read at the Platform, which Operator admin holds; so is the Operators item in the nav. Without it (an Operator alone) /platform/operators shows the 404 block in the content, the Shell around it (pick Putri Rahayu under "Signed in as"); the backend answers 403 FORBIDDEN anyway. A company's Admin, who holds the key at their own company, never reaches it: it exists only at the Platform, on the private entry point.
The team uses the operations every company uses, at the Platform; there is no operator-only endpoint. The list reads GET /api/org-chart (membership.read) with the Platform active: its active Memberships, then its Invitations, open or expired. An ended Membership never appears. The Platform has no branches, so there is no Branch filter.
The API has no paging, search or filter, so the page does all three over what it holds: 10, 25 or 50 rows a page; the search matches a name or an email, ignoring case. The Invited tag counts what the search leaves, filters the list by it (try it), and hides at 0.
Roles are the Platform template's two, by name: Operator admin (protected) manages Operators and the Platform's Roles; Operator runs companies and people. Someone can hold both. Status is Active, or Invited with "until" and its expiry in the Platform's zone; an expired Invitation would show Expired with "since", as on Members.
A row opens the Operator in a side panel over this list, which holds Change Roles (PUT /api/memberships/{id}/roles) and Remove (Membership removal), or Resend and Revoke on an Invitation. There is no Actions column.
Invite Operator needs invitation.create. POST /api/invitations {organisationId, name, email, roleIds} sends the ordinary Invitation holding Operator, Operator admin or both: an Activation link for a new email, a notice for a registered one. A new email becomes a Pending Person with the typed name; a known one keeps its own. It lasts 7 days.
The form checks the email before sending ("Enter a valid email address."). Main refuses a Person already a Member with 409 ORGANISATION_MEMBERSHIP_EXISTS, one already invited with 409 ORGANISATION_INVITATION_EXISTS ("This Person already has an Invitation here. Resend it instead."), and no Role with 409 ORGANISATION_LAST_ROLE; each shows at the top of the dialog.
Sent: the dialog closes, the new row shows as Invited, and a toast says so. Progress shows on Send invitation only. Everything here is audited in the Platform's own log.

Applied from the rules: the Operators list's row opens an Operator's side panel holding Change Roles and Remove, as Members does, not the mockup's inline row buttons; no access is the 404 block, not the mockup's "Only Operator admins manage Operators" card; the Invite result is a toast, not an alert on the page.
Laid out by the list-page rule, from Members' own parts: the heading and its line with Invite Operator top right, then one tinted card with "Filter by:" and the search, the Invited tag under it, and the table paged above and below, the Operator pinned left.
Status chips carry their icon (Active the success tick, Invited the mail); the expiry sits under the chip. "You" is a neutral chip.
The Invite dialog is a task dialog, as Change Roles is: a borderless close X, Cancel an outline button, both disabled while it sends. Its Roles are the Members picker's checkbox rows, with names only, since the Platform has no branch for the Members picker's "Admin" mark to matter.
A refusal shows at the top of the dialog, the field kept as typed; a malformed email shows on the field only, as the sign-in page's does, with web's "Enter a valid email address.".
Drafted: "lina.marlina@platform.test is already an Operator." for ORGANISATION_MEMBERSHIP_EXISTS, which has no text in main's catalogue; the invited toast's "They have until 19 Oct 2026, 15:10 WIB to accept."; the removed toast "Putri Rahayu is removed" / "They were signed out everywhere. The account stays, and can be invited again."; the revoked toast "Rudi Hartanto's invitation is revoked" / "The link in their email no longer works."; "Loading Operators…", "No Invitations here." and the no-match card's "No Operator matches “budi”" / "Check the spelling, or search by email. Someone whose Membership ended isn't listed.".
The subtitle says "the Platform", the glossary's English for the Platform Organisation, as PR #567 does.
Sample: Fajar Nugroho (you), Lina Marlina, Putri Rahayu and Rudi Hartanto (invited), at platform.test; Maya Putri is the Operator the Invite dialog sends. Her row opens Rudi Hartanto's panel, the Invitation drawn.
After removing Putri Rahayu and after revoking Rudi Hartanto's invitation are where the Operator's panel lands, each without its row and with its toast.
Loading draws four skeleton rows inside the table; a failed read shows INTERNAL's text and Try again, as Members does.

ticket #331 → comment: Operators is a list page by the rule: a tinted card with the "Name or email" search, an Invited count tag, the table paged above and below with Operator pinned, and the row opening the Operator's side panel. The mockup's plain table with inline Change Roles and Remove goes; those live on the panel.
ticket #331 → comment: without membership.read the page is the 404 block in the content, the Shell around it. Both the mockup's "Only Operator admins manage Operators" card and the ticket's "sends them to the first page they may open" go.
ticket #331 → comment: Invite Operator lands on the list with the new Invited row and the toast "Invitation sent to Maya Putri", not the mockup's alert. Send invitation shows its progress on itself.
ticket #331 → comment: ORGANISATION_MEMBERSHIP_EXISTS needs a catalogue text; drafted here as "{email} is already an Operator.", shown at the top of the dialog.
ticket #331 → comment: an Operator's Invitation email links to the public entry point, where the Platform is never a landing or a switch target. Decide where its link leads before Invite ships.

The console opens on Companies; the Platform has no Home. Its nav is Companies, Find person and Operators, then Settings. (12 Oct 2026)
Settings › Organisation at the Platform holds Roles only: Company, Members and Policy import are hidden there, and the Platform's team is this page. (12 Oct 2026)

From operator-console.html (Operators) for the copy and states; spec #322, its comment from #174 and ticket #331 for the behaviour; main's GET /org-chart, POST /invitations and the errorCode texts; the list from settings-members.html