Page not found

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

Settings/Roles/Surveyor/Edit
Settings/Roles/Admin/Edit
Settings/Roles/New Role
Settings/Roles/Operator admin/Edit
Settings/Roles/Operator/Edit
Settings/Roles/New Role
Settings/Roles/Edit

Edit SurveyorEdit AdminNew RoleEdit Operator adminEdit OperatorEdit Role

Protected

Held by 12 Members

Held by 7 Members at Surabaya and below

Held by 3 Members

Held by 2 Members

Cancel Cancel Cancel Cancel Cancel Save changes Save changes Create Role
This Role keeps your organisation manageableAdmin always holds every administrative Permission, and it can't be deleted. You can rename it and add other Permissions.
This Role keeps the Platform manageableOperator admin always holds every administrative Permission, and it can't be deleted. You can rename it and add the Platform's Permissions.
Roles are edited at head officeYou can see this Role here. To change it, switch to Asuransi Demo (head office).
Something went wrong on our side. Try again in a moment.
Surveyor

Name

A Role with this name already exists. Choose another name.

Unique in Asuransi Demo, whatever its case. Members see it in their Organisation switcher.

Permissions

Ticking an action also gives what it needs to see; those show as Included.

Permissions marked Admin can be given to a Member only from head office.

Organisation and people
Claim
Policies
Fraud and reports
Some details aren't valid. Check them and try again.

Name

Enter a name for the Role.

Unique in Asuransi Demo, whatever its case. Members see it in their Organisation switcher.

Permissions

Ticking an action also gives what it needs to see; those show as Included.

Permissions marked Admin can be given to a Member only from head office.

Organisation and people
Claim
Policies
Fraud and reports
This Role is protected: it can't be deleted or lose its administrative Permissions.

Name

Unique in the Platform, whatever its case. Operators see it in their Organisation switcher.

Permissions

Ticking an action also gives what it needs to see; those show as Included.

The Platform's Roles hold the Platform's own Permissions, which no company's Role can hold.

Organisation and people
Platform

Name

Unique in the Platform, whatever its case. Operators see it in their Organisation switcher.

Permissions

Ticking an action also gives what it needs to see; those show as Included.

The Platform's Roles hold the Platform's own Permissions, which no company's Role can hold.

Organisation and people
Platform

Name

Unique in the Platform, whatever its case. Operators see it in their Organisation switcher.

Permissions

Ticking an action also gives what it needs to see; those show as Included.

The Platform's Roles hold the Platform's own Permissions, which no company's Role can hold.

Organisation and people
Platform
This Role is protected: it can't be deleted or lose its administrative Permissions.

Name

Unique in Asuransi Demo, whatever its case. Members see it in their Organisation switcher.

Permissions

Ticking an action also gives what it needs to see; those show as Included.

Permissions marked Admin can be given to a Member only from head office.

