Authorization policies for the API endpoints are based on (OAuth) scopes. A scope is an equivalent to a permission. The following scopes are available:
Scope name | Permissions | Role | Role | Role | Role |
|---|---|---|---|---|---|
gipod_pdo_write | Manage public domain occupancies (groundworks, works, events, parking bans) |
|
|
|
|
gipod_pdo_read | Read-only access to public domain occupancies (groundworks, works, events, parking bans) |
|
|
|
|
gipod_ts_write | Manage trench synergy requests & synergies |
|
|
|
|
gipod_ts_read | Read-only access trench synergy requests & synergies |
|
|
|
|
gipod_org_write | Manage organisations within the structure of your organisation |
|
|
|
|
gipod_org_read | Read-only access to organisations |
|
|
|
|
gipod_org_settings | Manage organisations & application settings on organisation level |
|
|
|
|
gipod_mh_write | Manage mobility hindrance |
|
|
|
|
gipod_mh_read | Read-only access to mobility hindrance |
|
|
|
|
gipod_notifications | Read notifications and update status of a notifications |
|
|
|
|
gipod_impact_ov | Judge impact of public domain occupancies on public transport |
|
|
|
|
*The following scopes will be added to this role: gipod_pdo_read, gipod_ts_read, gipod_mh_read, gipod_org_read.
A role is assigned to a user. A role specifies which scopes the user will get.
...