> ## Documentation Index > Fetch the complete documentation index at: https://docs.dados.rio/llms.txt > Use this file to discover all available pages before exploring further. # List actions allowed for a role > List all actions that a specific role can perform. **Authorization**: Users can view actions for roles they have permission to access. Permissions are checked via Cerbos policies. **Action Information**: Returns each action's ID, name, and description. **Use Cases**: - Audit role permissions and capabilities - Verify role-based access control configuration - Administrative oversight of security policies - Integration with external systems requiring permission information **Sorting**: Actions are returned sorted by name (alphabetical order). **Note**: This endpoint returns actions based on current Cerbos policy configuration. ## OpenAPI ````yaml https://raw.githubusercontent.com/prefeitura-rio/heimdall/main/docs/api/openapi.json get /api/v1/roles/{role_name}/actions openapi: 3.1.0 info: title: Heimdall Admin Service description: >- # Heimdall Admin Service API A comprehensive admin service for user and group management with authorization powered by Cerbos. ## Features - **User Management**: Automatic user creation from JWT tokens with role-based access control - **Group Management**: Create, manage, and assign users to groups with hierarchical permissions - **Role Management**: Define and assign roles to users and groups - **Mapping Management**: Configure API endpoint to action mappings for authorization - **Action Management**: Define available actions for fine-grained permission control - **Cerbos Integration**: Policy-based authorization with external Cerbos service - **Audit Logging**: Comprehensive audit trail for all administrative operations - **Redis Caching**: High-performance caching for frequently accessed data version: 1.0.0 servers: - url: https://services.pref.rio/heimdall-admin description: Production server - url: https://services.staging.app.dados.rio/heimdall-admin description: Staging server security: [] tags: - name: health description: Service health and readiness checks - name: users description: >- User management operations. Users are automatically created from JWT tokens. - name: groups description: >- Group management operations. Groups organize users and can have roles assigned. - name: memberships description: Group membership management. Assign and remove users from groups. - name: roles description: >- Role management operations. Roles define permissions that can be assigned to users or groups. - name: actions description: >- Action management operations. Actions define the granular permissions available in the system. - name: mappings description: >- API endpoint to action mapping configuration. Maps HTTP endpoints to authorization actions. paths: /api/v1/roles/{role_name}/actions: get: tags: - roles summary: List actions allowed for a role description: >- List all actions that a specific role can perform. **Authorization**: Users can view actions for roles they have permission to access. Permissions are checked via Cerbos policies. **Action Information**: Returns each action's ID, name, and description. **Use Cases**: - Audit role permissions and capabilities - Verify role-based access control configuration - Administrative oversight of security policies - Integration with external systems requiring permission information **Sorting**: Actions are returned sorted by name (alphabetical order). **Note**: This endpoint returns actions based on current Cerbos policy configuration. operationId: list_role_actions_api_v1_roles__role_name__actions_get parameters: - name: role_name in: path required: true schema: type: string title: Role Name responses: '200': description: List of role actions retrieved successfully content: application/json: schema: type: array items: $ref: '#/components/schemas/app__routers__roles__ActionResponse' title: >- Response List Role Actions Api V1 Roles Role Name Actions Get example: - id: 1 name: user:read description: Read user information - id: 2 name: user:list description: List users in the system '401': description: Unauthorized - Invalid or missing JWT token content: application/json: example: detail: Could not validate credentials '403': description: Forbidden - Insufficient permissions to view role actions content: application/json: example: detail: Permission denied to view actions for role 'data_analyst:read' '404': description: Role not found content: application/json: example: detail: Role 'unknown-role' not found '422': description: Validation Error content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' '500': description: Internal server error content: application/json: example: detail: 'Failed to retrieve role actions: Policy service error' security: - HTTPBearer: [] components: schemas: app__routers__roles__ActionResponse: properties: id: type: integer title: Id description: Unique identifier for the action example: 1 name: type: string title: Name description: Action name example: user:read description: anyOf: - type: string - type: 'null' title: Description description: Action description example: Read user information type: object required: - id - name title: ActionResponse description: Response model for action information. example: description: Read user information id: 1 name: user:read HTTPValidationError: properties: detail: items: $ref: '#/components/schemas/ValidationError' type: array title: Detail type: object title: HTTPValidationError ValidationError: properties: loc: items: anyOf: - type: string - type: integer type: array title: Location msg: type: string title: Message type: type: string title: Error Type type: object required: - loc - msg - type title: ValidationError securitySchemes: HTTPBearer: type: http scheme: bearer ````