> ## Documentation Index > Fetch the complete documentation index at: https://docs.domino.ai/llms.txt > Use this file to discover all available pages before exploring further. # Gets all permissions for requesting user > Gets all permissions for requesting user with optional volume ID or project ID in context field ## OpenAPI ````yaml /api-specs/cloud/public-api.json post /remotefs/v1/account/authz/permissions/authorizedactions openapi: 3.0.3 info: title: Domino Public API description: Reference for Domino's public REST API endpoints. version: 6.4.0 x-catalog-key: nucleus servers: - url: https://mycluster.domino.tech description: >- Replace 'mycluster.domino.tech' with your Domino cluster hostname. For Domino Cloud customers, that is `your-subdomain`.domino.tech (e.g., acme.domino.tech). For self-hosted deployments, it is the hostname you reach the Domino UI at. security: [] tags: - name: Projects - name: Project templates - name: Workspaces - name: Jobs - name: HPC Jobs - name: Environments - name: Hardware Tiers - name: Datasets - name: Data Sources - name: GenAI - name: AI Systems - name: Apps - name: App versions - name: App instances - name: Model APIs - name: Registered models - name: Model deployment - name: Extensions - name: Cost and billing - name: Users and organizations - name: Service accounts - name: Personal Access Tokens - name: Personal Access Tokens (admin) - name: Audit Trail - name: Custom metrics - name: PPM - name: Model Monitoring models - name: Model Monitoring drift and quality - name: Model Monitoring settings - name: Model Monitoring authentication - name: Governance bundles - name: Governance policies - name: Governance evidence and results - name: Governance operations - name: NetApp Volumes - name: NetApp Volumes snapshots - name: NetApp Volumes filesystems - name: NetApp Volumes transfers - name: Tags - name: Properties externalDocs: description: OpenAPI url: https://swagger.io/resources/open-api/ paths: /remotefs/v1/account/authz/permissions/authorizedactions: post: tags: - NetApp Volumes transfers summary: Gets all permissions for requesting user description: >- Gets all permissions for requesting user with optional volume ID or project ID in context field requestBody: content: application/json: schema: $ref: >- #/components/schemas/data-remotefs-service_server.PermissionRequest description: Permissions to check user against required: true responses: '200': description: OK content: application/json: schema: $ref: >- #/components/schemas/data-remotefs-service_server.PermissionResponse '400': description: Bad Request content: application/json: schema: $ref: '#/components/schemas/data-remotefs-service_server.HTTPError' '403': description: Forbidden content: application/json: schema: $ref: '#/components/schemas/data-remotefs-service_server.HTTPError' '404': description: Not Found content: application/json: schema: $ref: '#/components/schemas/data-remotefs-service_server.HTTPError' '500': description: Internal Server Error content: application/json: schema: $ref: '#/components/schemas/data-remotefs-service_server.HTTPError' components: schemas: data-remotefs-service_server.PermissionRequest: type: object required: - actions properties: actions: description: >- Effectively checking permissions, but using "actions" to be consistent with the rest of the API type: array items: $ref: '#/components/schemas/data-remotefs-service_server.PermissionInfo' data-remotefs-service_server.PermissionResponse: type: object properties: actions: description: Effectively are permissions, using "actions" for consistency type: array items: $ref: >- #/components/schemas/data-remotefs-service_server.PermissionResponseInfo data-remotefs-service_server.HTTPError: type: object properties: message: type: string data-remotefs-service_server.PermissionInfo: type: object required: - code - context - id properties: code: $ref: '#/components/schemas/data-remotefs-service_remotefs.PermissionCode' context: $ref: >- #/components/schemas/data-remotefs-service_server.PermissionInfoContext id: type: string data-remotefs-service_server.PermissionResponseInfo: type: object required: - code - id - result properties: code: $ref: '#/components/schemas/data-remotefs-service_remotefs.PermissionCode' id: type: string result: type: boolean data-remotefs-service_remotefs.PermissionCode: type: string enum: - data.manage_filesystems - data.view_filesystems - data.create_volumes - data.manage_volumes - data.manage_volumes_for_execution - data.read_volumes - data.view_volumes - data.mark_volumes_for_deletion - data.delete_volumes - data.edit_security_volumes - data.edit_taxonomy_tags - data.edit_property_values - data.project.perform_net_app_actions_in_project x-enum-varnames: - ManageFilesystemsCode - ViewFilesystemsCode - CreateVolumesCode - ManageVolumesCode - ManageVolumesForExecutionCode - ReadVolumesCode - ViewVolumesCode - MarkVolumesForDeletionCode - DeleteVolumesCode - EditSecurityVolumesCode - EditTaxonomyTagsCode - EditPropertyValuesCode - PerformNetAppActionsInProjectCode data-remotefs-service_server.PermissionInfoContext: type: object properties: projectId: type: string volumeId: type: string ```` ## Related topics - [Get Registered Models visible to user (v2)](/api-reference/registered-models/get-registered-models-visible-to-user-v2.md) - [Get a specific Registered Model](/api-reference/registered-models/get-a-specific-registered-model.md) - [Get Registered Models visible to user](/api-reference/registered-models/get-registered-models-visible-to-user.md) - [Check whether requesting user is over allowed volume limit](/api-reference/netapp-volumes/check-whether-requesting-user-is-over-allowed-volume-limit.md)