Page not found

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

Roles

Shared by Asuransi Demo and every branch under it. Members get one or more Roles at the branch they work in.

The Platform's own Roles. Operator admin manages Operators and these Roles; Operator runs companies and people.

New Role New Role

Roles are edited at head officeYou can see them and assign them to Members here. To create or change a Role, switch to Asuransi Demo (head office).

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

Filter by:

Showing 1–10 of 15Showing 1–2 of 2Showing 1–1 of 1Showing 1–10 of 14Loading Roles…Show per page · Page of 211

Roles
Role	Permissions	Members
Adjuster	2	94
Admin Protected	16	31
Auditor	3	10
Branch head	3	21
Call centre	3	40
Claim registration	5	52
Complaints handler	1	00
Finance	1	31
Fraud investigator	5	10
Manager	4	21
Recovery	1	0
Surveyor	10	12
Operator admin Protected	10	2
Operator	6	2

Showing 1–10 of 15Showing 1–2 of 2Showing 1–1 of 1Showing 1–10 of 14Loading Roles…Page of 211

No Role matches "Underwriter"

Check the spelling, or clear the search to see every Role.

Renaming a Role keeps every Member who holds it. A Role in use can't be deleted.

The Members column counts those at Surabaya and the branches under it.

You can see the Roles and who holds them. Creating or changing one needs a Role holding "Create a Role" or "Rename a Role or change its Permissions".

Complaints handler deleted

GET /api/roles needs role.read. Without it the Organisation menu hides Roles, and the page shows the "Page not found" block inside the Settings frame.
The list is the root's Roles, by name and then id, and it is the same list at head office and at every branch. Only Members changes: it counts the active Memberships holding the Role at the Active Organisation and the branches under it, so a branch sees its own, smaller counts. Invitations are never counted.
The API has no paging and no search, so the page pages (10, 25 or 50 a page) and searches the Roles it already holds. The search matches the Role's name as you type, ignoring case.
Creating, changing and deleting a Role work only while head office is the Active Organisation. At a branch the banner shows and New Role hides. New Role needs role.create and opens the Role editor.
Admin is protected: it can be renamed and given more Permissions, but never deleted, and it always holds every administrative Permission.
At the Platform (sign in as an Operator admin) the list holds the Platform's two Roles from its template: Operator admin, protected, and Operator. Settings › Organisation holds only Roles there; the team is the console's Operators page.
A row opens the Role in a read-only side panel. A Role deleted from its panel lands back here with a toast, and its row is gone.
Role changes apply at once, as main does. Spec #894 and ticket #912 will make creating a Role, changing its Permissions, deleting it and giving an administrative Role wait for a second Admin once the company has two approvers; that waiting state is not drawn until #184 is grilled.

Laid out by the list-page rule inside the Settings frame, its content column widened: the heading and its line above, New Role on the right, then one tinted card holding the "Filter by:" row with the search and the table, paged above and below. Role is pinned left, and the whole row opens the Role.
The heading sits above the card, as Policy import's does: "Roles" is an h2 under the Settings h1.
No count tags under the filters: a Role has no status to count by.
The 15 Roles are main's 14 seeded ones and "Call centre", which the company made. Surveyor's 10 Permissions and Fraud investigator's 5 include the grilled Claim and fraud Permissions the prototype's other pages already gate on; main seeds Surveyor with 3 today.
"Protected" is a neutral chip with the shield icon, since a chip takes the neutral tone or a Status; the old mockup's brand chip goes.
At a branch and read-only are drawn as states of the Admin; in the app they follow the Active Organisation and the Person's keys. The branch's Member counts are sample numbers.
A failed read shows INTERNAL's text with "Try again", and "Clear the search" goes back to every Role, as on Policies.
Drafted, defined nowhere: "No Role matches …" and its line, "Loading Roles…", the branch's line on what Members counts, the read-only line, and the toast "Complaints handler deleted".
Applied from the rules: a row opens a read-only panel with Edit, and a company always has Roles, so there is no empty state.

#184 → comment: the Roles list is a list page: one tinted card with a "Role name" search in its "Filter by:" row, paging above and below, and Role pinned left. The old mockup's plain card has none of them.
#184 → comment: rows come in GET /roles's order, by name, not the old mockup's seeded order, with main's counts. Admin holds 16 Permissions and is the only Role holding an administrative one; Auditor carries no chip.
#184 → comment: a row opens the Role's read-only side panel, not the editor.
#184 → comment: at a branch Members shows the branch's own counts, since memberCount narrows to the Scope; the old mockup repeats head office's.
#184 → comment: without role.read the page shows "Page not found" in the Settings content, not a redirect with a notice.

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, with the Settings tabs and menu kept around it. (12 Oct 2026)
The Roles list sits in the Settings frame with the content column widened. (12 Oct 2026)
At the Platform, Settings › Organisation holds Roles only, where Operator admin edits the Platform's two Roles. (12 Oct 2026)

From roles-and-permissions.html; main's GET /roles; the list-page rule from policies.html