Organisation and people
Claim
Policies
Fraud and reports
  • New Role (/settings/organisation/roles/new) needs role.create, and editing (/settings/organisation/roles/{id}/edit) needs role.update. Without the key the page shows "Page not found"; a reader has the Role's side panel, not this form.
  • GET /api/permissions (role.read) lists only the Permissions the Organisation's type may hold, each with its group, whether it is administrative and the reads it includes. A group opens when it holds a tick; New Role opens the first. Each group counts what is ticked.
  • Ticking a Permission ticks and locks the reads it includes and marks them Included. POST /api/roles (role.create) and PATCH /api/roles/{id} (role.update) send the name and the whole key set, which replaces the held one; a save stores the reads each Permission includes, so a stored Role is always complete. A Role may hold no Permission.
  • The name is trimmed and unique in the company whatever its case: 409 ORGANISATION_ROLE_NAME_TAKEN shows on the field. A blank name answers 400 VALIDATION, shown at the top of the form with the field marked.
  • On Admin every administrative Permission is ticked and locked; it can be renamed and given other Permissions. Dropping an administrative one answers 409 ORGANISATION_ROLE_PROTECTED, shown at the top of the form; with the boxes locked, only a stale or hand-made request reaches it.
  • Saving works only while head office is the Active Organisation: a page rendered at a branch is read-only with Save hidden, and its request would answer 403 ORGANISATION_ROLE_ROOT_ONLY. A tab rendered for another Organisation is refused earlier with 409 IDENTITY_ORGANISATION_SWITCHED, and the page reloads.
  • Save changes lands on the Role's panel with "Surveyor saved", and Create Role on the new Role's panel with "Senior surveyor created". Cancel and the back icon leave without saving.
  • A rename changes nothing for the Role's holders. A change to its Permissions applies on each holder's next request.
  • Role changes apply at once, as main does. Spec #894 and ticket #912 will make creating a Role and changing its Permissions wait for a second Admin once the company has two approvers (a rename stays immediate); that waiting state is not drawn until #184 is grilled.
  • At the Platform (sign in as the Operator admin), the editor lists the Platform's type: Organisation and people, without the Insurer-only overlap list and support-access grant, and the Platform group, whose Permissions no company's Role can hold. Operator admin is protected as a company's Admin is; its administrative Permissions are ticked and locked.
  • Laid out by the form-page rule: the breadcrumb (Settings opens Company, as Import mapping's does), the back icon beside the title, "Held by …" as the subtitle, and Cancel with Save changes or Create Role top right, each with its busy twin. Delete lives on the Role's panel, not here.
  • The catalogue is main's twenty Insurer Permissions with main's labels, plus the five grilled Claim Permissions (survey, reject, take a Capture, verify and waive a document) and the three fraud ones, which are not built yet but which the prototype's own pages already gate on. Their labels come from the old mockup's naming plan, and "Fraud and reports" is the group #305 names, which main doesn't have yet.
  • Groups keep catalogue order; "Change the Organisation's details" sits last in Organisation and people, where main's array lists it after the Claim Permissions.
  • The form is at most 48rem wide so a label stays beside its chips, which follow the label; the name field is at most 24rem.
  • Name taken shows main's text on the field alone, since it names the field. A blank name shows main's VALIDATION text at the top of the form with the field marked, and Protected refused main's text at the top.
  • At a branch the whole form is disabled and Save hidden; Cancel stays. Saving Admin and Creating have their own busy states, so each Save shows its spinner on its own page.
  • Drafted, defined nowhere: the name's help, its placeholder, "Enter a name for the Role." under a blank name, "Edit Role" while loading, and the branch banner's body here.
  • Applied from the rules: no "Not at root" or "Key not for type" state, as main can't reach them from this page.
  • Drafted: the Platform Permissions' labels other than "See every Organisation with its branches and Admins" (PR #570) and "Receive support access from an Organisation's Admin" (main); the Platform's protected banner; the name help "Unique in the Platform…"; the placeholder "e.g. Support lead". "Protected refused" shows the refusal a save gets when it would drop an administrative Permission.
  • #184 → comment: the editor is a form page: the breadcrumb, the back icon beside the title, and Cancel with Save changes or Create Role top right, with a spinner on the clicked button. The old mockup's "← Roles" link and its buttons at the card's foot go, and Delete moves to the Role's panel.
  • #184 → comment: the catalogue is main's, grouped as drawn: no Settings or Money and parts group, no setting.read and no "First release" state. policyImport.create is not administrative and sits under Policies, and membership.update and invitation.create include role.read beside membership.read.
  • #184 → comment: refusals use main's texts: "A Role with this name already exists. Choose another name." on the field, and VALIDATION and ORGANISATION_ROLE_PROTECTED at the top of the form. "Key not for type" and "Not at root" are not states.
  • #184 → comment: at a branch the editor is read-only with Save hidden.
  • #184 → comment: Permissions show by label only, with no key under the label.
  • Role changes apply at once, as main does. Behaviour names #894 and #912's coming second-Admin approval; its waiting state is not drawn until #184 is grilled. (12 Oct 2026)
  • No access is the "Page not found" block in the content section. (12 Oct 2026)
  • Permissions show their label only. (12 Oct 2026)
  • The Role editor and New Role are full-width form pages outside the Settings frame. (12 Oct 2026)

From roles-and-permissions.html; main's GET /permissions, POST /roles, PATCH /roles/{id}, the permission labels and the errorCode texts; the form page from policy-import-mapping.html