> For the complete documentation index, see [llms.txt](https://railnology.gitbook.io/railnology-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://railnology.gitbook.io/railnology-docs/organization-administration/roles-and-access.md).

# Roles and Access Levels

Organization administration in Railnology is built around a two-layer access model. Understanding how these layers work together helps you assign the right level of access to every person on your team from day one.

### The Two Layers of Access

Every member of your organization has two separate but related assignments:

**Layer 1 — Platform Role** controls what a user can see and do inside Railnology. It governs access to administrative tools, compliance records, reporting features, and settings.

**Layer 2 — Crew Position** controls how a user's Hours of Service is tracked and how they appear in crew management. It is only assigned to users who perform regulated railroad duties.

### Platform Roles

Railnology uses six operational roles for new assignments:

| Role                   | What They Can Do                                                                                    |
| ---------------------- | --------------------------------------------------------------------------------------------------- |
| **Administrator**      | Full organization control — user management, knowledge base, billing, settings, all compliance data |
| **Train Master**       | Train operations oversight, crew supervision, HoS monitoring                                        |
| **Dispatcher**         | Train dispatching, trip assignments, operations coordination                                        |
| **Operations Planner** | Trip planning, scheduling, operational coordination                                                 |
| **Safety Officer**     | Safety compliance, incident reporting, regulatory oversight                                         |
| **Crew Member**        | Operational duties, HoS tracking, compliance records                                                |

> **Note:** Legacy roles (Compliance, Technical User, and others) remain supported for existing members until migrated. All new role assignments should use the six operational roles above.

### How Roles Are Displayed

The **Team** tab in Org Admin shows a **Role Hierarchy** panel with all six roles and their current member counts. Expand any role to see which team members are assigned to it.

### Platform Admin vs. Org Admin

Railnology has two distinct administrative levels. **Org Admin** manages a single organization and is available to any user with the Administrator role. **Platform Admin** manages the entire Railnology platform and is reserved for Railnology's internal team.

> **Note:** Only users with the **Administrator** platform role can manage team members, assign roles, and access organization settings.
