🔏Roles
This page provides a description of the available API routes for managing roles.
The PORTOS system has a predefined list of user rights. Role allows to combine multiple user rights. When assigning rights to the user, roles are used. The role is represented by Role
class. Roles can be freely managed using API routes described in this section.
For instance, a user possessing the "sale" role would be granted rights such as ticketCreate
, ticketUpdate
, and ticketClose
. Roles can be used to group user rights based on areas of work or represent specific job positions like "cashier," "waiter," or "manager."
During product installation, the default roles setup is established, and it follows a more detailed approach, allowing precise role management, such as "sale", "stats", "storno," etc.
API methods
Get roles
GET
http://{server-address}/roles
Returns all roles that matches query parameters. Result is of type QueryResult<Role>
.
Query Parameters
name
string
Supports NData syntax.
label
string
Supports NData syntax.
$skip
int
Pagination property. Describing number of records to skip from beginning of result collection.
$take
int
Pagination property. Maximum count of items to be returned.
$sort
string[]
Comma separated list of property names. Please see NData syntax.
$count
bool
If set to true
, response will not contain items
collection. Use to get resource count, not the resources themselves.
Headers
Authorization*
string
Authorization header with authorization token.
Get role by name
GET
http://{server-address}/roles/{name}
Result is of type Role.
Path Parameters
name*
string
Unique role name.
Headers
Authorization*
string
Authorization header with authorization token.
Create role
POST
http://{server-address}/roles
Creates new role. Result is of type Role.
Required rights
Authorized user must have RoleCreate
right assigned.
Headers
Authorization*
string
Authorization header with authorization token.
Request Body
(body)*
Role
Role model to create
Create or update role
PUT
http://{server-address}/roles/{name}
Updates existing or creates new role. Result is of type Role.
Required rights
Authorized user must have assigned RoleCreate
or RoleUpdate
right.
Path Parameters
name*
string
Unique role name.
Headers
Authorization*
string
Authorization header with authorization token.
Request Body
(body)*
Role
Model to create or update.
Delete role by name
DELETE
http://{server-address}/roles/{name}
Required rights
Authorized user must have RoleDelete
right assigned.
Path Parameters
name*
string
Unique role name.
Headers
Authorization*
string
Authorization header with authorization token.
Last updated